From: Frank Li <Frank.li@nxp.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
Tommaso Merciai <tomm.merciai@gmail.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
wsa+renesas <wsa+renesas@sang-engineering.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"magnus.damm" <magnus.damm@gmail.com>,
"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/4] i3c: renesas: Switch to clk_bulk API and store clocks in private data
Date: Tue, 6 Jan 2026 10:17:13 -0500 [thread overview]
Message-ID: <aV0neUGcqiGkE/Sv@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <TY3PR01MB113466AB09CC77C375492A0E28687A@TY3PR01MB11346.jpnprd01.prod.outlook.com>
On Tue, Jan 06, 2026 at 03:01:49PM +0000, Biju Das wrote:
> Hi Frank Li,
>
> Thanks for the feedback.
>
> > -----Original Message-----
> > From: Frank Li <Frank.li@nxp.com>
> > Sent: 06 January 2026 14:49
> > Subject: Re: [PATCH v4 1/4] i3c: renesas: Switch to clk_bulk API and store clocks in private data
> >
> > On Mon, Jan 05, 2026 at 06:06:19PM +0000, Biju Das wrote:
> > > Hi Frank Li,
> > >
> > > > -----Original Message-----
> > > > From: Frank Li <Frank.li@nxp.com>
> > > > Sent: 05 January 2026 17:12
> > > > Subject: Re: [PATCH v4 1/4] i3c: renesas: Switch to clk_bulk API and
> > > > store clocks in private data
> > > >
> > > > On Mon, Jan 05, 2026 at 11:49:59AM +0100, Tommaso Merciai wrote:
> > > > > Replace individual devm_clk_get_enabled() calls with the clk_bulk
> > > > > API and store the clock handles in the driver's private data structure.
> > > > >
> > > > > All clocks required by the controller are now acquired and enabled
> > > > > using devm_clk_bulk_get_all_enabled(), removing the need for
> > > > > per-SoC clock handling and the renesas_i3c_config data.
> > > > > The TCLK is accessed via a fixed index in the bulk clock array.
> > > > >
> > > > > Simplify the code and prepare the driver for upcoming
> > > > > suspend/resume support.
> > > > >
> > > > > No functional change intended.
> > > > >
> > > > > Reviewed-by: Biju Das <biju.das.jz@bp.renesas.com>
> > > > > Signed-off-by: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
> > > > > ---
> > > > > v3->v4:
> > > > > - Collected Biju Das tag.
> > > > >
> > > > > v2->v3:
> > > > > - Added define for TCLK index.
> > > > > - Use devm_clk_bulk_get_all_enabled() into renesas_i3c_probe().
> > > > > - Improved commit body.
> > > > > - Dropped unnecessary static const char * const renesas_i3c_clks[].
> > > > > - Removed the need for per-SoC clock handling and the renesas_i3c_config data.
> > > > >
> > > > > v1->v2:
> > > > > - New patch.
> > > > >
> > > > > drivers/i3c/master/renesas-i3c.c | 43
> > > > > ++++++++------------------------
> > > > > 1 file changed, 11 insertions(+), 32 deletions(-)
> > > > >
> > > > > diff --git a/drivers/i3c/master/renesas-i3c.c
> > > > > b/drivers/i3c/master/renesas-i3c.c
> > > > > index 426a418f29b6..1b8f4be9ad67 100644
> > > > > --- a/drivers/i3c/master/renesas-i3c.c
> > > > > +++ b/drivers/i3c/master/renesas-i3c.c
> > > > > @@ -198,6 +198,8 @@
> > > > > #define RENESAS_I3C_MAX_DEVS 8
> > > > > #define I2C_INIT_MSG -1
> > > > >
> > > > > +#define RENESAS_I3C_TCLK_IDX 1
> > > > > +
> > > > > enum i3c_internal_state {
> > > > > I3C_INTERNAL_STATE_DISABLED,
> > > > > I3C_INTERNAL_STATE_CONTROLLER_IDLE,
> > > > > @@ -259,7 +261,8 @@ struct renesas_i3c {
> > > > > u8 addrs[RENESAS_I3C_MAX_DEVS];
> > > > > struct renesas_i3c_xferqueue xferqueue;
> > > > > void __iomem *regs;
> > > > > - struct clk *tclk;
> > > > > + struct clk_bulk_data *clks;
> > > > > + u8 num_clks;
> > > > > };
> > > > >
> > > > > struct renesas_i3c_i2c_dev_data { @@ -272,10 +275,6 @@ struct
> > > > > renesas_i3c_irq_desc {
> > > > > const char *desc;
> > > > > };
> > > > >
> > > > > -struct renesas_i3c_config {
> > > > > - unsigned int has_pclkrw:1;
> > > > > -};
> > > > > -
> > > > > static inline void renesas_i3c_reg_update(void __iomem *reg, u32
> > > > > mask, u32 val) {
> > > > > u32 data = readl(reg);
> > > > > @@ -489,7 +488,7 @@ static int renesas_i3c_bus_init(struct i3c_master_controller *m)
> > > > > int od_high_ticks, od_low_ticks, i2c_total_ticks;
> > > > > int ret;
> > > > >
> > > > > - rate = clk_get_rate(i3c->tclk);
> > > > > + rate = clk_get_rate(i3c->clks[RENESAS_I3C_TCLK_IDX].clk);
> > > > > if (!rate)
> > > > > return -EINVAL;
> > > > >
> > > > > @@ -1302,13 +1301,8 @@ static int renesas_i3c_probe(struct
> > > > > platform_device *pdev) {
> > > > > struct renesas_i3c *i3c;
> > > > > struct reset_control *reset;
> > > > > - struct clk *clk;
> > > > > - const struct renesas_i3c_config *config = of_device_get_match_data(&pdev->dev);
> > > > > int ret, i;
> > > > >
> > > > > - if (!config)
> > > > > - return -ENODATA;
> > > > > -
> > > > > i3c = devm_kzalloc(&pdev->dev, sizeof(*i3c), GFP_KERNEL);
> > > > > if (!i3c)
> > > > > return -ENOMEM;
> > > > > @@ -1317,19 +1311,11 @@ static int renesas_i3c_probe(struct platform_device *pdev)
> > > > > if (IS_ERR(i3c->regs))
> > > > > return PTR_ERR(i3c->regs);
> > > > >
> > > > > - clk = devm_clk_get_enabled(&pdev->dev, "pclk");
> > > > > - if (IS_ERR(clk))
> > > > > - return PTR_ERR(clk);
> > > > > -
> > > > > - if (config->has_pclkrw) {
> > > > > - clk = devm_clk_get_enabled(&pdev->dev, "pclkrw");
> > > > > - if (IS_ERR(clk))
> > > > > - return PTR_ERR(clk);
> > > > > - }
> > > > > + ret = devm_clk_bulk_get_all_enabled(&pdev->dev, &i3c->clks);
> > > > > + if (ret < 0)
> > > > > + return ret;
> > > > >
> > > > > - i3c->tclk = devm_clk_get_enabled(&pdev->dev, "tclk");
> > > > > - if (IS_ERR(i3c->tclk))
> > > > > - return PTR_ERR(i3c->tclk);
> > > > > + i3c->num_clks = ret;
> > > >
> > > > Need check num_clks > RENESAS_I3C_TCLK_IDX to avoid outbound access
> > > > at
> > > > i3c->clks[RENESAS_I3C_TCLK_IDX].clk
> > >
> > > I guess dt binding check validate this as well. Eg: a single clk
> > > defined in the DT instead of minimum 2, will give DT warnings.
> > >
> > > Do you expect additional check in C code as well?
> >
> > Yes, worry about a wrong dtb cause kernel crash. Direct access
> > i3c->clks[RENESAS_I3C_TCLK_IDX] without check is risk. if clock wrong
> > i3c->in
> > dtb,generally, it just impact function. but this may cause crash. So I suggest add addtional check
> > here.
>
> OK, to avoid a crash num_clks > RENESAS_I3C_TCLK_IDX check is sufficient
Yes,
> But it does not check whether tclk in 0th entry or first entry.
>
> >
> > Or search 'tclk' in array i3c->clks.
> > for (i = 0; i < i3c->num_clks; i++)
> > if (!strcmp("tclk", i3c->clks[i]->id))
> > break;
>
> But this returns correct index of the "tclk"
This is just more flexiable for clk schema. If your schema is simple enough
check num_clks > RENESAS_I3C_TCLK_IDX should be enough.
Frank
>
> Cheers,
> Biju
next prev parent reply other threads:[~2026-01-06 15:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 10:49 [PATCH v4 0/4] i3c: renesas: Add suspend/resume support Tommaso Merciai
2026-01-05 10:49 ` [PATCH v4 1/4] i3c: renesas: Switch to clk_bulk API and store clocks in private data Tommaso Merciai
2026-01-05 17:11 ` Frank Li
2026-01-05 18:06 ` Biju Das
2026-01-06 14:49 ` Frank Li
2026-01-06 15:01 ` Biju Das
2026-01-06 15:17 ` Frank Li [this message]
2026-01-06 15:41 ` Biju Das
2026-01-06 15:54 ` Alexandre Belloni
2026-01-05 10:50 ` [PATCH v4 2/4] i3c: renesas: Store clock rate and reset controls in struct renesas_i3c Tommaso Merciai
2026-01-05 10:53 ` Biju Das
2026-01-05 11:15 ` Tommaso Merciai
2026-01-05 10:50 ` [PATCH v4 3/4] i3c: renesas: Factor out hardware initialization to separate function Tommaso Merciai
2026-01-05 10:50 ` [PATCH v4 4/4] i3c: renesas: Add suspend/resume support Tommaso Merciai
2026-01-05 17:15 ` 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=aV0neUGcqiGkE/Sv@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=tomm.merciai@gmail.com \
--cc=tommaso.merciai.xr@bp.renesas.com \
--cc=wsa+renesas@sang-engineering.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®