From: Alexander Dahl <ada@thorsis.com>
To: Hans Kurscheidt <lve0200@gmail.com>
Cc: linux-gpio@vger.kernel.org
Subject: Re: gpiod: Set pullup for Input Line
Date: Mon, 21 Mar 2022 15:42:56 +0100 [thread overview]
Message-ID: <YjiO8CScFFVjiy1/@ada.ifak-system.com> (raw)
In-Reply-To: <33b30df9-3763-7ced-88f9-3b6e32ae236b@gmail.com>
Hei hei,
Am Mon, Mar 21, 2022 at 02:48:02PM +0100 schrieb Hans Kurscheidt:
> sure, device trees are eventually overwritten w/ new kernels or "as is" on a
> new device.
You would need a board specific dts or dt overlay anyways. Just compile
that again with you new kernel. For a new board, you need to make a
new dts anyways, I don't see the problem here.
> Hence my application won't work on a new installation/board,
> because it needs certain GPIO input pins w/pull ups.
Well, and those pullups need to be in SoC, and can not be external?
> DTBs need to be
> disassembled and re-compiled, which is not for the average user to install &
> run an application!
Why disassemble dtb, just go with the dts and compile that.
For easier handling in your application and across different boards,
you might want to checkout gpio line names. We successfully used that
to let the same application work with different boards (even with
SoCs of different vendors), without the need to modify the app at all
if the hardware changes. That is much more convenient than putting
pin numbers and knowledge about each and every possible board into the
application.
HTH & Greets
Alex
next prev parent reply other threads:[~2022-03-21 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ab3240e5-df61-cff4-ebba-f6a7e5d99f52@gmail.com>
2022-03-21 13:48 ` gpiod: Set pullup for Input Line Hans Kurscheidt
2022-03-21 14:42 ` Alexander Dahl [this message]
2022-03-21 10:43 Hans Kurscheidt
2022-03-21 13:34 ` Alexander Dahl
2022-03-21 16:26 ` Andy Shevchenko
2022-03-21 17:27 ` Hans Kurscheidt
2022-03-21 17:33 ` Andy Shevchenko
2022-03-21 18:17 ` Hans Kurscheidt
2022-03-21 20:25 ` Fwd: " Hans Kurscheidt
2022-03-22 0:59 ` Kent Gibson
[not found] ` <1a7fd31a-221e-7b23-b95f-d71e440b3ff0@gmail.com>
2022-03-22 8:39 ` Hans Kurscheidt
2022-03-22 8:50 ` Andy Shevchenko
2022-03-22 9:39 ` Hans Kurscheidt
2022-03-22 16:12 ` Kent Gibson
2022-03-22 16:11 ` Kent Gibson
2022-03-22 16:11 ` Kent Gibson
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=YjiO8CScFFVjiy1/@ada.ifak-system.com \
--to=ada@thorsis.com \
--cc=linux-gpio@vger.kernel.org \
--cc=lve0200@gmail.com \
/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 NNTP newsgroup(s).