Re: [PATCH v2] misc: Driver for Silicon Labs Si570 and compatibles

[Sid Boyce]

Guenter Roeck wrote:
Depends. In our case, turns out the devices consuming the clock
have user mode drivers. Lots of history there, but the chip vendors
provide those user mode drivers, and the teams responsible for
integrating the drivers decided to not rewrite it to kernel mode drivers.
Also, for special purposes such as margining, it is necessary to control
the clock from userspace. So, for our use case, I need the user-visible
interface. I _don't_ need the kernel interface, at least not right now,
which is why I did not add it.

Browsing through the web, it seems the chip is somewhat popular with
Amateur Radio. No idea if it would ever be controlled for such a purpose
from Linux, but if so, it would also require a user configurable frequency.

If there is a better place for such a driver than misc, please let me know.

Thanks,
Guenter
=============================================================================
Support for these devices included in several Amateur radio programs 
tend to differ greatly which means reinventing the wheel in most of them.
Programs like Linrad, sdr-shell, quisk, lysdr, ghpsdr3, etc.
It's a small addition to the kernel that would significantly help in the 
development of software for the myriad of SDR (Software Defined Radio) 
designs based on this chip family.
I have 5 Amateur Radio transceivers using this chip and 2 more soon to 
be added.
They are all open hardware heavily reliant on Linux.
The addition of UAC2 (USB Audio Class 2) kernel support has helped our 
SDR hardware design efforts significantly.
I and the rest of the Linux SDR community would be happy to see it included.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/