From: Hans de Goede <hansg@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Linus Walleij <linus.walleij@linaro.org>,
Richard Hughes <rhughes@redhat.com>,
linux-i2c@vger.kernel.org, linux-usb@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 0/3] usb/gpio/i2c: Add Intel USBIO USB IO-expander drivers
Date: Wed, 10 Sep 2025 15:36:34 +0200 [thread overview]
Message-ID: <dbfe2464-394e-46fd-9e4d-7e41b62069e8@kernel.org> (raw)
In-Reply-To: <2025091045-expel-fiction-299f@gregkh>
Hi Greg,
On 10-Sep-25 3:25 PM, Greg Kroah-Hartman wrote:
> On Sun, Sep 07, 2025 at 07:50:53PM +0200, Hans de Goede wrote:
>> Hi All,
>>
>> Here is v2 of the patch series to add support for the Intel USBIO USB
>> IO-expander used by the MIPI cameras on various new (Meteor Lake and later)
>> Intel laptops.
>>
>> Changes in v2:
>> - Split usbio-bridge mutex into ctrl_mutex and bulk_mutex
>> - Drop SPI support since this is not used on devices in the field
>> - Rework disconnect handling to be more robust
>> - Several different revisions need special casing add a quirks mechanism
>> for this
>> - Stop using stdint.h (uintX_t) types
>> - Use __le16, __le32 type + cpu_to_le16() and friends for on wire words
>> - Properly check auxiliary_device_add() return value
>> - Add a mutex to the GPIO driver to 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
>> - Various (small) style fixes from Sakari's review of all 3 patches
>>
>> The first patch adds an USB bridge driver which registers auxbus children
>> for the GPIO and I2C functions of the USBIO chip.
>>
>> The second and third patch add a GPIO resp. an I2C driver for the
>> auxbus children using the IO functions exported by the USB bridge driver.
>>
>> The second and third patch depend on the IO functions exported by
>> the first patch. So to merge this we will need either an immutable tag on
>> the USB tree, or all 3 patches can be merged through the USB tree with
>> acks from the GPIO and I2C subsystem maintainers.
>
> Either is fine with me, patch 1 looks good enough for me to queue it up
> now.
That is good news.
> Let me know what you want me to do.
I've done a v3 of just the GPIO patch since Bart had some review-comments
there. Bart still had 2 more small remarks on the v3 GPIO patch. So I'm
about to send out a v4 series (with just changes to the GPIO driver
compared to this v2).
I hope Bart will be happy with v4, so then Bart can let you know if
he prefers an immutable tag, or wants you to merge the GPIO driver
into usb-next.
Once it is clear how to proceed with the GPIO driver I suggest that
we get both of them merged and then wait for feedback on the I2C driver.
Regards,
Hans
next prev parent reply other threads:[~2025-09-10 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 17:50 [PATCH v2 0/3] usb/gpio/i2c: Add Intel USBIO USB IO-expander drivers Hans de Goede
2025-09-07 17:50 ` [PATCH v2 1/3] usb: misc: Add Intel USBIO bridge driver Hans de Goede
2025-09-07 17:50 ` [PATCH v2 2/3] gpio: Add Intel USBIO GPIO driver Hans de Goede
2025-09-09 9:58 ` Bartosz Golaszewski
2025-09-10 11:34 ` Hans de Goede
2025-09-10 13:18 ` Bartosz Golaszewski
2025-09-10 13:23 ` Hans de Goede
2025-09-07 17:50 ` [PATCH v2 3/3] i2c: Add Intel USBIO I2C driver Hans de Goede
2025-09-10 13:25 ` [PATCH v2 0/3] usb/gpio/i2c: Add Intel USBIO USB IO-expander drivers Greg Kroah-Hartman
2025-09-10 13:36 ` Hans de Goede [this message]
2025-09-10 13:47 ` Bartosz Golaszewski
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=dbfe2464-394e-46fd-9e4d-7e41b62069e8@kernel.org \
--to=hansg@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=brgl@bgdev.pl \
--cc=gregkh@linuxfoundation.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