From: Jerome Brunet <jbrunet@baylibre.com>
To: Yu Tu <yu.tu@amlogic.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: "kelvin . zhang" <Kelvin.Zhang@amlogic.com>,
"qi . duan" <qi.duan@amlogic.com>
Subject: Re: [PATCH V6 3/3] clk: meson: s4: add support for Amlogic S4 SoC peripheral clock controller
Date: Mon, 30 Jan 2023 10:06:49 +0100 [thread overview]
Message-ID: <1jy1pko0fc.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <a4ad6ac6-60c2-8f7b-fdb0-509de31db282@amlogic.com>
On Sat 28 Jan 2023 at 18:17, Yu Tu <yu.tu@amlogic.com> wrote:
> On 2023/1/20 17:47, Jerome Brunet wrote:
>> [ EXTERNAL EMAIL ]
>> On Fri 20 Jan 2023 at 11:33, Yu Tu <yu.tu@amlogic.com> wrote:
>>
>>> Hi
>>> On 2023/1/19 19:37, Jerome Brunet wrote:
>>>> [ EXTERNAL EMAIL ]
>>>> On Mon 16 Jan 2023 at 15:42, Yu Tu <yu.tu@amlogic.com> wrote:
>>>>
>>>>> Add the peripherals clock controller driver in the s4 SoC family.
>>>>>
>>>>> Signed-off-by: Yu Tu <yu.tu@amlogic.com>
>>>> [...]
>>>>
>>>>> +
>>>>> +/* Video Clocks */
>>>>> +static struct clk_regmap s4_vid_pll_div = {
>>>>> + .data = &(struct meson_vid_pll_div_data){
>>>>> + .val = {
>>>>> + .reg_off = CLKCTRL_VID_PLL_CLK_DIV,
>>>>> + .shift = 0,
>>>>> + .width = 15,
>>>>> + },
>>>>> + .sel = {
>>>>> + .reg_off = CLKCTRL_VID_PLL_CLK_DIV,
>>>>> + .shift = 16,
>>>>> + .width = 2,
>>>>> + },
>>>>> + },
>>>>> + .hw.init = &(struct clk_init_data) {
>>>>> + .name = "vid_pll_div",
>>>>> + /*
>>>>> + * The frequency division from the hdmi_pll clock to the vid_pll_div
>>>>> + * clock is the default value of this register. When designing the
>>>>> + * video module of the chip, a default value that can meet the
>>>>> + * requirements of the video module will be solidified according
>>>>> + * to the usage requirements of the chip, so as to facilitate chip
>>>>> + * simulation. So this is ro_ops.
>>>>> + * It is important to note that this clock is not used on this
>>>>> + * chip and is described only for the integrity of the clock tree.
>>>>> + */
>>>> If it is reset value and will be applicable to all the design, regarless
>>>> of the use-case, then yes RO ops is OK
>>>>
>>>> >From what I understand here, the value will depend on the use-case requirements.
>>>> This is a typical case where the DT prop "assigned-rate" should be used, not RO ops.
>>>
>>> Check the previous chip history, the actual scene is not used at all,
>>> basically is used in simulation. So the previous SOC was "ro_ops" without
>>> any problems. This S4 SOC is not actually useful either.
>>>
>>> So when you were upstream, you had no problem making "ro_ops". I wonder if
>>> I could delete this useless clock, so you don't have to worry about it.
>> I don't know what to make of this. What is the point of adding a useless
>> clock ?
>
> As explained earlier this "vid_pll_div" is actually used in chip
> emulation. So next I'd like to know what you suggest to do with the clock?
>
If it does not exist in the actual SoC, please remove it
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-01-30 9:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 7:42 [PATCH V6 0/3] Add S4 SoC PLL and Peripheral clock controller Yu Tu
2023-01-16 7:42 ` [PATCH V6 1/3] dt-bindings: clock: document Amlogic S4 SoC PLL & peripheral " Yu Tu
2023-01-16 8:29 ` Krzysztof Kozlowski
2023-01-16 9:31 ` Yu Tu
2023-01-19 0:38 ` Kevin Hilman
2023-01-20 2:25 ` Yu Tu
2023-01-25 0:25 ` Kevin Hilman
2023-01-28 8:19 ` Yu Tu
2023-01-20 9:37 ` Jerome Brunet
2023-01-28 8:23 ` Yu Tu
2023-01-16 7:42 ` [PATCH V6 2/3] clk: meson: S4: add support for Amlogic S4 SoC PLL clock driver Yu Tu
2023-01-19 11:20 ` Jerome Brunet
2023-01-20 2:58 ` Yu Tu
2023-01-20 9:43 ` Jerome Brunet
2023-01-28 8:36 ` Yu Tu
2023-01-16 7:42 ` [PATCH V6 3/3] clk: meson: s4: add support for Amlogic S4 SoC peripheral clock controller Yu Tu
2023-01-19 11:37 ` Jerome Brunet
2023-01-20 3:33 ` Yu Tu
2023-01-20 9:47 ` Jerome Brunet
2023-01-28 10:17 ` Yu Tu
2023-01-30 9:06 ` Jerome Brunet [this message]
2023-01-30 9:41 ` Yu Tu
2023-01-30 9:47 ` Jerome Brunet
2023-01-30 9:59 ` Yu Tu
2023-01-30 10:07 ` Jerome Brunet
2023-01-31 3:29 ` Yu Tu
2023-01-19 11:18 ` [PATCH V6 0/3] Add S4 SoC PLL and Peripheral " Jerome Brunet
2023-01-20 2:31 ` Yu Tu
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=1jy1pko0fc.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=Kelvin.Zhang@amlogic.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=qi.duan@amlogic.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=yu.tu@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