2009/9/7 Jinsung Yang <jsgood.yang@xxxxxxxxxxx>: >> > I have some questions: >> > 1) Could you explain to us what is the 'well-defined' driver? >> >> I mean the driver to support three cpu and various target in one keypad >> driver, but i think that your posted driver seems for only SMDK6410. >> Also, we can make better driver via the review. >> > > Why do you think my driver cannot support various target? > I think there are misunderstandings, are there any architecture specific codes? For example, there is the keycodes. My target uses other keycodes. > Surely, there can be something wrong driver-specific codes such as 'dev_pm_ops', > but that's not a big deal.. we can modify it with mainline feedbacks. > My driver codes also have considered for our s5pc100, s5pc110, and many Samsung SoCs. > We will support other SoCs with adding some architecture definitions (not changing driver codes), but just 'NOT NOW'. OK, but It needs to implement considering not only s3c64xx but also s5pc1xx from first, and i think it's better to use "samsung" prefix. > Please understand, 'step by step'. > Of course we aware now our SoCs line-ups better than you, we are not happy to hear from you. I know but we need many discussion to merge the better code in kernel. I welcome it whenever. > > Finally, in your driver, regarding the if (cpu_is_s5pc100()) statement, > how do you think if you have to check another SoC at some time in the future? > Doing like this if (cpu_is_s5pc110()) else if (cpu_is_s5pc120()) else if (cpu_is_s5pc130()) ?? > Will you send some patches for this? looks be not good. I used only cpu_is_s5pc110(), also you can refer the omap keypad driver. It is a good example to support many omap arch > >> > 2) Did you test your keypad driver at s3c6410 based platform? >> >> No, i cannot test it on s3c64xx because i don't have a target using the >> keypad of s3c64xx such SMDK6410 but i tested the keypad driver on >> s5pc100 and s5pc110 and as you know, the keypad of the s3c6410 and >> s5pc100 datasheet is same almost, so i think it will operate on s3c64xx. >> >> > 3) There is no architecture codes for s5pc1xx series, why did you send >> keypad driver first for s5pc1xx before architecture codes? >> > >> >> Of course, I can post the arch code for keypad, but it is the common >> code for s3c64xx and s5pc1xx and we didn't post s5pc1xx arch code yet on >> ML. I also think it is better to post the keypad driver after posting >> arch. >> > > Best Regards > -- > Jinsung, Yang <jsgood.yang@xxxxxxxxxxx> > AP Development Team > System LSI, Semiconductor Business > SAMSUNG Electronics Co., LTD > > > -- > 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 > -- - Joonyoung Shim -- 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
