[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<PH7PR12MB7284595E5D409486D91118768A6A2@PH7PR12MB7284.namprd12.prod.outlook.com>
Date: Tue, 9 Jan 2024 11:24:37 +0000
From: "Trivedi Manojbhai, Naman" <Naman.TrivediManojbhai@....com>
To: Stephen Boyd <sboyd@...nel.org>, "abel.vesa@...aro.org"
<abel.vesa@...aro.org>, "angelogioacchino.delregno@...labora.com"
<angelogioacchino.delregno@...labora.com>, "Simek, Michal"
<michal.simek@....com>, "mturquette@...libre.com" <mturquette@...libre.com>,
"robh@...nel.org" <robh@...nel.org>
CC: "linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] drivers: clk: zynqmp: remove clock name dependency
Hi Stephen,
Thanks for review. Please find my response inline.
Thanks,
Naman
>-----Original Message-----
>From: Stephen Boyd <sboyd@...nel.org>
>Sent: Thursday, January 4, 2024 6:30 AM
>To: Trivedi Manojbhai, Naman <Naman.TrivediManojbhai@....com>;
>abel.vesa@...aro.org; angelogioacchino.delregno@...labora.com;
>krzysztof.kozlowski@...aro.org; Simek, Michal <michal.simek@....com>;
>mturquette@...libre.com; robh@...nel.org
>Cc: linux-clk@...r.kernel.org; linux-arm-kernel@...ts.infradead.org; linux-
>kernel@...r.kernel.org; Trivedi Manojbhai, Naman
><Naman.TrivediManojbhai@....com>
>Subject: Re: [PATCH] drivers: clk: zynqmp: remove clock name dependency
>
>Caution: This message originated from an External Source. Use proper caution
>when opening attachments, clicking links, or responding.
>
>
>Quoting Naman Trivedi Manojbhai (2024-01-02 23:20:17)
>> Currently, from zynqmp_get_parent_list() function the clock driver
>> references the clock by name instead of its reference from device tree.
>> This causes problem when the clock name in the device tree is changed.
>>
>> Remove hard dependency of clock name and update the logic to use clock
>> reference from device tree instead of clock name.
>
>Please use struct clk_parent_data instead.
Can you please clarify how struct clk_parent_data can be used here?
The zynqmp clock driver receives clock parent information from firmware and it is stored in struct clock_parent. In this patch, I added logic to get the parent clock reference from device tree and get corresponding clock name. Can you please explain how the struct clk_parent_data can be used for the same?
Thanks,
Naman
Powered by blists - more mailing lists