From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "luhua.xu" <luhua.xu@mediatek.com>
Cc: Rob Herring <robh@kernel.org>, Marek Vasut <marex@denx.de>,
Nick Dyer <nick.dyer@itdev.co.uk>,
Richard Leitner <richard.leitner@skidata.com>,
Martin Kepplinger <martink@posteo.de>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
weiqi.fu@mediatek.com, wsd_upstream@mediatek.com
Subject: Re: Kernel touch Kconfig consult
Date: Sun, 23 Jun 2019 00:02:49 -0700 [thread overview]
Message-ID: <20190623070249.GD204275@dtor-ws> (raw)
In-Reply-To: <1560509239.24963.25.camel@mbjsdccf07>
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
next parent reply other threads:[~2019-06-23 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1560509239.24963.25.camel@mbjsdccf07>
2019-06-23 7:02 ` Dmitry Torokhov [this message]
2019-06-23 10:43 ` Kernel touch Kconfig consult Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190623070249.GD204275@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luhua.xu@mediatek.com \
--cc=marex@denx.de \
--cc=martink@posteo.de \
--cc=nick.dyer@itdev.co.uk \
--cc=richard.leitner@skidata.com \
--cc=robh@kernel.org \
--cc=weiqi.fu@mediatek.com \
--cc=wsd_upstream@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.