Hi Thomas,
On ven., sept. 29 2017, Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx> wrote:
> Hello,
>
> On Fri, 29 Sep 2017 11:13:00 +0200, Gregory CLEMENT wrote:
>
>> >> - clock-names:
>> >> Array of names corresponding to clocks property.
>> >> The input clock for Xenon IP core should be named as "core".
>> >> + The input clock for the AXI bus must be named as "axi".
>> >
>> > Is "bus" more suitable?
>>
>> I find bus too vague.
>
> Actually no, I believe "bus" is more common. Indeed, you could have the
> same IP, attached to a different interconnect I guess.
>
>> >> /*
>> >> * Link Xenon specific mmc_host_ops function,
>> >> @@ -491,9 +493,20 @@ static int xenon_probe(struct platform_device *pdev)
>> >> if (err)
>> >> goto free_pltfm;
>> >>
>> >> + priv->axi_clk = devm_clk_get(&pdev->dev, "axi");
>> >> + if (IS_ERR(priv->axi_clk)) {
>
> -EPROBE_DEFER handling ?
See
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-September/533510.html
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com