From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Hans de Goede <hansg@kernel.org>,
Richard Hughes <rhughes@redhat.com>,
linux-i2c@vger.kernel.org, linux-usb@vger.kernel.org,
linux-gpio@vger.kernel.org,
Israel Cepeda <israel.a.cepeda.lopez@intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Wolfram Sang <wsa@kernel.org>, Andi Shyti <andi.shyti@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v5 2/3] gpio: Add Intel USBIO GPIO driver
Date: Thu, 11 Sep 2025 15:31:48 +0200 [thread overview]
Message-ID: <2025091139-scalping-twenty-93d2@gregkh> (raw)
In-Reply-To: <CAMRc=McKOTWxu=M0S0p0Uyhod-h4mNH9QfsLsycN4vbHJPtgeQ@mail.gmail.com>
On Thu, Sep 11, 2025 at 09:27:19AM -0400, Bartosz Golaszewski wrote:
> On Thu, 11 Sep 2025 15:18:31 +0200, Hans de Goede <hansg@kernel.org> said:
> > From: Israel Cepeda <israel.a.cepeda.lopez@intel.com>
> >
> > Add a a driver for the GPIO auxbus child device of the Intel USBIO USB
> > IO-expander used by the MIPI cameras on various new (Meteor Lake and
> > later) Intel laptops.
> >
> > Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> > Co-developed-by: Hans de Goede <hansg@kernel.org>
> > Signed-off-by: Hans de Goede <hansg@kernel.org>
> > Signed-off-by: Israel Cepeda <israel.a.cepeda.lopez@intel.com>
> > ---
> > Changes in v5:
> > - Move GPIO_USBIO Kconfig option under 'menu "USB GPIO expanders"'
> >
> > Changes in v4:
> > - Drop include <linux/dev_printk.h>, unneeded auxiliary_set_drvdata()
> >
> > Changes in v3:
> > - Drop (offset >= gc->ngpio) check and make usbio_gpio_get_bank_and_pin()
> > return void
> > - Propagate usbio_gpio_set() ret val in usbio_gpio_direction_output()
> > - Use devm_gpiochip_add_data() and drop auxiliary_driver remove() callback
> >
> > Changes in v2:
> > - Add a config_mutex protect usbio_gpio_update_config() calls, which
> > read-modify-write banks[x].config, racing with each other
> > - Adjust usbio_gpio_get() to have an int return value and propagate the
> > usbio_control_msg() return value
> > - Use __le16, __le32 type + cpu_to_le16() and friends for on wire words
> > - Some small style fixes from Sakari's review
>
> If Greg wants to take it:
>
> Acked-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> or I can take it once patch 1/3 is in an immutable branch.
I'll just take it, simpler that way, thanks!
greg k-h
next prev parent reply other threads:[~2025-09-11 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 13:18 [PATCH v5 0/3] usb/gpio/i2c: Add Intel USBIO USB IO-expander drivers Hans de Goede
2025-09-11 13:18 ` [PATCH v5 1/3] usb: misc: Add Intel USBIO bridge driver Hans de Goede
2025-09-11 13:18 ` [PATCH v5 2/3] gpio: Add Intel USBIO GPIO driver Hans de Goede
2025-09-11 13:27 ` Bartosz Golaszewski
2025-09-11 13:31 ` Greg Kroah-Hartman [this message]
2025-09-11 13:18 ` [PATCH v5 3/3] i2c: Add Intel USBIO I2C driver Hans de Goede
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=2025091139-scalping-twenty-93d2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andi.shyti@kernel.org \
--cc=brgl@bgdev.pl \
--cc=hansg@kernel.org \
--cc=israel.a.cepeda.lopez@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rhughes@redhat.com \
--cc=sakari.ailus@linux.intel.com \
--cc=wsa@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;
as well as URLs for NNTP newsgroup(s).