[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z8bp0qRvE0CzF6S_@smile.fi.intel.com>
Date: Tue, 4 Mar 2025 13:53:54 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Inochi Amaoto <inochiama@...il.com>
Cc: Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Jan Dabros <jsd@...ihalf.com>, Andi Shyti <andi.shyti@...nel.org>,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
Yixun Lan <dlan@...too.org>, Longbin Li <looong.bin@...il.com>
Subject: Re: [PATCH] i2c: designware: Add ACPI HID for DWAPB I2C controller
on Sophgo SG2044
On Tue, Mar 04, 2025 at 07:46:09PM +0800, Inochi Amaoto wrote:
> On Tue, Mar 04, 2025 at 01:43:27PM +0200, Andy Shevchenko wrote:
> > On Tue, Mar 04, 2025 at 03:02:11PM +0800, Inochi Amaoto wrote:
> > > Add ACPI ID for DWAPB I2C controller on Sophgo SG2044 so
> > > the SoC can enumerated the device via ACPI.
> >
> > Same as per UART:
> >
> > ---8<---
> >
> > This is fake ACPI ID. Please work with a vendor to issue the proper one.
> > Vendor ACPI ID registry has no records on Sophgo:
> > https://uefi.org/ACPI_ID_List?acpi_search=SophGo
> >
> > NAK.
> >
> > ---8<---
> >
> > But, it might be that is already in the process of getting proper ACPI vendor
> > ID, please provide an evidence in such a case.
> >
> > Otherwise drag the representative of the vendor to this email thread to answer
> > the question why the heck they abuse ACPI specification.
>
> OK, I will ask for the vendor and check whether there is some
> evidence for it. Now let's pause these patch.
>
> Thanks for your info.
You're welcome! As I already replied in another mail, feel free to contact me
or give my contacts to the vendor in order to help them to follow the process.
I will be glad to help.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists