From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Ferry Toth <ftoth@exalondelft.nl>
Subject: Re: [PATCH v1 1/1] Revert "pinctrl: avoid unsafe code pattern in find_pinctrl()"
Date: Wed, 18 Oct 2023 08:01:23 +0300 [thread overview]
Message-ID: <ZS9mo4/jnRNoTE+v@smile.fi.intel.com> (raw)
In-Reply-To: <ZS7_5VGvRnw99gzd@google.com>
On Tue, Oct 17, 2023 at 02:43:01PM -0700, Dmitry Torokhov wrote:
> On Tue, Oct 17, 2023 at 10:45:39PM +0300, Andy Shevchenko wrote:
Thanks for your response.
...
> I wonder, could you please post entire dmesg for your system?
Working, non-working or both?
...
> I think the right answer is "fix the userspace" really in this case. We
> could also try extend of_alias_get_id() to see if we could pass some
> preferred numbering on x86. But this will again be fragile if the
> knowledge resides in the driver and is not tied to a particular board
> (as it is in DT case): there could be multiple controllers, things will
> be shifting board to board...
Any suggestion how should it be properly done in the minimum shell environment?
(Busybox uses mdev with static tables IIRC and there is no fancy udev or so)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-10-18 5:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 14:18 [PATCH v1 1/1] Revert "pinctrl: avoid unsafe code pattern in find_pinctrl()" Andy Shevchenko
2023-10-17 18:18 ` Linus Walleij
2023-10-17 18:34 ` Andy Shevchenko
2023-10-17 18:39 ` Andy Shevchenko
2023-10-17 18:59 ` Linus Walleij
2023-10-17 19:45 ` Andy Shevchenko
2023-10-17 21:43 ` Dmitry Torokhov
2023-10-18 5:01 ` Andy Shevchenko [this message]
2023-10-18 22:41 ` Dmitry Torokhov
2023-10-19 8:12 ` Linus Walleij
2023-10-19 12:15 ` Andy Shevchenko
2023-10-19 12:13 ` Andy Shevchenko
2023-10-19 16:52 ` Andy Shevchenko
2023-10-19 17:19 ` Andy Shevchenko
2023-10-18 7:56 ` Ferry Toth
2023-10-19 8:13 ` Linus Walleij
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=ZS9mo4/jnRNoTE+v@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ftoth@exalondelft.nl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ulf.hansson@linaro.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 NNTP newsgroup(s).