On 10/25/19 10:18 AM, Vignesh Raghavendra wrote:
> Some boards don't populate clk/reset entries as these are are optional
> as per binding documentation. Therefore, don't fail driver probe if
> clk/reset entries are absent in DT.
>
> This fixes fastboot failures seen due to enabling of CONFIG_CLK
+ Praneeth
On Fri, Oct 25, 2019 at 1:08 PM Sam Protsenko
wrote:
>
> Hi Vignesh,
>
> On Fri, Oct 25, 2019 at 11:17 AM Vignesh Raghavendra wrote:
> >
> > Some boards don't populate clk/reset entries as these are are optional
> > as per binding documentation. Therefore, don't fail driver probe if
>
Hi Vignesh,
On Fri, Oct 25, 2019 at 11:17 AM Vignesh Raghavendra wrote:
>
> Some boards don't populate clk/reset entries as these are are optional
> as per binding documentation. Therefore, don't fail driver probe if
> clk/reset entries are absent in DT.
>
> This fixes fastboot failures seen due
On 25/10/2019 11:18, Vignesh Raghavendra wrote:
Some boards don't populate clk/reset entries as these are are optional
as per binding documentation. Therefore, don't fail driver probe if
clk/reset entries are absent in DT.
This fixes fastboot failures seen due to enabling of CONFIG_CLK on AM57xx
Some boards don't populate clk/reset entries as these are are optional
as per binding documentation. Therefore, don't fail driver probe if
clk/reset entries are absent in DT.
This fixes fastboot failures seen due to enabling of CONFIG_CLK on AM57xx
Fixes: e8e683d33b0c ("board: ti: am57xx-idk: Con
5 matches
Mail list logo