All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Ray <ian.ray@gehealthcare.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nfc: nxp-nci: allow GPIOs to sleep
Date: Fri, 20 Feb 2026 15:28:54 +0200	[thread overview]
Message-ID: <aZhhljVG907fI6jC@zeus> (raw)
In-Reply-To: <d991e47a-0275-4f8d-afef-0e26fbd2bfdc@lunn.ch>

On Fri, Feb 20, 2026 at 02:19:34PM +0100, Andrew Lunn wrote:
> CAUTION: This email originated from outside of GE HealthCare. Only open links or attachments if you trust the sender. Report suspicious emails using Outlook’s “Report” button.
> 
> On Fri, Feb 20, 2026 at 01:59:05PM +0200, Ian Ray wrote:
> > Allow the firmware and enable GPIOs to sleep.
> >
> > This fixes a `WARN_ON' and allows the driver to operate GPIOs which are
> > connected to I2C GPIO expanders.
> >
> > -- >8 --
> > kernel: WARNING: CPU: 3 PID: 2636 at drivers/gpio/gpiolib.c:3880 gpiod_set_value+0x88/0x98
> > -- >8 --
> 
> Are there in tree boards which have this problem? Should this be part
> of stable?

I could not find any (I am working on a board which I have not submitted
upstream as yet).

> 
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> 
> Did you use ./scripts/get_maintainer.pl to get the To: and Cc: list?
> It is very unusual to see an empty To:.
> 

I did.  This driver is marked as an orphan.

>         Andrew

Regards,
Ian

  reply	other threads:[~2026-02-20 13:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 11:59 [PATCH] nfc: nxp-nci: allow GPIOs to sleep Ian Ray
2026-02-20 13:16 ` Charalampos Mitrodimas
2026-02-20 13:41   ` Ian Ray
2026-02-20 13:19 ` Andrew Lunn
2026-02-20 13:28   ` Ian Ray [this message]
2026-02-20 13:38     ` Ian Ray

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=aZhhljVG907fI6jC@zeus \
    --to=ian.ray@gehealthcare.com \
    --cc=andrew@lunn.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.