; dev; ret =
uclass_next_device()) {
puts("gpio-uclass loop\n");
...
puts inside loop is never executed, that's why I asked if I should maybe
first declare GPIOs to the system via device tree.
On Thu, Aug 15, 2019 at 4:05 PM Nemanja Savic wrote:
> It return -2 which should be -ENOENT. In
Hi all,
I am struggling with porting our old board init code for a sabre auto based
custom board with i.MX6 DualLite processor. The code used to work in our
older u-boot version, but what I saw in mx6qsabreauto.c is that the new
style is by using new driver model which means the gpio should be
19 at 7:46 AM Nemanja Savic wrote:
> >
> > Hi all,
> >
> > I am struggling with porting our old board init code for a sabre auto
> based
> > custom board with i.MX6 DualLite processor. The code used to work in our
> > older u-boot version, but what I saw in m
This is solved. Namely, I called gpio_request from checkboard function, and
it seems like at that point it is not possible to use gpios. When I moved
my code to board_init it started working fine.
On Thu, Aug 15, 2019 at 4:18 PM Nemanja Savic wrote:
> And to be more precise inside gpio-uclas
Hi all list members,
this is my first post. I am almost new to u-boot, which means that a few
times in my life I had tasks to implement some commands and perform
initialization of GPIOS, etc. In summary very simple tasks. Now I have a
bit harder tasks - to update from version 2015.04 to 2017.03.
Thank you Adam for your answer. Sounds like a good starting point for me.
Additionally I would like to ask you further questions regarding your
answers.
> 3. Is device tree used by u-boot the same device tree later used by linu
>
>> > kernel?
>>
>> On my imx6q_logic board, the device tree is
6 matches
Mail list logo
