| 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
| ||
|
Message-Id: <200812031218.36036.david-b@pacbell.net> Date: Wed, 3 Dec 2008 12:18:35 -0800 From: David Brownell <david-b@...bell.net> To: "Trilok Soni" <soni.trilok@...il.com> Cc: "Kwangwoo Lee" <kwangwoo.lee@...il.com>, dmitry.torokhov@...il.com, linux-kernel@...r.kernel.org, "linux-omap@...r.kernel.org Mailing List" <linux-omap@...r.kernel.org> Subject: Re: [PATCH] Add tsc2007 based touchscreen driver. On Wednesday 03 December 2008, Trilok Soni wrote: > Adding linux-omap mailing list. Sometime I am thinking that same chip > might have interface to be connected on another board/cpu through SPI > too, so in this case we will have two drivers doing the same thing and > difference is just a change of the bus interface. Is this chip an example of that? It's I2C-only, and a quick scan of TI's touchscreen chip page didn't show a sibling chip with a logically-identical interface using SPI. > We should do something v4l2_subdev framework right now going on on > v4l2 mailing list to abstract the sensor drivers from bus. I'll disagree. When it's needed, this is easy to do ... bus glue talking to chip-specific code, and including some kind of bus-specific register access wrapper. No framework necessary, just straightforward design for any such drivers. - Dave -- 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