Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	 linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Bartosz Golaszewski	 <bartosz.golaszewski@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH] reset: gpio: add the "compatible" property
Date: Thu, 08 Jan 2026 13:02:09 +0100	[thread overview]
Message-ID: <f203856efd3deedce56cc39dda13d563636c5f7e.camel@pengutronix.de> (raw)
In-Reply-To: <CAMRc=Mcp8b81XX0AcBEpPNZQxDcPtHXQrKatw7k+fN7u5tYuGw@mail.gmail.com>

Hi Bartosz,

On Mo, 2025-12-08 at 23:57 -0800, Bartosz Golaszewski wrote:
> On Tue, 25 Nov 2025 11:43:01 +0100, Philipp Zabel <p.zabel@pengutronix.de> said:
> > On Fr, 2025-11-21 at 14:57 +0100, Bartosz Golaszewski wrote:
> > > From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> > > 
> > > In order to correctly handle the interaction between the reset-gpio
> > > devices and shared GPIOs managed by GPIOLIB, we need to be able to
> > > identify the former. Add the "compatible" property to allow us to use
> > > the device_is_compatible() helper.
> > > 
> > > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> > > ---
> > > Philipp: this can go directly into your branch, I will fix the GPIO part
> > > in the next cycle. For now it just parses the device name.
> > 
> > Applied to reset/next, thanks!
> > 
> > [1/1] reset: gpio: add the "compatible" property
> >       https://git.pengutronix.de/cgit/pza/linux/commit/?id=a0d57f7504b6
> > 
> > regards
> > Philipp
> > 
> 
> Hi Phillipp!
> 
> I realized this didn't make your v6.19-rc1 PR. Any chance you could make it
> into an immutable branch or maybe you could back it out from your branch and
> allow me to take it with your Ack? I have a WiP patch that fixes one remaining
> issue in the interaction between reset-gpios and shared GPIOs. I want to send
> it for rc1 or rc2 but I would prefer to use device_is_compatible() in it.

Sorry for the delay, I didn't get to this before hibernating. I've now
rebased the patch onto v6.19-rc1 now and made an immutable branch for
you to fetch:

The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:

  Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)

are available in the Git repository at:

  https://git.pengutronix.de/git/pza/linux.git reset/gpio-compatible

for you to fetch changes up to b3d8508351af7f6366a0a18068c194b399ead2c3:

  reset: gpio: add the "compatible" property (2026-01-08 12:25:20 +0100)

----------------------------------------------------------------
Bartosz Golaszewski (1):
      reset: gpio: add the "compatible" property

 drivers/reset/core.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

regards
Philipp

      reply	other threads:[~2026-01-08 12:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 13:57 [PATCH] reset: gpio: add the "compatible" property Bartosz Golaszewski
2025-11-21 15:12 ` Philipp Zabel
2025-11-25 10:43 ` Philipp Zabel
2025-12-09  7:57   ` Bartosz Golaszewski
2026-01-08 12:02     ` Philipp Zabel [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=f203856efd3deedce56cc39dda13d563636c5f7e.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=brgl@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@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