On 06/15, Ricardo Ribalda Delgado wrote:
> Hi Stephen
>
> Assume this device tree overlay:
>
>
> &bus0{
>
> axi_clk: axi_clk {
> compatible = "fixed-clock";
> #clock-cells = <0x0>;
> clock-frequency = <12500>;
> };
>
> iic_0: iic {
> #address-cells = <1>;
> #size-cells = <1>;
> compatible
Hi Stephen
Assume this device tree overlay:
&bus0{
axi_clk: axi_clk {
compatible = "fixed-clock";
#clock-cells = <0x0>;
clock-frequency = <12500>;
};
iic_0: iic {
#address-cells = <1>;
#size-cells = <1>;
compatible = "xlnx,xps-iic-2.00.a";
reg = < 0x0003 0x1 >;
interrupt-parent = <
On 06/08, Ricardo Ribalda Delgado wrote:
> When clock providers are added to the device tree after of_clk_init is called
> they are not added to the clock provider list. This makes that drivers such
> as i2c-xiic.c fail to init, as they may depend on the unadded clock provider.
Who's the provider
When clock providers are added to the device tree after of_clk_init is called
they are not added to the clock provider list. This makes that drivers such
as i2c-xiic.c fail to init, as they may depend on the unadded clock provider.
We first introduce a new function clk.c that will check if a devic
4 matches
Mail list logo