From: Jean Delvare <jdelvare@suse.de>
To: Andi Shyti <andi.shyti@samsung.com>
Cc: linux-input@vger.kernel.org, Jaechul Lee <jcsing.lee@samsung.com>,
Beomho Seo <beomho.seo@samsung.com>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [RFC PATCH] Input: tm2-touchkey - add hardware dependency
Date: Wed, 3 May 2017 10:31:10 +0200 [thread overview]
Message-ID: <20170503103110.748c306a@endymion> (raw)
In-Reply-To: <20170425110056.5aw5ce6b74z6txl2@gangnam.samsung>
Hi Andi,
On Tue, 25 Apr 2017 20:00:56 +0900, Andi Shyti wrote:
> > > On Mon, Apr 24, 2017 at 09:42:31AM +0200, Jean Delvare wrote:
> > So it really boils down to this question: is that chip a generic part
> > from Cypress, and if so, what is the real part number? Or was is
> > designed privately by Cypress specifically for Samsung for this one
> > board (and possibly others to come)?
>
> I knew that the naming was bringing confusion and we had a
> previous discussion about it with Chanwoo [1].
>
> This is indeed a generic device from Cypress. The driver has been
> ported from Android's Kernel [2]; it says that the device
> part is cy8cmbr3xxx, but the datasheet [3] doesn't have any
> connection with what the TM2 board has (i.e. the registers don't
> match). That's why we suspected that (as you said) this might be
> a touch key sensor specifically designed for the TM2 board.
Thanks for the pointers, it helps.
> Cypress was not that helpful.
I've been there before with other manufacturers. Chipsets designed
specifically for one hardware vendor are the hardest to support for this
reason.
> The alternative was to not provide support, but it didn't look
> right.
I agree, you did the right thing by getting the driver upstream. But it
doesn't mean this driver must be enabled in all distribution kernels.
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2017-05-03 8:31 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
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 [this message]
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=20170503103110.748c306a@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).