From: Jean Delvare <jdelvare@suse.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
linux-input@vger.kernel.org, Jaechul Lee <jcsing.lee@samsung.com>,
Beomho Seo <beomho.seo@samsung.com>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Andi Shyti <andi.shyti@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Rob Herring <robh@kernel.org>
Subject: Re: [RFC PATCH] Input: tm2-touchkey - add hardware dependency
Date: Tue, 25 Apr 2017 10:58:36 +0200 [thread overview]
Message-ID: <20170425105836.1e7be88c@endymion> (raw)
In-Reply-To: <20170424170953.GB12374@dtor-ws>
Hi Dmitry,
On Mon, 24 Apr 2017 10:09:53 -0700, Dmitry Torokhov wrote:
> On Mon, Apr 24, 2017 at 01:56:06PM +0200, Krzysztof Kozlowski wrote:
> > >> > On Mon, 24 Apr 2017 10:00:32 +0200, Krzysztof Kozlowski wrote:
> > >> > > On Mon, Apr 24, 2017 at 9:42 AM, Jean Delvare <jdelvare@suse.de> wrote:
> > >> > > > The tm2-touchkey driver is only useful on specific platforms. Add the
> > >> > > > missing hardware dependency so that the driver is not proposed on
> > >> > > > systems where the device does not exist.
> > >> > >
> > >> > > Although the device exists in only two upstreamed Exynos boards but
> > >> > > there is no hardware dependency on Exynos. The hardware does not
> > >> > > depend on Exynos.
> > >> > (...)
> > Workaround might be using default = N, unless ARCH_EXYNOS. Something like:
> > default y if ARCH_EXYNOS
>
> This would strongly imply that the device is available on all Exynos
> boards. I am fairly certain that our Chromebooks, for example, do not
> have it.
>
> Besides, I do not see what is wrong with driver being offered on a
> platform that does not have it.
It makes the life of distribution kernel maintainers a lot harder, by
asking them questions that are irrelevant. They may eventually figure
it out and say "no", but it costs them time to investigate each option.
Worst case they will accidentally say yes and bloat their kernel.
> This happens all the time.
That doesn't make it right. The trend is changing, and you should
embrace that change. What was acceptable 10 days ago when we had 7000
kernel options no longer works today with 17000.
> Consider I2C stuff:
Trying to make it personal? ;-)
> config I2C_I801
> tristate "Intel 82801 (ICH/PCH)"
> depends on PCI
> select CHECK_SIGNATURE if X86 && DMI
> select I2C_SMBUS
>
> This is an X86 device, but is offered everywhere where we have PCI.
In fact the 82801 family of south bridges is not limited to X86, it can
be found on IA64 hardware as well. It was discussed here:
https://patchwork.ozlabs.org/patch/635865/
and as you can see I would have liked the hardware dependency to be
added, it's Andy Shevchenko who declined :-(
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2017-04-25 8:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170424074240epcas3p2f90e0507afab25e9bfa48fe564936198@epcas3p2.samsung.com>
2017-04-24 7:42 ` [RFC PATCH] Input: tm2-touchkey - add hardware dependency Jean Delvare
2017-04-24 8:00 ` Krzysztof Kozlowski
2017-04-24 9:48 ` Jean Delvare
2017-04-24 9:58 ` Krzysztof Kozlowski
2017-04-24 11:34 ` Jean Delvare
2017-04-24 11:56 ` Krzysztof Kozlowski
2017-04-24 17:09 ` Dmitry Torokhov
2017-04-24 18:31 ` Krzysztof Kozlowski
2017-04-25 8:58 ` Jean Delvare [this message]
2017-04-24 18:49 ` Jean Delvare
2017-04-24 18:57 ` Krzysztof Kozlowski
2017-04-25 9:37 ` Jean Delvare
2017-04-25 2:28 ` Andi Shyti
2017-04-25 9:55 ` Jean Delvare
2017-04-25 11:00 ` Andi Shyti
2017-04-25 17:28 ` Dmitry Torokhov
2017-05-03 9:42 ` Jean Delvare
2017-05-03 9:53 ` Krzysztof Kozlowski
2017-05-03 8:31 ` Jean Delvare
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=20170425105836.1e7be88c@endymion \
--to=jdelvare@suse.de \
--cc=andi.shyti@samsung.com \
--cc=beomho.seo@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=javier@osg.samsung.com \
--cc=jcsing.lee@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=robh@kernel.org \
/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 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).