From: Javier Martinez Canillas <javier@dowhile0.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
Ferruh Yigit <fery@cypress.com>,
Javier Martinez Canillas <javier@osg.samsung.com>
Subject: Re: [PATCH v2] Input: cyttsp - Convert bindings to YAML and extend
Date: Wed, 31 Mar 2021 08:54:28 +0200 [thread overview]
Message-ID: <CABxcv==Dv6Z8QVzE+unbUTfS2DhE7xp6UTVnifDs9eVHM3UBsg@mail.gmail.com> (raw)
In-Reply-To: <20210329130758.2082126-1-linus.walleij@linaro.org>
On Mon, Mar 29, 2021 at 3:09 PM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> This converts the CYTTSP "Cypress TrueTouch Standard Product"
> to YAML bindings and fixes and adds some things in the process:
>
> - Rename the bindings file to cypress,cy8ctma340 after the main
> product in the series.
> - Add proper compatibles for the two known products:
> CY8CTMA340 and CY8CTST341.
> - Deprecate "cypress,cyttsp-spi" and "cypress,cyttsp-i2c"
> because device compatibles should be named after the
> hardware and not after which bus they are connected to.
> The topology implicitly tells us which bus it is and what
> interface to used.
> - Add VCPIN and VDD supplies, these are present just like
> on the CY8CTMA140.
>
> Cc: devicetree@vger.kernel.org
> Cc: Ferruh Yigit <fery@cypress.com>
> Cc: Javier Martinez Canillas <javier@osg.samsung.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
Reviewed-by: Javier Martinez Canillas <javier@dowhile0.org>
Best regards,
Javier
prev parent reply other threads:[~2021-03-31 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 13:07 [PATCH v2] Input: cyttsp - Convert bindings to YAML and extend Linus Walleij
2021-03-30 22:08 ` Rob Herring
2021-03-31 6:54 ` Javier Martinez Canillas [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='CABxcv==Dv6Z8QVzE+unbUTfS2DhE7xp6UTVnifDs9eVHM3UBsg@mail.gmail.com' \
--to=javier@dowhile0.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fery@cypress.com \
--cc=javier@osg.samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.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).