* Re: Kernel touch Kconfig consult [not found] <1560509239.24963.25.camel@mbjsdccf07> @ 2019-06-23 7:02 ` Dmitry Torokhov 2019-06-23 10:43 ` Marek Vasut 0 siblings, 1 reply; 2+ messages in thread From: Dmitry Torokhov @ 2019-06-23 7:02 UTC (permalink / raw) To: luhua.xu Cc: Rob Herring, Marek Vasut, Nick Dyer, Richard Leitner, Martin Kepplinger, linux-input, linux-kernel, weiqi.fu, wsd_upstream Hi, On Fri, Jun 14, 2019 at 06:47:19AM -0400, luhua.xu wrote: > Hi Dmitry,Rob,Marek, Nick,Richard,Martin, > > In our customer support experience, many smartphone have two or three > touch vendor mixture , and customer use one load to support all touches. > For easy to config touch driver we use kernel config like this down > below, > > We change the config type from 'bool' to 'string'. > > config TOUCHSCREEN_MTK_TOUCH > string "Touch IC name for Mediatek package" > help > Set touch IC name if you have touch panel. > To compile this dirver for used touch IC. > > > And we config touch driver like this: > CONFIG_TOUCHSCREEN_MTK_TOUCH="GT9886 GT1151 TD4320" > > I only use one config to support 3 touches, while we have to use 3 > config to support 3 touch drivers if we set the config as 'bool'. > > So can I use Kconfig like this? > I do look forward to receiving your reply at your convenience . > I really do not see why having a sting is easier to have than 3 bools, especially if they pertain to different touch controllers. You must also have some custom processing of the config above as I am pretty sure our standard build tools would not work for it. Thanks. -- Dmitry ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Kernel touch Kconfig consult 2019-06-23 7:02 ` Kernel touch Kconfig consult Dmitry Torokhov @ 2019-06-23 10:43 ` Marek Vasut 0 siblings, 0 replies; 2+ messages in thread From: Marek Vasut @ 2019-06-23 10:43 UTC (permalink / raw) To: Dmitry Torokhov, luhua.xu Cc: Rob Herring, Nick Dyer, Richard Leitner, Martin Kepplinger, linux-input, linux-kernel, weiqi.fu, wsd_upstream On 6/23/19 9:02 AM, Dmitry Torokhov wrote: > Hi, > > On Fri, Jun 14, 2019 at 06:47:19AM -0400, luhua.xu wrote: >> Hi Dmitry,Rob,Marek, Nick,Richard,Martin, >> >> In our customer support experience, many smartphone have two or three >> touch vendor mixture , and customer use one load to support all touches. >> For easy to config touch driver we use kernel config like this down >> below, >> >> We change the config type from 'bool' to 'string'. >> >> config TOUCHSCREEN_MTK_TOUCH >> string "Touch IC name for Mediatek package" >> help >> Set touch IC name if you have touch panel. >> To compile this dirver for used touch IC. >> >> >> And we config touch driver like this: >> CONFIG_TOUCHSCREEN_MTK_TOUCH="GT9886 GT1151 TD4320" >> >> I only use one config to support 3 touches, while we have to use 3 >> config to support 3 touch drivers if we set the config as 'bool'. >> >> So can I use Kconfig like this? >> I do look forward to receiving your reply at your convenience . >> > > I really do not see why having a sting is easier to have than 3 bools, > especially if they pertain to different touch controllers. You must also > have some custom processing of the config above as I am pretty sure our > standard build tools would not work for it. I might be missing something obvious, but isn't DT something you want to use on your ARM device to describe the hardware , instead of hard-coding it into the kernel configuration ? I recently worked with MT6797 (the Gemini PDA SoC), and the vendorkernel does exactly this, it's a spectacular display of ifdeffery and Kconfig chaos, so I suspect this is where the idea of putting stuff into Kconfig comes from. -- Best regards, Marek Vasut ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-06-23 10:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1560509239.24963.25.camel@mbjsdccf07>
2019-06-23 7:02 ` Kernel touch Kconfig consult Dmitry Torokhov
2019-06-23 10:43 ` Marek Vasut
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).