Linux I2C development
 help / color / mirror / Atom feed
From: "Ye, Xiang" <xiang.ye@intel.com>
To: Lee Jones <lee@kernel.org>
Cc: Wolfram Sang <wsa@kernel.org>, Tyrone Ting <kfting@nuvoton.com>,
	"Mark Brown" <broonie@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	"Bartosz Golaszewski" <brgl@bgdev.pl>,
	<linux-usb@vger.kernel.org>, <linux-i2c@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-spi@vger.kernel.org>,
	<linux-gpio@vger.kernel.org>, <srinivas.pandruvada@intel.com>,
	<heikki.krogerus@linux.intel.com>,
	<andriy.shevchenko@linux.intel.com>,
	<sakari.ailus@linux.intel.com>, <zhifeng.wang@intel.com>,
	<wentong.wu@intel.com>, <lixu.zhang@intel.com>
Subject: Re: [PATCH 1/5] mfd: Add support for Intel LJCA device
Date: Mon, 6 Mar 2023 10:55:46 +0800	[thread overview]
Message-ID: <ZAVWMp2LyxY7w6N0@ye-NUC7i7DNHE> (raw)
In-Reply-To: <20230305103456.GF2574592@google.com>

Hi Lee,

Thanks for the review.
On Sun, Mar 05, 2023 at 10:34:56AM +0000, Lee Jones wrote:
> On Mon, 20 Feb 2023, Ye Xiang wrote:
> 
> > This patch implements the USB part of Intel USB-I2C/GPIO/SPI adapter
> > device named "La Jolla Cove Adapter" (LJCA).
> 
> The "USB part" should live in drivers/usb.
What about putting ljca.c to drivers/usb/misc?
> 
> You can use MFD to register each of the components, but all of the USB
> functionality needs moving somewhere else.
Ok, Now the USB functionality drivers have already been put to related driver
folders: spi-ljca in drivers/spi, i2c-ljca in drivers/i2c, and gpio-ljca
in drivers/gpio.
>  
> > The communication between the various LJCA module drivers and the
> > hardware will be muxed/demuxed by this driver. The sub-module of
> > LJCA can use ljca_transfer() to issue a transfer between host
> > and hardware.
> > 
> > Each sub-module of LJCA device is identified by type field within
> > the LJCA message header.
> > 
> > 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)
> >         }
> >     }
> > 
> > Signed-off-by: Ye Xiang <xiang.ye@intel.com>
> > ---
> >  drivers/mfd/Kconfig      |  13 +
> >  drivers/mfd/Makefile     |   1 +
> >  drivers/mfd/ljca.c       | 977 +++++++++++++++++++++++++++++++++++++++
> >  include/linux/mfd/ljca.h |  95 ++++
> >  4 files changed, 1086 insertions(+)
> >  create mode 100644 drivers/mfd/ljca.c
> >  create mode 100644 include/linux/mfd/ljca.h
> 
> -- 
> Lee Jones [李琼斯]

  reply	other threads:[~2023-03-06  2:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-19 18:30 [PATCH 0/5] Add Intel LJCA device driver Ye Xiang
2023-02-19 18:30 ` [PATCH 1/5] mfd: Add support for Intel LJCA device Ye Xiang
2023-03-05 10:34   ` Lee Jones
2023-03-06  2:55     ` Ye, Xiang [this message]
2023-03-06  9:09       ` Lee Jones
2023-02-19 18:30 ` [PATCH 2/5] gpio: Add support for Intel LJCA USB GPIO driver Ye Xiang
2023-02-19 21:02   ` kernel test robot
2023-02-20  1:00   ` kernel test robot
2023-02-24 10:48   ` Linus Walleij
2023-02-24 17:25     ` Ye, Xiang
2023-02-19 18:30 ` [PATCH 3/5] i2c: Add support for Intel LJCA USB I2C driver Ye Xiang
2023-02-19 20:31   ` kernel test robot
2023-02-19 23:56   ` kernel test robot
2023-02-19 18:30 ` [PATCH 4/5] spi: Add support for Intel LJCA USB SPI driver Ye Xiang
2023-02-20  3:25   ` kernel test robot
2023-02-19 18:30 ` [PATCH 5/5] Documentation: Add ABI doc for attributes of LJCA device Ye Xiang
2023-02-24 10:53   ` Linus Walleij
2023-02-24 18:01     ` Ye, Xiang
2023-03-06 14:00       ` Linus Walleij

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=ZAVWMp2LyxY7w6N0@ye-NUC7i7DNHE \
    --to=xiang.ye@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=brgl@bgdev.pl \
    --cc=broonie@kernel.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=kfting@nuvoton.com \
    --cc=lee@kernel.org \
    --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=lixu.zhang@intel.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=srinivas.pandruvada@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