From: Greg KH <gregkh@linuxfoundation.org>
To: zain_zhou@realsil.com.cn
Cc: linux-staging@lists.linux.dev, linux-i3c@lists.infradead.org,
devicetree@vger.kernel.org, alexandre.belloni@bootlin.com,
Frank.Li@nxp.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linusw@kernel.org, brgl@kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: i3c: add Realtek RTS490x I3C HUB driver
Date: Mon, 4 May 2026 16:25:41 +0200 [thread overview]
Message-ID: <2026050412-bush-rosy-959d@gregkh> (raw)
In-Reply-To: <20260430121354.6253-2-zain_zhou@realsil.com.cn>
On Thu, Apr 30, 2026 at 08:13:54PM +0800, zain_zhou@realsil.com.cn wrote:
> From: zain_zhou <zain_zhou@realsil.com.cn>
>
> Add driver for Realtek RTS490x series I3C HUB devices (RTS4900,
> RTS4901, RTS4902, RTS4903, RTS4904, RTS4906).
>
> The I3C HUB is a smart device that provides:
> - voltage compatibility across I3C Controller and Target devices
> - bus capacitance isolation
> - address conflict isolation
> - I3C port expansion (up to 8 target ports)
> - dual controller port support
> - I3C and SMBus device compatibility
> - GPIO expansion via target ports
>
> The driver supports:
> - Device Tree based configuration of LDO, pull-up, IO strength
> and per-port mode (I3C/SMBus/GPIO/disabled)
> - Logical I3C bus registration per target port
> - SMBus agent functionality with IBI and polling modes
> - GPIO chip with IRQ support
> - DebugFS interface for register access and DT config inspection
> - IBI (In-Band Interrupt) handling
>
> The driver is placed in staging as it has known issues to be resolved
> before mainlining; see drivers/staging/rts490x/TODO for details.
>
> Signed-off-by: zain_zhou <zain_zhou@realsil.com.cn>
We need a real name, not an email alias.
And no, please don't add new drivers to drivers/staging/ especially when
it is so easy to fix them up properly "first" before adding them to the
kernel tree.
Your TODO file is pretty easy:
> diff --git a/drivers/staging/rts490x/TODO b/drivers/staging/rts490x/TODO
> new file mode 100644
> index 000000000000..0be2d7693d68
> --- /dev/null
> +++ b/drivers/staging/rts490x/TODO
> @@ -0,0 +1,19 @@
> +TODO list for rts490xa-i3c-hub staging driver
> +==============================================
> +
> +- Move driver out of staging once the following are addressed:
> + - Add proper DT binding schema validation (dt-schema)
> + - Clean up open-coded OF property parsing; use device_property_* APIs
> + instead of of_property_read_* where possible
> + - Remove use of full_name / sscanf for node name parsing; use
> + of_node_name_eq() and fwnode helpers instead
> + - Replace global mutex (i3c_hub_regmap_mutex) with per-device locking
> + - Add kernel-doc comments for all exported/public functions
> + - Resolve TODO comment in i3c_hub_hw_configure_tp() regarding MUX
> + connection verification
> + - Remove TBD comment in i3c_hub_probe() regarding DEV_CMD security lock
> + - Review and fix potential locking issues in i3c_hub_delayed_work()
> + when registering logical buses
> + - Fix error handling in i3c_hub_delayed_work(): early return on failure
> + does not unregister already-registered logical buses, causing resource
> + leak; needs proper cleanup on error path
All of those you could do this week. Don't add stuff to staging that
you are going to maintain, as it will be more work in the end. Just do
the needed extra effort and then merge it to the proper place in the
tree.
thanks,
greg k-h
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2026-05-04 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 12:13 [PATCH 1/2] dt-bindings: i3c: add binding for Realtek RTS490x I3C HUB zain_zhou
2026-04-30 12:13 ` [PATCH 2/2] staging: i3c: add Realtek RTS490x I3C HUB driver zain_zhou
2026-05-04 14:25 ` Greg KH [this message]
2026-04-30 13:41 ` [PATCH 1/2] dt-bindings: i3c: add binding for Realtek RTS490x I3C HUB Rob Herring (Arm)
2026-05-01 9:37 ` Krzysztof Kozlowski
2026-05-04 20:34 ` Frank Li
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=2026050412-bush-rosy-959d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=robh@kernel.org \
--cc=zain_zhou@realsil.com.cn \
/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