From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: <broonie@kernel.org>, <linus.walleij@linaro.org>, <brgl@bgdev.pl>,
<linux-gpio@vger.kernel.org>, <linux-spi@vger.kernel.org>,
<patches@opensource.cirrus.com>
Subject: Re: [PATCH v3 3/3] spi: cs42l43: Add bridged cs35l56 amplifiers
Date: Tue, 9 Apr 2024 09:24:19 +0000 [thread overview]
Message-ID: <ZhUJQxss1m8aIvJs@ediswmail9.ad.cirrus.com> (raw)
In-Reply-To: <ZhROj-ZfKp_CEcA6@smile.fi.intel.com>
On Mon, Apr 08, 2024 at 11:07:43PM +0300, Andy Shevchenko wrote:
> On Mon, Apr 08, 2024 at 10:50:28PM +0300, Andy Shevchenko wrote:
> > On Mon, Apr 08, 2024 at 07:07:55PM +0300, Andy Shevchenko wrote:
> > > On Mon, Apr 8, 2024 at 6:35 PM Charles Keepax
> > > <ckeepax@opensource.cirrus.com> wrote:
> > > > On Wed, Apr 03, 2024 at 11:47:36PM +0300, Andy Shevchenko wrote:
> > > > > Fri, Mar 29, 2024 at 11:47:30AM +0000, Charles Keepax kirjoitti:
>
> ...
>
> > > > > > +#include <dt-bindings/gpio/gpio.h>
> > > > >
> > > > > Hmm... Is it requirement by gpiolib-swnode? (I haven't looked at the use cases,
> > > > > I'm not the author of this idea, hence the Q).
> > > >
> > > > It's required for the GPIO_ACTIVE_LOW used in the swnode stuff.
> > >
> > > Seems to me like you are mistaken.
> > > https://elixir.bootlin.com/linux/latest/source/drivers/gpio/gpiolib-swnode.c#L85
> >
> > Okay, I stand corrected, under "native" the GPIO_* are assumed.
> >
> > But what you need is to include gpio/property.h for that, and not directly
> > the DT header.
>
> Oh, my, we have two _almost_ identical definitions in machine.h and under DT.
> So, I believe we are using ones from machine.h.
>
Yeah that is my bad I should be using those instead.
Thanks,
Charles
prev parent reply other threads:[~2024-04-09 9:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 11:47 [PATCH 0/3] Add bridged amplifiers to cs42l43 Charles Keepax
2024-03-29 11:47 ` [PATCH v3 1/3] gpio: swnode: Add ability to specify native chip selects for SPI Charles Keepax
2024-04-03 20:21 ` Andy Shevchenko
2024-03-29 11:47 ` [PATCH v3 2/3] spi: Add a mechanism to use the fwnode name for the SPI device Charles Keepax
2024-04-03 20:29 ` Andy Shevchenko
2024-04-08 13:51 ` Charles Keepax
2024-04-08 16:11 ` Andy Shevchenko
2024-03-29 11:47 ` [PATCH v3 3/3] spi: cs42l43: Add bridged cs35l56 amplifiers Charles Keepax
2024-04-03 20:47 ` Andy Shevchenko
2024-04-08 15:35 ` Charles Keepax
2024-04-08 16:07 ` Andy Shevchenko
2024-04-08 19:50 ` Andy Shevchenko
2024-04-08 20:07 ` Andy Shevchenko
2024-04-09 9:24 ` Charles Keepax [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=ZhUJQxss1m8aIvJs@ediswmail9.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
/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).