| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 26 Oct 2011 11:21:51 +1300 From: Austin Boyle <Austin.Boyle@...atnet.com> To: <linux-i2c@...r.kernel.org> CC: <linux-kernel@...r.kernel.org>, <lm-sensors@...sensors.org> Subject: Zarlink ZL30143 DPLL Driver Hello, I have written a driver for the Zarlink ZL30143 DPLL. It would typically be used in an embedded system as part of Sync-E support. The device is accessed via an I2C interface. In general the driver just exports register read/write functions, but I have also added some ioctl's to get/set various settings that require multiple register writes (e.g. selecting references, setting up priorities) and interrupt support. I can't find any similar drivers, but I can see that most of the configuration for this device could just be done using i2c-tools in user space. I would imagine there are too many generic I2C devices to include a separate driver for each of them in the kernel. Is there any point submitting a patch for this? In what system would this kind of device belong? Kind regards, Austin .................................................................... Austin Boyle Software Engineer AVIAT NETWORKS Direct: + 64 577 8711 Mobile: + 64 27 488 0221 Email: Austin.Boyle@...atnet.com Web: www.aviatnetworks.com Skype: boyle.austin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists