[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53dkcpiewy64hv37kpqhrvpkprr7mgg7bl6f7ofpmpl5utqbe6@yldveipvbisb>
Date: Tue, 4 Mar 2025 19:46:09 +0800
From: Inochi Amaoto <inochiama@...il.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
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 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.
Regards,
Inochi.
Powered by blists - more mailing lists