All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerome Brunet <jbrunet@baylibre.com>
To: Stephen Boyd <sboyd@kernel.org>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	ulf.hansson@linaro.org
Cc: linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org
Subject: clk: clk_register is deprecated
Date: Thu, 30 Apr 2020 14:24:41 +0200	[thread overview]
Message-ID: <1jftcli2k6.fsf@starbuckisacylon.baylibre.com> (raw)

Hi Stephen,

We have a question regarding drivers which register clocks in CCF and
later need to use these clocks.

So far, these drivers had been using clk_register() to get a 'struct
clk*' they could later use with the linux/clk.h API.

Now that this clk_register() is deprecated in favor of
clk_hw_register(), how are these driver supposed to get the per-user
"struct clk*" they need ?

In this mmc thread [0] Martin proposed to go through a provider. I think
it is overkill, especially for a device which will not provide its clocks
to any other device.

They other way available is "hw->clk". I suspect it is not recommended
to do so, is it ?

If not, what would be the recommended way to get the "struct clk*" from
a newly registered "struct clk_hw *" ? Should we add something new to
clk-provider.h API ?

Cheers
Jerome

[0]: https://lore.kernel.org/linux-amlogic/20200428210229.703309-3-martin.blumenstingl@googlemail.com

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

WARNING: multiple messages have this Message-ID (diff)
From: Jerome Brunet <jbrunet@baylibre.com>
To: Stephen Boyd <sboyd@kernel.org>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	ulf.hansson@linaro.org
Cc: linux-clk@vger.kernel.org, linux-amlogic@lists.infradead.org
Subject: clk: clk_register is deprecated
Date: Thu, 30 Apr 2020 14:24:41 +0200	[thread overview]
Message-ID: <1jftcli2k6.fsf@starbuckisacylon.baylibre.com> (raw)

Hi Stephen,

We have a question regarding drivers which register clocks in CCF and
later need to use these clocks.

So far, these drivers had been using clk_register() to get a 'struct
clk*' they could later use with the linux/clk.h API.

Now that this clk_register() is deprecated in favor of
clk_hw_register(), how are these driver supposed to get the per-user
"struct clk*" they need ?

In this mmc thread [0] Martin proposed to go through a provider. I think
it is overkill, especially for a device which will not provide its clocks
to any other device.

They other way available is "hw->clk". I suspect it is not recommended
to do so, is it ?

If not, what would be the recommended way to get the "struct clk*" from
a newly registered "struct clk_hw *" ? Should we add something new to
clk-provider.h API ?

Cheers
Jerome

[0]: https://lore.kernel.org/linux-amlogic/20200428210229.703309-3-martin.blumenstingl@googlemail.com

             reply	other threads:[~2020-04-30 12:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 12:24 Jerome Brunet [this message]
2020-04-30 12:24 ` clk: clk_register is deprecated Jerome Brunet
2020-05-04 17:16 ` Stephen Boyd
2020-05-04 17:16   ` Stephen Boyd
2020-05-05 16:03   ` Jerome Brunet
2020-05-05 16:03     ` Jerome Brunet
2020-05-05 19:10     ` Stephen Boyd
2020-05-05 19:10       ` Stephen Boyd

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=1jftcli2k6.fsf@starbuckisacylon.baylibre.com \
    --to=jbrunet@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=sboyd@kernel.org \
    --cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.