public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Linus Walleij <linusw@kernel.org>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
	Bartosz Golaszewski <brgl@kernel.org>,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] mfd: si476x: Modernize GPIO handling
Date: Thu, 9 Apr 2026 15:58:23 +0100	[thread overview]
Message-ID: <20260409145823.GG3290953@google.com> (raw)
In-Reply-To: <20260327-mfd-si476x-v1-1-93298ca35d6d@kernel.org>

On Fri, 27 Mar 2026, Linus Walleij wrote:

> The SI476X driver depends on the legacy GPIO API. As it only
> really use a single GPIO for reset, and this can be easily converted
> to use a GPIO descriptor, modernize the driver.
> 
> The "reset" GPIO is obtained from a device property, such as a
> device tree ("reset-gpios", which is standard, but this hardware has
> no DT bindings as of now) or a software node for static platforms.
> 
> Out-of-tree users can easily adopt to providing a GPIO descriptor
> this way.
> 
> Signed-off-by: Linus Walleij <linusw@kernel.org>
> ---
>  drivers/mfd/Kconfig                 |  1 -
>  drivers/mfd/si476x-cmd.c            |  1 -
>  drivers/mfd/si476x-i2c.c            | 46 +++++++++++++------------------------
>  include/linux/mfd/si476x-core.h     |  5 ++--
>  include/linux/mfd/si476x-platform.h |  2 --
>  5 files changed, 19 insertions(+), 36 deletions(-)

Doesn't seem to want to apply:

diff a/include/linux/mfd/si476x-core.h b/include/linux/mfd/si476x-core.h        (rejected hunks)
@@ -103,7 +104,7 @@ enum si476x_power_state {
  * @state: Current power state of the device.
  * @supplues: Structure containing handles to all power supplies used
  * by the device (NULL ones are ignored).
- * @gpio_reset: GPIO pin connectet to the RSTB pin of the chip.
+ * @reset: GPIO connected to the RSTB pin of the chip.
  * @pinmux: Chip's configurable pins configuration.
  * @diversity_mode: Chips role when functioning in diversity mode.
  * @status_monitor: Polling worker used in polling use case scenarion

-- 
Lee Jones [李琼斯]

  parent reply	other threads:[~2026-04-09 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27  8:37 [PATCH] mfd: si476x: Modernize GPIO handling Linus Walleij
2026-03-30  8:46 ` Bartosz Golaszewski
2026-03-30  8:59   ` Linus Walleij
2026-04-09 14:58 ` Lee Jones [this message]
2026-04-09 22:31   ` Linus Walleij

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=20260409145823.GG3290953@google.com \
    --to=lee@kernel.org \
    --cc=andrew.smirnov@gmail.com \
    --cc=brgl@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@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