mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Badhri Jagan Sridharan <badhri@google.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel@collabora.com
Subject: Re: [PATCH 0/8] usb: typec: fusb302: cleanup device driver probe
Date: Mon, 16 Nov 2026 16:32:28 +0800	[thread overview]
Message-ID: <55fa6972-1c9f-4964-87f7-f36d1d4aae3f@rock-chips.com> (raw)
In-Reply-To: <20261113-fusb302-probe-cleanup-v1-0-e5c65a8c58c8@collabora.com>

Hi Sebastian,

On 11/14/2026 12:42 AM, Sebastian Reichel wrote:
> Move fusb302 to be fully converted to device managed resources
> instead of having a mix risking leaks and clean up the interrupt
> setup.
> 
> These have been tested for over half a year locally with different
> Rockchip boards. I waited for [0] to land, so that the DRM HPD auxillary
> device registration can also be dropped. As that series drags forever,
> let's get these cleanups processed independently.
> 

Although this patch series has received the RB tags it deserves,
but no one has time to merge it.

Perhaps we should split it further into smaller parts, focus only on
the generic parts, and send the v9?

> Note, that this first cleanups the GPIO interrupt handling and then drops
> it completley. The rationale is, that the last patch has a (low) chance of
> regressing somebody's system and having to be reverted. In that case the
> custom interrupt GPIO API should be properly documented (as deprecated)
> and we want at least the cleanups.
> 
> The series is based on 7.4-rc2 instead of Greg's usb-next branch (based
> on 7.4-rc1 and still empty), which is relevant for the first patch as
> older versions had devm_kzalloc() instead of devm_kzalloc_obj().
> 
> [0] https://lore.kernel.org/linux-rockchip/20261020072816.180-3-kernel@airkyi.com/
> 

-- 
Best, 
Chaoyi

      parent reply	other threads:[~2026-11-16  8:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 16:42 Sebastian Reichel
2026-11-13 16:42 ` [PATCH 1/8] usb: typec: tcpm: allocate pd_list entries non device managed Sebastian Reichel
2026-11-13 16:42 ` [PATCH 2/8] usb: typec: tcpm: add device managed port registration Sebastian Reichel
2026-11-13 16:42 ` [PATCH 3/8] usb: typec: fusb302: Switch to device managed resources Sebastian Reichel
2026-11-13 16:42 ` [PATCH 4/8] usb: typec: fusb302: switch to devm_pm_set_wake_irq Sebastian Reichel
2026-11-13 16:42 ` [PATCH 5/8] usb: typec: fusb302: rename init_gpio into fusb302_init_irq Sebastian Reichel
2026-11-13 16:42 ` [PATCH 6/8] usb: typec: fusb302: move gpio_int_n into function local scope Sebastian Reichel
2026-11-13 16:42 ` [PATCH 7/8] usb: typec: fusb302: rework gpio_int_n_irq handling Sebastian Reichel
2026-11-13 16:42 ` [PATCH 8/8] usb: typec: fusb302: drop custom gpio interrupt logic Sebastian Reichel
2026-11-16  8:32 ` Chaoyi Chen [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=55fa6972-1c9f-4964-87f7-f36d1d4aae3f@rock-chips.com \
    --to=chaoyi.chen@rock-chips.com \
    --cc=badhri@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sebastian.reichel@collabora.com \
    /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

all inboxes | Powered by JetHome®