public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Wentong Wu <wentong.wu@intel.com>
Cc: gregkh@linuxfoundation.org, oneukum@suse.com, wsa@kernel.org,
	andi.shyti@linux.intel.com, broonie@kernel.org,
	bartosz.golaszewski@linaro.org, linus.walleij@linaro.org,
	hdegoede@redhat.com, linux-usb@vger.kernel.org,
	linux-i2c@vger.kernel.org, linux-spi@vger.kernel.org,
	sakari.ailus@linux.intel.com, zhifeng.wang@intel.com,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v20 1/4] usb: Add support for Intel LJCA device
Date: Wed, 11 Oct 2023 13:21:20 +0300	[thread overview]
Message-ID: <ZSZ3IPgLk7uC5UGI@smile.fi.intel.com> (raw)
In-Reply-To: <1696833205-16716-2-git-send-email-wentong.wu@intel.com>

On Mon, Oct 09, 2023 at 02:33:22PM +0800, Wentong Wu wrote:
> Implements the USB part of Intel USB-I2C/GPIO/SPI adapter device
> named "La Jolla Cove Adapter" (LJCA).
> 
> The communication between the various LJCA module drivers and the
> hardware will be muxed/demuxed by this driver. Three modules (
> I2C, GPIO, and SPI) are supported currently.
> 
> Each sub-module of LJCA device is identified by type field within
> the LJCA message header.
> 
> The sub-modules of LJCA can use ljca_transfer() to issue a transfer
> between host and hardware. And ljca_register_event_cb is exported
> to LJCA sub-module drivers for hardware event subscription.
> 
> The minimum code in ASL that covers this board is
> Scope (\_SB.PCI0.DWC3.RHUB.HS01)
>     {
>         Device (GPIO)
>         {
>             Name (_ADR, Zero)
>             Name (_STA, 0x0F)
>         }
> 
>         Device (I2C)
>         {
>             Name (_ADR, One)
>             Name (_STA, 0x0F)
>         }
> 
>         Device (SPI)
>         {
>             Name (_ADR, 0x02)
>             Name (_STA, 0x0F)
>         }
>     }

This commit message is not true anymore, or misleading at bare minimum.
The ACPI specification is crystal clear about usage _ADR and _HID, i.e.
they must NOT be used together for the same device node. So, can you
clarify how the DSDT is organized and update the commit message and
it may require (quite likely) to redesign the architecture of this
driver. Sorry I missed this from previous rounds as I was busy by
something else.

Greg, please do not promote this to the next before above will be clarified.

P.S> Using _ADR and _HID together is an immediate NAK from me.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2023-10-11 10:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09  6:33 [PATCH v20 0/4] Add Intel LJCA device driver Wentong Wu
2023-10-09  6:33 ` [PATCH v20 1/4] usb: Add support for Intel LJCA device Wentong Wu
2023-10-09 10:22   ` Oliver Neukum
2023-10-11 10:21   ` Andy Shevchenko [this message]
2023-10-11 10:37     ` Hans de Goede
2023-10-11 10:43       ` Andy Shevchenko
2023-10-11 12:50       ` Wu, Wentong
2023-10-12 11:14         ` Hans de Goede
2023-10-13 20:05           ` Shevchenko, Andriy
2023-10-14 10:58             ` Hans de Goede
2023-10-16  5:52               ` Wu, Wentong
2023-10-16  7:35                 ` Hans de Goede
2023-10-16  7:38                 ` Shevchenko, Andriy
2023-10-16 15:05                   ` Wu, Wentong
2023-10-16 15:19                     ` gregkh
2023-10-16 15:44                       ` Wu, Wentong
2023-10-16 16:05                         ` Shevchenko, Andriy
2023-10-16 17:20                           ` Hans de Goede
2023-10-17  0:46                             ` Wu, Wentong
2023-10-09  6:33 ` [PATCH v20 2/4] i2c: Add support for Intel LJCA USB I2C driver Wentong Wu
2023-10-10 19:25   ` Wolfram Sang
2023-10-09  6:33 ` [PATCH v20 3/4] spi: Add support for Intel LJCA USB SPI driver Wentong Wu
2023-10-09 12:50   ` Mark Brown
2023-10-09  6:33 ` [PATCH v20 4/4] gpio: update Intel LJCA USB GPIO driver Wentong Wu

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=ZSZ3IPgLk7uC5UGI@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=wentong.wu@intel.com \
    --cc=wsa@kernel.org \
    --cc=zhifeng.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox