From: Junyi Zhao <junyi.zhao@amlogic.com>
To: Frank Li <Frank.li@oss.nxp.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Frank Li <Frank.Li@nxp.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-i3c@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, imx@lists.linux.dev,
linux-hardening@vger.kernel.org, xianwei.zhao@amlogic.com,
Kelvin.Zhang@amlogic.com
Subject: Re: [PATCH v2 1/2] i3c: master: svc: Add amlogic a9 support
Date: Wed, 4 Nov 2026 13:18:45 +0800 [thread overview]
Message-ID: <e2b65a8f-a1c3-47f6-896d-22884907d7b1@amlogic.com> (raw)
In-Reply-To: <auqkKAKRZZ0pA-R3@SMW015318>
Hi Frank,
thanks for your detail.
On 04/11/2026 11:19, Frank Li wrote:
> [ EXTERNAL EMAIL ]
>
> On Wed, Nov 04, 2026 at 10:44:59AM +0800, Junyi Zhao wrote:
>> Hi Frank,
>>
>> Thanks for the review.
>>
>> On 03/11/2026 06:10, Frank Li wrote:
>>> [ EXTERNAL EMAIL ]
>>>
>>> On Mon, Nov 02, 2026 at 07:05:39PM +0800, Junyi Zhao wrote:
>>>> Amlogic a9 SoCs integrate the Silvaco I3C IP, and their peripheral
>>>> clocks vary from the vanilla implementation:
>>>>
>>>> - The EE-domain controller (amlogic,a9-i3c) takes two clocks,
>>>> "pclk" and "fast_clk", and the fast clock rate must be
>>>> programmed before the controller can be used.
>>>>
>>>> - The AO-domain controller (amlogic,a9-ao-i3c) exposes only "pclk":
>>>> its bus clock is generated by an internal divider located in the
>>>> controller's own register space.
>>>>
>>>> Add a vendor_init callback to handle this clock setup.
>>>> Add a vendor_quirks field to describe AO-specific behavior.
>>>>
>>>> Signed-off-by: Junyi Zhao <junyi.zhao@amlogic.com>
>>>> ---
> ...
>>>> + int (*vendor_init)(struct svc_i3c_master *master);
>>>> +};
>>>> +
>>>
>>> why need move this struct
>>
>> because callback need param struct svc_i3c_master *master, and if not,
>> compile error. undefined.
>
> Most likely svc_i3c_master need save a point for drvdata in future.
>
> You add forward declear before drvdata
>
> struct svc_i3c_drvdata;
>
will do.
>>
> ...
>>>> +static int aml_ao_i3c_tail_clocks(struct svc_i3c_master *master, struct clk *parent)
>>>> +{
>>>> + struct device *dev = master->dev;
>>>> + struct aml_i3c_ao_clk *ao;
>>>> + struct clk_init_data init = {};
>>>> + char name[64];
>>>> + int ret;
>>>> + struct clk_bulk_data *new_clks;
>>>> + struct clk *fclk;
>>>
>>> keep revise Chemistry order
>>>
>> will change order:
>> struct aml_i3c_ao_clk *ao;
>> struct clk *fclk;
>> struct clk_bulk_data *new_clks;
>> struct device *dev = master->dev;
>> struct clk_init_data init = {};
>> char name[64];
>> int ret;
>
>
> longest is first
>
> struct device *dev = master->dev;
> struct clk_bulk_data *new_clks;
> struct clk_init_data init = {};
> struct aml_i3c_ao_clk *ao;
> struct clk *fclk;
> char name[64];
> int ret;
>
will do. thanks the detail.
>
> Frank
next prev parent reply other threads:[~2026-11-04 5:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 11:05 [PATCH v2 0/2] Add Amlogic A9 I3C support Junyi Zhao via B4 Relay
2026-11-02 11:05 ` [PATCH v2 1/2] i3c: master: svc: Add amlogic a9 support Junyi Zhao via B4 Relay
2026-11-02 22:10 ` Frank Li
2026-11-04 2:44 ` Junyi Zhao
2026-11-04 3:19 ` Frank Li
2026-11-04 5:18 ` Junyi Zhao [this message]
2026-11-02 11:05 ` [PATCH v2 2/2] dt-bindings: i3c: silvaco,i3c-master: Add Amlogic A9 support Junyi Zhao via B4 Relay
2026-11-02 21:44 ` Frank Li
2026-11-04 2:45 ` Junyi Zhao
2026-11-02 21:48 ` Frank Li
2026-11-04 2:47 ` Junyi Zhao
2026-11-03 11:42 ` Krzysztof Kozlowski
2026-11-04 2:56 ` Junyi Zhao
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=e2b65a8f-a1c3-47f6-896d-22884907d7b1@amlogic.com \
--to=junyi.zhao@amlogic.com \
--cc=Frank.Li@nxp.com \
--cc=Frank.li@oss.nxp.com \
--cc=Kelvin.Zhang@amlogic.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gustavoars@kernel.org \
--cc=imx@lists.linux.dev \
--cc=jbrunet@baylibre.com \
--cc=kees@kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=miquel.raynal@bootlin.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=xianwei.zhao@amlogic.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®