linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Daniel Mack <daniel@zonque.org>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Robert Jarzmik <robert.jarzmik@free.fr>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Mark Brown <broonie@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	linux-spi@vger.kernel.org
Subject: Re: [PATCH 3/3] ARM: spitz: Use software nodes for the ADS7846 touchscreen
Date: Fri, 21 Jun 2024 15:26:14 -0700	[thread overview]
Message-ID: <ZnX-Bs1dSQZS8sMP@google.com> (raw)
In-Reply-To: <CACRpkdbY2R_DzCx48OdGBFh6Lgytt_+VN1QK1pRq+9dDB=zw9w@mail.gmail.com>

On Thu, May 02, 2024 at 10:13:44AM +0200, Linus Walleij wrote:
> On Tue, Apr 30, 2024 at 9:04 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> 
> > Convert the Spitz to use software nodes for SPI CS and the
> > ADS7846 touchscreen following the pattern used in the TI
> > platforms.
> >
> > The Spitz is the only user of the wait_for_sync() callback in
> > the platform data, so define that this is a separate GPIO
> > in the device tree bindings (previous patch) and handle this
> > directly inside the ADS7846 driver instead.
> >
> > Add some infrastructure to the PXA boardfile common code to
> > handle software nodes attached to the SPI bus instead of
> > platform data.
> >
> > The SPI core will investigate the numner of GPIO handles to
> > figure out the number of chipselects used on the platform, so
> > no explicit encoding of the number of the number of chipselects
> > is needed.
> >
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> 
> Andy's patch series makes the Spitz SPI much cleaner to begin
> with so I will hold this off and rebase on top of Andy's stuff once
> that is in.

I dropped spitz parts from the patch leaving only the new hsync gpio
handling (and keeping the old legacy way of doing hsync) and applied.

There's an immutable branch ib/ads6746-hsync in my tree to help us
iterate on spitz changes.

Thanks.

-- 
Dmitry

      reply	other threads:[~2024-06-21 22:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30  7:03 [PATCH 0/3] ARM: Modernize the PXA Spitz a bit Linus Walleij
2024-04-30  7:03 ` [PATCH 1/3] ARM: spitz: Convert Spitz board to GPIO descriptors for LEDs Linus Walleij
2024-04-30  7:03 ` [PATCH 2/3] dt-bindings: ads7846: Add hsync-gpios Linus Walleij
2024-04-30 17:45   ` Conor Dooley
2024-06-21 22:24   ` Dmitry Torokhov
2024-04-30  7:03 ` [PATCH 3/3] ARM: spitz: Use software nodes for the ADS7846 touchscreen Linus Walleij
2024-05-02  8:13   ` Linus Walleij
2024-06-21 22:26     ` Dmitry Torokhov [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=ZnX-Bs1dSQZS8sMP@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=daniel@zonque.org \
    --cc=devicetree@vger.kernel.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=robert.jarzmik@free.fr \
    --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).