linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Ye, Xiang" <xiang.ye@intel.com>, Lee Jones <lee@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Matthias Kaehlcke <mka@chromium.org>,
	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,
	sakari.ailus@linux.intel.com, zhifeng.wang@intel.com,
	wentong.wu@intel.com, lixu.zhang@intel.com
Subject: Re: [PATCH v5 1/5] usb: Add support for Intel LJCA device
Date: Wed, 15 Mar 2023 11:09:53 +0200	[thread overview]
Message-ID: <ZBGLYXxpkwokgV4R@kuha.fi.intel.com> (raw)
In-Reply-To: <ZBCYVNmoo2EdDY90@smile.fi.intel.com>

On Tue, Mar 14, 2023 at 05:52:52PM +0200, Andy Shevchenko wrote:
> On Tue, Mar 14, 2023 at 11:38:14PM +0800, Ye, Xiang wrote:
> > On Tue, Mar 14, 2023 at 10:36:57AM +0200, Heikki Krogerus wrote:
> > > On Tue, Mar 14, 2023 at 04:03:26PM +0800, Ye, Xiang wrote:
> 
> ...
> 
> > > You don't really seem to get any benefit from MFD. Perhaps it would be
> > > more appropriate and clear if you just registered auxiliary devices in
> > > this driver. Check drivers/base/auxiliary.c.
> > Yes, it should be a work. I have a question.
> > MFD provides the ACPI binding for sub-devices through
> > struct mfd_cell_acpi_match. But I didn't see this in drivers/base/auxiliary.c.
> > If using auxiliary bus to implement the LJCA sub-devices, we need to do
> > the sub-devices acpi binding manually in ljca.c.
> > 
> > Something Like:
> > adr = LJCA_ACPI_MATCH_GPIO
> > adev = acpi_find_child_device(parent, adr, false);
> > ACPI_COMPANION_SET(&pdev->dev, adev ?: parent);
> > 
> > Is that acceptable?

Looks ok to me.

> Maybe you can implement this on the level of auxiliary bus.

I would actually prefer that the auxiliary bus itself does not make
any assumptions regarding the whereabouts of the fwnodes at this
stage. Maybe later, when(if) there are more users.

thanks,

-- 
heikki

  reply	other threads:[~2023-03-15  9:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 19:04 [PATCH v5 0/5] Add Intel LJCA device driver Ye Xiang
2023-03-12 19:04 ` [PATCH v5 1/5] usb: Add support for Intel LJCA device Ye Xiang
2023-03-13  6:56   ` Greg Kroah-Hartman
2023-03-14  6:54     ` Ye, Xiang
2023-03-13 16:21   ` Andi Shyti
2023-03-14  7:33     ` Ye, Xiang
2023-03-13 17:03   ` Lee Jones
2023-03-14  8:03     ` Ye, Xiang
2023-03-14  8:36       ` Heikki Krogerus
2023-03-14 15:38         ` Ye, Xiang
2023-03-14 15:52           ` Andy Shevchenko
2023-03-15  9:09             ` Heikki Krogerus [this message]
2023-06-30  7:40               ` Wu, Wentong
2023-06-30 17:37                 ` Andy Shevchenko
2023-03-12 19:04 ` [PATCH v5 2/5] gpio: Add support for Intel LJCA USB GPIO driver Ye Xiang
2023-03-15 12:20   ` Bartosz Golaszewski
2023-03-12 19:04 ` [PATCH v5 3/5] i2c: Add support for Intel LJCA USB I2C driver Ye Xiang
2023-03-12 19:04 ` [PATCH v5 4/5] spi: Add support for Intel LJCA USB SPI driver Ye Xiang
2023-03-12 19:04 ` [PATCH v5 5/5] Documentation: Add ABI doc for attributes of LJCA device Ye Xiang

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=ZBGLYXxpkwokgV4R@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=brgl@bgdev.pl \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --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=mka@chromium.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=srinivas.pandruvada@intel.com \
    --cc=wentong.wu@intel.com \
    --cc=wsa@kernel.org \
    --cc=xiang.ye@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).