From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Konstantin Aladyshev <aladyshev22@gmail.com>
Cc: linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: Assigning fixed numbers to i2c buses via ACPI code
Date: Wed, 12 Feb 2025 15:31:17 +0200 [thread overview]
Message-ID: <Z6yipb0ACrqVaECP@smile.fi.intel.com> (raw)
In-Reply-To: <CACSj6VUV7XjYMnu482tVsS2Sb1XrxzBA5h+AAkt1K-FU3Dy=Hw@mail.gmail.com>
On Wed, Feb 12, 2025 at 03:37:22PM +0300, Konstantin Aladyshev wrote:
> Don't get me wrong, I'm not trying to defend a solution with aliases.
I'm not assuming you defend it, just telling you that, yeah, design of
some solutions in the user space WRT HW finding and identification is
broken. And OF alias approach was maybe a mistake to work around that.
> It is just there is existing code that relies on fixed i2c bus
> numbers, and I was just trying to understand if it can be ported to
> x86 easily.
If you do it correctly from day 1, there porting will not be needed *at all*
independently on the architecture (it will work even on legacy non-OF/non-ACPI
platforms as good as on newest ones). That's my point.
> Apparently it can't.
It can't be done in current code base, but one may patch the kernel and
the ACPI tables to achieve that. I do not think it's a practical solution,
though.
> Thanks for the answer!
You're welcome!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-02-12 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 8:18 Assigning fixed numbers to i2c buses via ACPI code Konstantin Aladyshev
2025-02-12 11:08 ` Andy Shevchenko
2025-02-12 12:06 ` Konstantin Aladyshev
2025-02-12 12:06 ` Andy Shevchenko
2025-02-12 12:37 ` Konstantin Aladyshev
2025-02-12 13:31 ` Andy Shevchenko [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=Z6yipb0ACrqVaECP@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=aladyshev22@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.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