From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "open list:BAREBOX" <barebox@lists.infradead.org>
Subject: Re: [PATCH 3/3] spi: spi-gpio: switch to new gpio binding
Date: Thu, 26 Sep 2024 10:19:23 +0200 [thread overview]
Message-ID: <ZvUZC9gzQFLMx5Ue@pengutronix.de> (raw)
In-Reply-To: <42e379a1-412b-4f46-81db-7dbd270d0dfd@pengutronix.de>
On Thu, Sep 26, 2024 at 08:09:44AM +0200, Ahmad Fatoum wrote:
> Hello Sascha,
>
> On 25.09.24 16:06, Sascha Hauer wrote:
> > The old deprecated device tree binding for the spi-gpio driver uses
> > "gpio-sck", "gpio-mosi" and "gpio-miso" to specify the GPIOs. Switch to
> > the new binding which uses the standard GPIO property names.
> >
> > The old binding is still used in some device trees, but none of the SoCs
> > using them is actually supported in barebox, so do not bother to keep a
> > fallback to the old binding. The one in-tree user of the old binding is
> > converted in this patch.
>
> There is one more user in sandbox-libftdi-example.dtsi. Please fix that as well.
Missed that, will do.
>
> Also, while you are it, why not switch over to the GPIOD API? :-)
I'll do that for the next round.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2024-09-26 8:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 14:06 [PATCH 0/3] spi-gpio updates Sascha Hauer
2024-09-25 14:06 ` [PATCH 1/3] spi: spi-gpio: actually delay in spidelay() Sascha Hauer
2024-09-26 5:55 ` Ahmad Fatoum
2024-09-26 7:05 ` Sascha Hauer
2024-09-25 14:06 ` [PATCH 2/3] spi: spi-gpio: support different word widths Sascha Hauer
2024-09-26 6:07 ` Ahmad Fatoum
2024-09-26 7:16 ` Sascha Hauer
2024-09-25 14:06 ` [PATCH 3/3] spi: spi-gpio: switch to new gpio binding Sascha Hauer
2024-09-26 6:09 ` Ahmad Fatoum
2024-09-26 8:19 ` Sascha Hauer [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=ZvUZC9gzQFLMx5Ue@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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