Re: am335x: GPIOs in userspace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, May 27, 2022 at 1:01 PM Yegor Yefremov
<yegorslists@xxxxxxxxxxxxxx> wrote:
>
> I have the following problem. The latest kernel version I am using for
> my devices is 5.4.x. In my DTS I don't explicitly expose the GPIOs to
> the usespace but I can read input both via sysfs as also libgpiod API.
>
> With the newest kernel like 5.17 or 5.18, I can read the same input
> pin but I always read 0. I have also tried to add my GPIOs as
> "default" into the am33xx_pinmux section (the way it is done in [1]) but
> it didn't help.
>
> [1] https://patchwork.kernel.org/project/linux-omap/patch/20200712103717.1219765-1-drew@xxxxxxxxxxxxxxx/
>
> Regards,
> Yegor

Hello Yegor,

Which am335x board are you using?  Is it the PocketBeagle?

Have you tried reverting abe4e4675dfc ("ARM: dts: am335x-pocketbeagle:
set default mux for gpio pins") to see if the results change?

Please post the dts files you created or modified so I can better
familiarize myself with your environment.

Unfortunately, I'm currently traveling with only a BeagleBone Black,
but it might be useful for testing depending on what the issue is.

Thanks,
Drew



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux