From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Moritz Fischer <moritzf@google.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
mdf@kernel.org, ovt@google.com,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>
Subject: Re: [PATCH] i2c: designware: Add a new ACPI HID for GOOG5000 I2C controller
Date: Sat, 28 Feb 2026 12:47:47 +0200 [thread overview]
Message-ID: <aaLH0wYeUki0jqGc@ashevche-desk.local> (raw)
In-Reply-To: <ttbg5vcgzximy77bswykeprkl27hc2civnlpfwmgusm62wvzad@hvnapqphg6af>
On Fri, Feb 27, 2026 at 09:52:48PM +0000, Moritz Fischer wrote:
> On Fri, Feb 27, 2026 at 08:51:26PM +0200, Andy Shevchenko wrote:
> > On Fri, Feb 27, 2026 at 06:23:07PM +0000, Moritz Fischer wrote:
> > > Define a new ACPI HID for GOOG5000 as used on Google Axion.
> > >
> > > This has been validated on Silicon.
>
> > > Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> > > Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > Cc: Jan Dabros <jsd@semihalf.com>
>
> > Please, put Cc list...
>
> > > Signed-off-by: Moritz Fischer <moritzf@google.com>
> > > ---
>
> > ...somewhere here. It will have the same effect on the email. But the
> > positive
> > outcome is the noise reduction in the commit message.
>
> > See also this discussion (patch 18 subthread):
> > https://lore.kernel.org/lkml/20260123113708.416727-19-bigeasy@linutronix.de/
>
> Ok, fair. Do you want me to resend or do you want to patch it when
> applying?
I'm not a maintainer, so from my p.o.v. the safest option is to send a new
version with all data gathered and put properly (Cc list, ACPI excerpt, et
cetera) in one place.
...
> > > + { "GOOG5000", 0 },
>
> > The ID seems legit, but we need an ACPI excerpt from DSDT to show how it's
> > described (just important pieces of the respective Device() object) and
> > better
> > reference to the device / platform in question: Is it already on the
> > market?
>
> I pulled this out of the EDK2 code, I hope this satisfies your request.
>
> Device (I2C0)
> {
> Name (_HID, "GOOG5000")
> Name (_UID, 0x00)
> Method (_STA) {
> Return (0xf)
> }
> Name (_CRS, ResourceTemplate ()
> {
> QWordMemory (
> ResourceProducer,
> PosDecode,
> MinFixed,
> MaxFixed,
> NonCacheable,
> ReadWrite,
> 0x0,
> 0xA02048000,
> 0xA020480FF,
> 0x000000000,
> 0x000000100
> )
> Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive)
> {
> 109
> }
> })
> ...
> }
>
> This is being used by SoCs powering Google's Axion product line.
>
> I can't go into more details on timelines etc, but they *are* real
> products.
Good, just collect summary of this with the ACPI excerpt in the comment field
(after '---' line) in a new version, so we will have it for the record in the
ML archive in one place.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-28 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 18:23 Moritz Fischer
2026-02-27 18:51 ` Andy Shevchenko
2026-02-27 21:52 ` Moritz Fischer
2026-02-28 10:47 ` Andy Shevchenko [this message]
2026-03-02 5:37 ` Mika Westerberg
2026-03-02 7:51 ` Andy Shevchenko
2026-03-02 20:39 ` Moritz Fischer
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=aaLH0wYeUki0jqGc@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=moritzf@google.com \
--cc=ovt@google.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
all inboxes | Powered by JetHome®