May 2024 - kernelnewbies@kernelnewbies.org - Kernelnewbies Mailing Lists

notifying clock consumers of frequency change
by Sam Winchenbach May 30, 2024

May 30, 2024

Hello, I am writing a driver for a frequency synthesizer that does not currently have any support in the kernel. This synthesizer is clocked by a fixed external oscillator. In my driver, I: 1. Register the clock hardware with devm_clk_hw_register 2. Describe the clocks to the DTS nodes with devm_of_clk_add_hw_provider Various external stimuli and commands (through IIO) can change the frequency of this synthesizer. How do I notify downstream devices that the frequency has changed? Ultimately it looks like __clk_notify() is what I want to call, but that is a non-exported function. Tracking it through, the function stack that calls this looks like it is used to request a new frequency, not to notify consumers that the frequency has changed. Does anyone have any tips, or perhaps know of an in-tree driver I could study to understand this better? Thanks. -Sam

1 0

Which driver to use for patches?
by Philipp Hortmann May 18, 2024

May 18, 2024

Dear knewbies and developers, maybe you ask yourself: Which driver to use for patches? Here the list of drivers I can support you with tests (from the staging subsystem): rtl8723bs rtl8192e rtl8712 vt6655 vt6656 Please feel free to contact me for questions. Thanks for your support. Bye Philipp Hint: You like to get your own hardware? Here some hints where I got mine from: rtl8723bs This hardware can be bought directly. https://www.ebay.de/sch/i.html?_from=R40&_nkw=rtl8723bs&_sacat=0 But since it has a SDIO Interface it is not so easy to connect it. Luckily I found out that the Laptop ODYS TRENDBOOK NEXT 14 (not so easy to install linux on) Laptop ODYS TRENDBOOK NEXT 14 Pro do have it build in. I just got one so I am able to test. rtl8192e This hardware can be bought directly. https://www.ebay.de/sch/i.html?_from=R40&_nkw=rtl8192e&_sacat=0&_odkw=rtl87… But you need a mini PCIe Card slot to connect it to your computer. rtl8712 I found this hardware some time ago. It is a USB Stick brand packard bell Part Number: AW-NU120 vt6655 I found this hardware long time ago. It is a mini PCI card. It seems that it is build in a One A400 Notebook. But I do not have this Notebook. https://forum.ubuntuusers.de/topic/via-vt-8739/ vt6656 I found this hardware long time ago. It is a USB Dongle. It was build into video cameras. That is the reason why I found it and was able to buy it.

1 0

Seeking Assistance with Spin Lock Usage and Resolving Hard LOCKUP Error
by Muni Sekhar May 17, 2024

May 17, 2024

Dear Linux Kernel Community, I am reaching out to seek assistance regarding the usage of spin locks in the Linux kernel and to address a recurring issue related to hard LOCKUP errors that I have encountered during testing. Recently, I developed a small kernel module that involves ISR handling and utilizes the spinlock_t primitive. In my module, I have employed spin locks both in process context using spin_lock() and spin_unlock() APIs, as well as in ISR context using spin_lock_irqsave() and spin_unlock_irqrestore() APIs. Here is a brief overview of how I have implemented spin locks in my module: spinlock_t my_spinlock; // Declare a spin lock // In ISR context (interrupt handler): spin_lock_irqsave(&my_spinlock, flags); // ... Critical section ... spin_unlock_irqrestore(&my_spinlock, flags); // In process context: (struct file_operations.read) spin_lock(&my_spinlock); // ... Critical section ... spin_unlock(&my_spinlock); However, during testing, I have encountered a scenario where a hard LOCKUP (NMI watchdog: Watchdog detected hard LOCKUP on cpu 2) error occurs, specifically when a process context code execution triggers the spin_lock() function and is preempted by an interrupt that enters the ISR context and encounters the spin_lock_irqsave() function. This situation leads to the CPU being stuck indefinitely. My primary concern is to understand the appropriate usage of spin locks in both process and ISR contexts to avoid such hard LOCKUP errors. I am seeking clarification on the following points: Is it safe to use spin_lock_irqsave() and spin_unlock_irqrestore() APIs in ISR context and spin_lock() and spin_unlock() APIs in process context simultaneously? In scenarios where a process context code execution is preempted by an interrupt and enters ISR context, how should spin locks be used to prevent hard LOCKUP errors? Are there any specific guidelines or best practices for using spin locks in scenarios involving both process and ISR contexts? I would greatly appreciate any insights, guidance, or suggestions from the experienced members of the Linux kernel community to help address this issue and ensure the correct and efficient usage of spin locks in my kernel module. Thank you very much for your time and assistance. -- Thanks, Sekhar

2 1

Handling I2C eeprom devices
by Patryk May 17, 2024

May 17, 2024

Hi, I've got a question regarding how to handle I2C eeprom devices. I see that in the kernel/drivers/misc/eeprom there are not that many drivers available. Does it mean that they support various chips that do not necessarily come from one vendor? Looking at example at24.c, in the compatible properties I see that all of them refers to atmel, however when I compared the following devices: AT24C04C and BRCB008GWZ, at the first glance they look kinda similar: - they are organized internally in the same way - 1024 x 8 (8K) - read/write commands looks the same I'm not asking you to tell me whether or not it's possible this driver at24 with the device I need (BRCB008GWZ), rather I would like to get a suggestion on how to approach this and what factors I should take into account to make the right decision. Best regards Patryk

3 2

[RFC PATCH] kvm: replace spaces with a tab
by Mohamed Karaoui May 16, 2024

May 16, 2024

