On 9/7/2009 3:33 PM, Harald Welte wrote: > On Mon, Sep 07, 2009 at 02:38:27PM +0900, Joonyoung Shim wrote: >> We already implemented and tested the keypad driver for s5pc100 & >> s5pc110 and maybe it will operate on s3c64xx. We use the samsung prefix >> to support three cpu. Because there is no the arch for s5pc100 and >> s5pc110, this driver doesn't compile yet on upstream kernel. > > The schedule of System LSI (the department that makes the SoC and provides the > BSP) is to first complete the 6410 support in the mainline kernel, and then > incrementally submit the core architecture code for 6440, c100 and c110, > followed by driver additions. > > So the events (ordered by time) have to be in the following order > > 1) the s3c-keypad driver with 6400/6410 support needs to be submitted and > submitted mainline. This is what Jinsun was starting, and which he > will continue until it is included mainline. > The keypad of s3c64xx and s5pc1xx is same almost, so we need to submit the well-defined driver from the first. > 2) the c100 / c110 or other SoC core architecture support needs to be > submitted mainline. Nobody at System LSI is working on this yet, > but they already have a tree based on 2.6.31-rcX for this. I suppose > the real work on submitting this will only be started after most of the > pending 6410 stuff has been submitted. > > 3) Samsung (either system LSI or DMC) can then send an incremental patch > for adding 6440/c100/c110 support to the s3c-keypad driver. > > Regards, -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html