From: 'Andy Shevchenko' <andriy.shevchenko@linux.intel.com>
To: "Yoshihiro Furudera (Fujitsu)" <fj5100bi@fujitsu.com>
Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>, Andi Shyti <andi.shyti@kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2c: designware: Add ACPI HID for DWAPB I2C controller on Fujitsu MONAKA
Date: Tue, 22 Oct 2024 16:12:57 +0300 [thread overview]
Message-ID: <Zxek2SsrFg-XnHWP@smile.fi.intel.com> (raw)
In-Reply-To: <OS3PR01MB6903405361060650429FAC2AD44C2@OS3PR01MB6903.jpnprd01.prod.outlook.com>
On Tue, Oct 22, 2024 at 01:14:18AM +0000, Yoshihiro Furudera (Fujitsu) wrote:
> > On Mon, Oct 21, 2024 at 07:22:55AM +0000, Yoshihiro Furudera (Fujitsu) wrote:
> > > > On Fri, Oct 18, 2024 at 01:58:26AM +0000, Yoshihiro Furudera wrote:
...
> > Device (SMB0)
> > {
> > ...
> > }
> > Hmm... Why Device object is called SMB0, are you sure it's the correct one?
>
> We considered the string to be the most concise
> representation of SMBus HC#0, given the general
> constraint that object names should ideally be
> four characters or less. We understood that,
> unlike HID, SMBus object names are vendor-specific.
But this all about UART! How is it related to SMBus?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-10-22 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 1:58 [PATCH] i2c: designware: Add ACPI HID for DWAPB I2C controller on Fujitsu MONAKA Yoshihiro Furudera
2024-10-18 12:41 ` Andy Shevchenko
2024-10-21 7:22 ` Yoshihiro Furudera (Fujitsu)
2024-10-21 8:25 ` 'Andy Shevchenko'
2024-10-22 1:14 ` Yoshihiro Furudera (Fujitsu)
2024-10-22 13:12 ` 'Andy Shevchenko' [this message]
2024-10-23 4:40 ` Yoshihiro Furudera (Fujitsu)
2024-10-23 14:31 ` 'Andy Shevchenko'
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=Zxek2SsrFg-XnHWP@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=fj5100bi@fujitsu.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.