Hi list, This is an attempt to get a feeling of sending a first patch. Please feel free to comment. I have few questions: - I have build this patch against the torvalds/linux.git. Does it matter which tree I use as long as it works on the maintainer tree? - In this particular case I checked the maintainer. It seems that its tree is something of 11 years old. - Should I just go ahead and send this patch to the emails in ./scripts/get_maintainer.pl anyway? (replacing this message of course) Signed-off-by: Mohamed Karaoui <moharaka(a)gmail.com> --- virt/kvm/kvm_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c index ff0a20565f90..cd4702e069ca 100644 --- a/virt/kvm/kvm_main.c +++ b/virt/kvm/kvm_main.c @@ -6368,7 +6368,7 @@ EXPORT_SYMBOL_GPL(kvm_get_running_vcpu); */ struct kvm_vcpu * __percpu *kvm_get_running_vcpus(void) { - return &kvm_running_vcpu; + return &kvm_running_vcpu; } #ifdef CONFIG_GUEST_PERF_EVENTS -- 2.34.1

2 1

Looking for advise
by Jules Irenge May 15, 2024

May 15, 2024

I am looking for advice on what to do after reading the Linux device driver book. Someone suggests I get a beaglebone and write some i2c driver to get hands-on experience, I will consider that. Any other suggestion will be appreciated Thanks, Jules *..* Open source contributor: https://bit.ly/40GblaQ Blog: https:// <https://www.strava.com/athletes/72390635> www.julesirenge.blog twitter: @jules_irenge strava: https://www.strava.com/athletes/72390635 linkedIn: *https://www.linkedin.com/in/jules-irenge-87282238/ <https://www.linkedin.com/in/jules-irenge-87282238/>*

2 1

Fwd: Qemu hangs at Starting KernelMemorySanitizer
by Camila Alvarez May 14, 2024

May 14, 2024

Hello all, I'm trying to debug a KMSAN related issue. To do so I created a QEMU instance to replicate the bug, however, it gets stuck at startup. It gets stuck after saying: Starting KernelMemorySanitizer ATTENTION: KMSAN is a debugging tool! Do not use on production machines! Has anyone experienced something similar? Do you have any idea of which configuration options I should look into? To give some context: I'm working on an ARM64 machine, and I'm cross compiling the kernel for x86_64 using clang. Thanks!

1 0

Seeking Assistance: Implementing USB Device Suspend/Resume in User Space Driver
by Muni Sekhar May 13, 2024

May 13, 2024

Dear Linux USB Subsystem Community, I hope this email finds you well. We are currently working on a USB device driver in the Linux kernel space, which supports the suspend/resume functionality for a USB device using the struct usb_driver's .suspend and .resume callbacks. In our driver code, we perform a check to determine if the device has remote wakeup capability. If the device supports remote wakeup, we enable the device's autosuspend mode by setting the struct usb_device->dev.power.autosuspend_delay parameter and then calling usb_enable_autosuspend(). Similarly, to resume the suspended device, we expose an API to user space via IOCTL. In this process, we set struct usb_device->dev.power.autosuspend_delay to -1 and then call usb_disable_autosuspend(). While we have successfully converted most of the USB device driver functionality from kernel space to user space using libusb, we are now seeking guidance on how to implement USB device suspend/resume in user space. Specifically, we would like to know if libusb provides support for achieving the suspend/resume functionality mentioned above. Additionally, any insights or suggestions on how to accomplish this task would be greatly appreciated. It's worth mentioning that our USB device driver also supports Bulk\Coontrol I/O transfers and other functionalities. Thank you in advance for any assistance you can provide. I look forward to your valuable inputs and recommendations. -- Thanks, Sekhar

2 12

Inquiry Regarding Handling of Kernel Crashes
by Muni Sekhar May 12, 2024

May 12, 2024

Dear Linux Kernel Community, I hope this email finds you well. I am currently engaged in testing device drivers in Linux kernel mode, and I have encountered various types of kernel crashes during my testing process. Among these, some examples of kernel crashes include OOPS, lockups and others. I have a few questions regarding the handling of kernel crashes during testing: When encountering a kernel crash during testing, is it advisable to continue testing without rebooting the system? Or is it preferable to reboot the system after each kernel crash and then resume testing? Can the first kernel crash, whether it is an OOPS, or any other type crash, potentially lead to subsequent crashes of the same or different types? If so, should debugging efforts focus only on the first kernel crash, or should all subsequent crashes also be considered and addressed? In the event that the system needs to be rebooted after a kernel crash, how can user space test utilities be informed that a kernel crash has occurred? Additionally, how can the system be configured to automatically reboot in the event of a kernel crash? I would greatly appreciate any insights or best practices you can share regarding the handling of kernel crashes during testing. Your expertise and guidance on this matter would be invaluable to my testing efforts. Thank you very much for your time and assistance. I look forward to your response. -- Thanks, Sekhar

1 0

Regarding Linux Kernel Mentorship
by Manav May 12, 2024

May 12, 2024

Hi! I'm Manav Chauhan, a 3rd year Computer Science and Engineering student from India and I have an aim of working at CERN Labs one day where I can contribute to a place that drives scientific innovation where my interest lies in the domain of system/low-level as I have always been fascinated by the core or the internals of Computer Science. To achieve such an ambitious goal, I need some credibility and more experience in the field of low-level and operating systems. My research led me to the Linux Kernel Mentorship program where I read blogs and experiences of other such passionate individuals who contributed to such a core technology that is the linux kernel. I have been using Debian Testing for a year and am curious about how all of it works under the hood. Diving deep into this field may be daunting so I wanted some guidance regarding participation in this mentorship for the Fall program. I am already midway through the 'A Beginner's Guide to Linux Kernel Development (LFD103)' course and was looking forward to some guidance regarding other steps I should take to strengthen my application..

1 0