From: Bremenpl <bremenpl@gmail.com>
To: Jon Cormier <jcormier@criticallink.com>
Cc: <meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti] [kirkstone] libgpiod-tools gpioinfo missing for beaglebone
Date: Sat, 13 Jan 2024 10:23:06 +0100 [thread overview]
Message-ID: <18d0221c8a8.284e.a291efdfec6f8802d64589cd992131fb@gmail.com> (raw)
In-Reply-To: <17A9934C6E495BDF.31870@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 12874 bytes --]
Hi Jon,
Robert confirmed your findngs and already pushed the changes to another
repo (I guess pipelined). Still figuring out how to sync it with the
kirkstone repo. Thanks for your help!
https://forum.beagleboard.org/t/libgpiod-tools-gpioinfo-missing-for-beaglebone/37086/2
On January 12, 2024 11:38:11 "Lukasz Przenioslo via lists.yoctoproject.org"
<bremenpl=gmail.com@lists.yoctoproject.org> wrote:
> Thanks for the answer Jon,
> I must double confirm this then... I recall that on kirkstone:
> There were no labels in both meta-ti-bsp and meta-yocto-bsp,
> They were missing for both dts (black and green).
> Will check this with the author (Robert C Nelson) and also test it tomorrow
> and let you know.
>
> --
> Łukasz Przeniosło
>
>
> ------ Original Message ------
> From "Jon Cormier" <jcormier@criticallink.com>
> To "Bremenpl" <bremenpl@gmail.com>
> Cc meta-ti@lists.yoctoproject.org
> Date 2024-01-11 19:25:37
> Subject Re: [meta-ti] [kirkstone] libgpiod-tools gpioinfo missing for
> beaglebone
>
>> We can do a little digging to hopefully find out.
>>
>> Based on my checkout which may be newer or older than yours:
>> * According to meta-ti/meta-ti-bsp/conf/machine/beaglebone.conf, the kernel
>> recipe used is linux-bb.org.
>> * According to
>> meta-ti/meta-ti-bsp/recipes-kernel/linux/linux-bb.org_git.bb, the kernel
>> repo used is github.com/beagleboard/linux.git, branch v6.1.46-ti-r13.
>> * According to that repo, the boneblack should have the gpio-line-names and
>> the bonegreen doesn't...
>> https://github.com/beagleboard/linux/blob/6.1.46-ti-rt-r13/arch/arm/boot/dts/am335x-boneblack.dts
>> https://github.com/beagleboard/linux/blob/6.1.46-ti-rt-r13/arch/arm/boot/dts/am335x-bonegreen.dts
>>
>> To find out why you may have to ask them. Or look through the history to
>> find a commit about it.
>>
>>
>> On Thu, Jan 11, 2024 at 12:28 AM Bremenpl <bremenpl@gmail.com> wrote:
>> am335x-bonegreen.dts, can also be am335x-boneblack.dts, but the case here
>> is the same.
>>
>> On January 10, 2024 23:23:26 Jon Cormier <jcormier@criticallink.com> wrote:
>>> Which device tree file is your device loading?
>>>
>>> On Wed, Jan 10, 2024 at 5:07 PM Bremenpl <bremenpl@gmail.com> wrote:
>>> Hi Jonathan,
>>> Thank you for the answer.
>>>
>>> Yes it seems the dts file changed a bit between Dunfell and Kirkstone and
>>> these labers are now not there.
>>> Any idea why these were gotten rid of? As you mentioned they are usefull.
>>> Who should be contacted to potentially put them back in place in the repo
>>> (in case these were removed by error)?
>>> Thanks.
>>>
>>>
>>> On January 10, 2024 22:52:44 Jon Cormier <jcormier@criticallink.com> wrote:
>>>>
>>>>
>>>> On Fri, Jan 5, 2024 at 3:49 AM Lukasz Przenioslo <bremenpl@gmail.com> wrote:
>>>> Hello,
>>>> I have recently moved from Dunfell to Kirkstone for the beaglebone machine.
>>>> Since then I have noticed that calling gpioinfo from libgpiod-tools does
>>>> not show the gpio labels:
>>>>
>>>> ```
>>>> root@beaglebone:~# gpioinfo
>>>> gpiochip0 - 32 lines:
>>>> line 0: unnamed unused input active-high
>>>> line 1: unnamed unused input active-high
>>>> line 2: unnamed unused input active-high
>>>> line 3: unnamed unused input active-high
>>>> line 4: unnamed unused input active-high
>>>> line 5: unnamed unused input active-high
>>>> line 6: unnamed unused input active-high
>>>> line 7: unnamed unused input active-high
>>>> line 8: unnamed unused input active-high
>>>> line 9: unnamed unused input active-high
>>>> line 10: unnamed unused input active-high
>>>> line 11: unnamed unused input active-high
>>>> line 12: unnamed unused input active-high
>>>> line 13: unnamed unused input active-high
>>>> line 14: unnamed unused input active-high
>>>> line 15: unnamed unused input active-high
>>>> line 16: unnamed unused input active-high
>>>> line 17: unnamed unused input active-high
>>>> line 18: unnamed unused input active-high
>>>> line 19: unnamed unused input active-high
>>>> line 20: unnamed unused input active-high
>>>> line 21: unnamed "beaglebone:green:usr0" output active-high [used]
>>>> line 22: unnamed "beaglebone:green:usr1" output active-high [used]
>>>> line 23: unnamed "beaglebone:green:usr2" output active-high [used]
>>>> line 24: unnamed "beaglebone:green:usr3" output active-high [used]
>>>> line 25: unnamed unused input active-high
>>>> line 26: unnamed unused input active-high
>>>> line 27: unnamed unused input active-high
>>>> line 28: unnamed unused input active-high
>>>> line 29: unnamed unused input active-high
>>>> line 30: unnamed unused input active-high
>>>> line 31: unnamed unused input active-high
>>>> gpiochip1 - 32 lines:
>>>> line 0: unnamed unused input active-high
>>>> line 1: unnamed unused input active-high
>>>> line 2: unnamed unused input active-high
>>>> line 3: unnamed unused input active-high
>>>> line 4: unnamed unused input active-high
>>>> line 5: unnamed unused input active-high
>>>> line 6: unnamed unused input active-high
>>>> line 7: unnamed unused input active-high
>>>> line 8: unnamed unused input active-high
>>>> line 9: unnamed unused input active-high
>>>> line 10: unnamed unused input active-high
>>>> line 11: unnamed unused input active-high
>>>> line 12: unnamed unused input active-high
>>>> line 13: unnamed unused input active-high
>>>> line 14: unnamed unused input active-high
>>>> line 15: unnamed unused input active-high
>>>> line 16: unnamed unused input active-high
>>>> line 17: unnamed unused input active-high
>>>> line 18: unnamed unused input active-high
>>>> line 19: unnamed unused input active-high
>>>> line 20: unnamed unused input active-high
>>>> line 21: unnamed unused input active-high
>>>> line 22: unnamed unused input active-high
>>>> line 23: unnamed unused input active-high
>>>> line 24: unnamed unused input active-high
>>>> line 25: unnamed unused input active-high
>>>> line 26: unnamed unused input active-high
>>>> line 27: unnamed unused input active-high
>>>> line 28: unnamed unused input active-high
>>>> line 29: unnamed unused input active-high
>>>> line 30: unnamed unused input active-high
>>>> line 31: unnamed unused input active-high
>>>> gpiochip2 - 32 lines:
>>>> line 0: unnamed unused input active-high
>>>> line 1: unnamed unused input active-high
>>>> line 2: unnamed unused input active-high
>>>> line 3: unnamed unused input active-high
>>>> line 4: unnamed unused input active-high
>>>> line 5: unnamed unused input active-high
>>>> line 6: unnamed unused input active-high
>>>> line 7: unnamed unused input active-high
>>>> line 8: unnamed unused input active-high
>>>> line 9: unnamed unused input active-high
>>>> line 10: unnamed unused input active-high
>>>> line 11: unnamed unused input active-high
>>>> line 12: unnamed unused input active-high
>>>> line 13: unnamed unused input active-high
>>>> line 14: unnamed unused input active-high
>>>> line 15: unnamed unused input active-high
>>>> line 16: unnamed unused input active-high
>>>> line 17: unnamed unused input active-high
>>>> line 18: unnamed unused input active-high
>>>> line 19: unnamed unused input active-high
>>>> line 20: unnamed unused input active-high
>>>> line 21: unnamed unused input active-high
>>>> line 22: unnamed unused input active-high
>>>> line 23: unnamed unused input active-high
>>>> line 24: unnamed unused input active-high
>>>> line 25: unnamed unused input active-high
>>>> line 26: unnamed unused input active-high
>>>> line 27: unnamed unused input active-high
>>>> line 28: unnamed unused input active-high
>>>> line 29: unnamed unused input active-high
>>>> line 30: unnamed unused input active-high
>>>> line 31: unnamed unused input active-high
>>>> gpiochip3 - 32 lines:
>>>> line 0: unnamed unused input active-high
>>>> line 1: unnamed unused input active-high
>>>> line 2: unnamed unused input active-high
>>>> line 3: unnamed unused input active-high
>>>> line 4: unnamed unused input active-high
>>>> line 5: unnamed unused input active-high
>>>> line 6: unnamed "cd" input active-low [used]
>>>> line 7: unnamed unused input active-high
>>>> line 8: unnamed unused input active-high
>>>> line 9: unnamed unused input active-high
>>>> line 10: unnamed unused input active-high
>>>> line 11: unnamed unused input active-high
>>>> line 12: unnamed unused input active-high
>>>> line 13: unnamed unused input active-high
>>>> line 14: unnamed unused input active-high
>>>> line 15: unnamed unused input active-high
>>>> line 16: unnamed unused input active-high
>>>> line 17: unnamed unused input active-high
>>>> line 18: unnamed unused input active-high
>>>> line 19: unnamed unused input active-high
>>>> line 20: unnamed unused input active-high
>>>> line 21: unnamed unused input active-high
>>>> line 22: unnamed unused input active-high
>>>> line 23: unnamed unused input active-high
>>>> line 24: unnamed unused input active-high
>>>> line 25: unnamed unused input active-high
>>>> line 26: unnamed unused input active-high
>>>> line 27: unnamed unused input active-high
>>>> line 28: unnamed unused input active-high
>>>> line 29: unnamed unused input active-high
>>>> line 30: unnamed unused input active-high
>>>> line 31: unnamed unused input active-high
>>>> ```
>>>>
>>>> 1. What could be the cause for that (exact different between Dunfell and
>>>> Kirkstone in meta-ti)? Can it be that the relevant dts file(s) somehow changed?
>>>> The gpio names are defined in the device tree by defining "gpio-line-names
>>>> = ..."
>>>> Example for the am335x-boneblack.dts from TIs 6.1 kernel.
>>>> https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/arch/arm/boot/dts/am335x-boneblack.dts?h=ti-linux-6.1.y#n29
>>>> 2. Aside from labels missing, can there be any other consequences here? I
>>>> tested gpio outputs state changing and it works normally.
>>>> I'd guess no, other than it being harder to identify the correct gpio.
>>>>
>>>> I would appreciate all help and feedback!
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Jonathan Cormier
>>>> Software Engineer
>>>>
>>>> Voice: 315.425.4045 x222
>>>>
>>>>
>>>>
>>>>
>>>> http://www.CriticalLink.com
>>>> 6712 Brooklawn Parkway, Syracuse, NY 13211
>>>
>>>
>>>
>>> --
>>> Jonathan Cormier
>>> Software Engineer
>>>
>>> Voice: 315.425.4045 x222
>>>
>>>
>>>
>>>
>>> http://www.CriticalLink.com
>>> 6712 Brooklawn Parkway, Syracuse, NY 13211
>>
>>
>>
>> --
>> Jonathan Cormier
>> Software Engineer
>>
>> Voice: 315.425.4045 x222
>>
>>
>>
>>
>>
>>
>> http://www.CriticalLink.com
>> 6712 Brooklawn Parkway, Syracuse, NY 13211
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#17402):
> https://lists.yoctoproject.org/g/meta-ti/message/17402
> Mute This Topic: https://lists.yoctoproject.org/mt/103539668/8072670
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
> [bremenpl@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 33645 bytes --]
prev parent reply other threads:[~2024-01-13 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 8:49 [kirkstone] libgpiod-tools gpioinfo missing for beaglebone Lukasz Przenioslo
2024-01-10 21:52 ` [meta-ti] " Jon Cormier
2024-01-10 22:07 ` Bremenpl
2024-01-10 22:23 ` Jon Cormier
2024-01-11 5:28 ` Bremenpl
2024-01-11 18:25 ` Jon Cormier
2024-01-12 10:38 ` Re[2]: " Łukasz Przeniosło
[not found] ` <17A9934C6E495BDF.31870@lists.yoctoproject.org>
2024-01-13 9:23 ` Bremenpl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18d0221c8a8.284e.a291efdfec6f8802d64589cd992131fb@gmail.com \
--to=bremenpl@gmail.com \
--cc=jcormier@criticallink.com \
--cc=meta-ti@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).