u-boot.git/include/clk.h, branch v2022.01

clk: fix clk_get_rate() documentation

2021-12-15T17:16:15+00:00

Improve clk_get_rate() @return documentation that otherwise is a bit
ambiguous. At the moment I expect to return 0 as error since the return
type is 'ulong', instead the function really returns negative value in
case the corresponding function pointer is null and returns 0 if the clock
is invalid.

Signed-off-by: Giulio Benetti 
Reviewed-by: Sean Anderson

clk: Rename clk_get_by_driver_info()

2021-09-25T15:46:15+00:00

This is actually a misnomer now, since the phandle info may contain
a driver_info index or a udevice index. Rename it to use the word
'phandle', which seems more accurate. Add a comment while we are here.

Also add a test for this function.

Signed-off-by: Simon Glass

treewide: Simply conditions with the new OF_REAL

2021-09-25T15:46:15+00:00

Use this new Kconfig to simplify the compilation conditions where
appropriate.

Signed-off-by: Simon Glass

clk: Allow force setting clock defaults before relocation

2021-06-17T01:40:57+00:00

Since 291da96b8e ("clk: Allow clock defaults to be set during re-reloc
state for SPL only") it has been impossible to set clock defaults before
relocation. This is annoying on boards without SPL, since there is no way
to set clock defaults before U-Boot proper. In particular, the aisram rate
must be changed before relocation on the K210, since U-Boot will hang if we
try and change the rate while we are using aisram.

To get around this, extend the stage parameter to allow force setting
defaults, even if they would be otherwise postponed for later. A device
tree property was decided against because of the concerns in the original
commit thread about the overhead of repeatedly parsing the device tree.

Signed-off-by: Sean Anderson 
Reviewed-by: Simon Glass

clk: add clk_round_rate()

2021-01-12T05:28:04+00:00

It returns the rate which will be set if you ask clk_set_rate() to set
that rate. It provides a way to query exactly what rate you'll get if
you call clk_set_rate() with that same argument.
So essentially, clk_round_rate() and clk_set_rate() are equivalent
except the former does not modify the clock hardware in any way.

Signed-off-by: Dario Binacchi 
Reviewed-by: Simon Glass 
Reviewed-by: Sean Anderson

dtoc: extend dtoc to use struct driver_info when linking nodes

2020-07-10T04:00:29+00:00

In the current implementation, when dtoc parses a dtb to generate a struct
platdata it converts the information related to linked nodes as pointers
to struct platdata of destination nodes. By doing this, it makes
difficult to get pointer to udevices created based on these
information.

This patch extends dtoc to use struct driver_info when populating
information about linked nodes, which makes it easier to later get
the devices created. In this context, reimplement functions like
clk_get_by_index_platdata() which made use of the previous approach.

Signed-off-by: Walter Lozano 
Reviewed-by: Simon Glass

clk: Fix clk func names in comments

2020-05-10T20:00:49+00:00

clk function names in comments should be prefix with
clk instead of clock.

Fix it.

Cc: Simon Glass 
Cc: Tom Rini 
Signed-off-by: Jagan Teki 
Reviewed-by: Simon Glass

dm: clk: add stub when CONFIG_CLK is deactivated

2020-04-28T11:52:52+00:00

Add stub for functions clk_...() when CONFIG_CLK is deactivated.

This patch avoids compilation issues for driver using these API
without protection (#if CONFIG_IS_ENABLED(CLK))

For example, before this patch we have undefined reference to
`clk_disable_bulk') for code:
  clk_disable_bulk(&priv->clks);
  clk_release_bulk(&priv->clks);

Signed-off-by: Patrick Delaunay

clk: add APIs to get (optional) clock by name without a device

2020-01-16T14:39:45+00:00

Sometimes we may need get (optional) clock without a device,
that means use ofnode.
e.g. when the phy node has subnode, and there is no device created
for subnode, in this case, we need these new APIs to get subnode's
clock.

Signed-off-by: Chunfeng Yun 
Reviewed-by: Simon Glass 
Reviewed-by: Ryder Lee

drivers: clk: Fix using assigned-clocks in the node of the clock it sets up

2019-10-22T14:14:05+00:00

This fixes the case where assigned-clocks is used to define a clock
defaults inside this same clock's node. This is used sometimes to setup a
default parents and/or rate for a clock.

example:
muxed_clock: muxed_clock {
	clocks = <&clk_provider 0>, <&clk_provider 1>;
	#clock-cells = <0>;
	assigned-clocks = <&muxed_clock>;
	assigned-clock-parents = <&clk_provider 1>;
};

It doesn't work in u-boot because the assigned-clocks are setup *before*
the clock is probed. (clk_set_parent() will likely crash or fail if called
before the device probe function)
Making it work by handling "assigned-clocks" in 2 steps: first before the
clk device is probed, and then after the clk device is probed.

Signed-off-by: Jean-Jacques Hiblot