public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: mazziesaccount@gmail.com,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Alessandro Zummo <a.zummo@towertech.it>
Subject: Re: [PATCH] mfd: rohm PMICs - use platform_device_id to match MFD sub-devices
Date: Fri, 15 Nov 2019 17:06:15 +0000	[thread overview]
Message-ID: <20191115170615.GB24158@dell> (raw)
In-Reply-To: <20191115145351.GA13474@localhost.localdomain>

On Fri, 15 Nov 2019, Matti Vaittinen wrote:

> Hello Lee, Stephen, Mark & All,
> 
> On Thu, Nov 07, 2019 at 03:30:12PM +0200, Matti Vaittinen wrote:
> > Do device matching using the platform_device_id instead of using
> > explicit module_aliases to load modules and custom parent-data field
> > to do module loading and sub-device matching.
> > 
> > Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> > ---
> > 
> > Thanks to Stephen Boyd I just learned we can use platform_device_id
> > to do device and module matching for MFD sub-devices. This is handy
> > in cases where more than one chips are supported by same sub-device
> > drivers. For ROHM it currently is clk and regulator - but also the
> > RTC when BD71828 is in-tree.
> 
> I have been preparing driver for yet another ROHM PMIC (bd71828) - and
> the patch has been taking a few spins as RFC now. I would like to send
> first non RFC version of it - and I would like to write it on top of
> this patch. Is it Ok if I include this patch in the series - or should
> this stay as independent change? I would like to try avoid conflicting
> patches.

You can draft this patch in.

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2019-11-15 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 13:30 [PATCH] mfd: rohm PMICs - use platform_device_id to match MFD sub-devices Matti Vaittinen
2019-11-15 14:53 ` Matti Vaittinen
2019-11-15 17:06   ` Lee Jones [this message]

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=20191115170615.GB24158@dell \
    --to=lee.jones@linaro.org \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=mazziesaccount@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    /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