public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuan Liu <chuan.liu@amlogic.com>
To: Dmitry Rokosov <ddrokosov@salutedevices.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Kevin Hilman <khilman@baylibre.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [DMARC error][DKIM error]Re: [PATCH 3/3] clk: amlogic: s4: remove unused data
Date: Tue, 24 Dec 2024 13:20:14 +0800	[thread overview]
Message-ID: <4e4808ee-07f2-43db-b7f8-e9362c9898e4@amlogic.com> (raw)
In-Reply-To: <20241223090137.jbzwrlazhkumatfx@CAB-WSD-L081021>

hi Dmitry:


On 12/23/2024 5:01 PM, Dmitry Rokosov wrote:
> [You don't often get email from ddrokosov@salutedevices.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> [ EXTERNAL EMAIL ]
>
> Hello Chuan!
>
> On Mon, Dec 23, 2024 at 03:59:07PM +0800, Chuan Liu wrote:
>> Hi Jerome:
>>
>> Thank you for pointing out.
>>
>>
>> On 12/21/2024 1:17 AM, Jerome Brunet wrote:
>>> [ EXTERNAL EMAIL ]
>>>
>>> Following the removal of the big clk_regmap clock table from the
>>> s4-peripherals clock controller driver, it appears some clocks are unused,
>>> which means these are not exported or even registered.
>>
>> I have confirmed here that these clocks are used for the demodulator
>> of DTV (Digital Television). The DTV-related driver will use these
>> clocks.
>>
>>
>>> In all likelihood, these clocks have not been tested. Remove the unused
>>> clocks for now. These can added back later when they have been properly
>>> tested.
>>
>> I will complete these clocks later after testing.
> Are you planning to submit the DTV drivers that will utilize these
> clocks to the upstream?


I have learned that there is no plan for now. It is uncertain whether
it will be submitted upstream in the later stage.


>
> If I correctly interpret Jerome's patch series, it appears that these
> clocks will not be applied to the upstream kernel unless there are
> clients present in the future.


Jerome deleted these clocks because they were defined in the driver
but were not referenced and registered.

These clocks should be added to "s4d_hw_onecell_data" to be registered.
They were omitted when the driver was submitted previously.


> Please correct me if I'm wrong.
>
> [...]
>
> --
> Thank you,
> Dmitry

      reply	other threads:[~2024-12-24  5:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 17:17 [PATCH 0/3] clk: amlogic: drop clk_regmap tables Jerome Brunet
2024-12-20 17:17 ` [PATCH 1/3] clk: add a clk_hw helper to get the associate device structure Jerome Brunet
2024-12-20 23:55   ` Stephen Boyd
2024-12-20 17:17 ` [PATCH 2/3] clk: amlogic: drop clk_regmap tables Jerome Brunet
2024-12-21  0:12   ` Stephen Boyd
2024-12-21 11:09     ` Jerome Brunet
2024-12-31  1:08       ` Stephen Boyd
2025-01-06 10:12         ` Jerome Brunet
2025-01-06 21:09           ` Stephen Boyd
2025-01-07 14:46             ` Jerome Brunet
2025-01-07 21:28               ` Stephen Boyd
2025-01-15 15:58                 ` Jerome Brunet
2025-02-27 22:55                   ` Stephen Boyd
2025-03-21 15:46                     ` Jerome Brunet
2025-03-21 15:55                       ` Jerome Brunet
2024-12-20 17:17 ` [PATCH 3/3] clk: amlogic: s4: remove unused data Jerome Brunet
2024-12-23  7:59   ` Chuan Liu
2024-12-23  9:01     ` [DMARC error][DKIM error]Re: " Dmitry Rokosov
2024-12-24  5:20       ` Chuan Liu [this message]

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=4e4808ee-07f2-43db-b7f8-e9362c9898e4@amlogic.com \
    --to=chuan.liu@amlogic.com \
    --cc=ddrokosov@salutedevices.com \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --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=sboyd@kernel.org \
    /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