public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andrey Zhizhikin <andrey.z@gmail.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, lee.jones@linaro.org,
	linux-kernel@vger.kernel.org,
	Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>
Subject: Re: [PATCH 2/2] mfd: add regulator cell to Cherry Trail Whiskey Cove PMIC
Date: Fri, 25 Oct 2019 13:49:25 +0300	[thread overview]
Message-ID: <20191025104925.GR32742@smile.fi.intel.com> (raw)
In-Reply-To: <CAHtQpK7P2X42WxZzok+XVZESV7O_JWK3Th7JMnMQsaq6f0gELw@mail.gmail.com>

On Fri, Oct 25, 2019 at 11:16:22AM +0200, Andrey Zhizhikin wrote:
> On Fri, Oct 25, 2019 at 10:07 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Thu, Oct 24, 2019 at 02:29:39PM +0000, Andrey Zhizhikin wrote:
> > > Add a regulator mfd cell to Whiskey Cove PMIC driver, which is used to
> > > supply various voltage rails.
> > >
> > > In addition, make the initialization of this mfd driver early enough in
> > > order to provide regulator cell to mmc sub-system when it is initialized.
> >
> > Doesn't deferred probe mechanism work for you?
> > MMC core returns that error till we have the driver initialized.
> 
> This would work for mmc sub-system, but my idea was that later when
> more cells are added to this mfd - it might turn out that we would
> require an early initialization anyway. So I decided to take an
> opportunity to adjust it with this patch as well, and this is what I
> roughly explained in the commit message. When I'm reading it now,
> exactly this point was not mentioned in commit message at all, and I
> rather coupled the early init with mmc sub-system, which creates a
> source of confusion here. I guess if there would be no other
> objections about early init - I'd go with v2 of this patch, where I
> would clean-up the point below and adjust the commit description.
> 
> Thanks a lot for pointing this out!

> > > -static struct i2c_driver cht_wc_driver = {
> > > +static struct i2c_driver cht_wc_i2c_driver = {
> >
> > Renaming is not explained in the commit message.
> 
> True, this point I forgot to mention. Actually, this is tightly
> coupled with the fact that mfd driver has been moved to an earlier
> init stage and since it does belong to I2C sub-system (and represented
> by i2c_device structure) - I decided to make a name sound more
> logical.

So, seems you have three changes in one patch. Please, split accordingly.

In v2 also Cc all stakeholders I mentioned.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2019-10-25 10:49 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 14:29 [PATCH 0/2] add regulator driver and mfd cell for Intel Cherry Trail Whiskey Cove PMIC Andrey Zhizhikin
2019-10-24 14:29 ` [PATCH 1/2] regulator: add support for Intel Cherry Whiskey Cove regulator Andrey Zhizhikin
2019-10-25  8:01   ` Andy Shevchenko
2019-10-25  8:58     ` Andrey Zhizhikin
2019-10-25  9:14       ` Andy Shevchenko
2019-10-25  9:31         ` Andrey Zhizhikin
2019-10-25 10:47           ` Andy Shevchenko
2019-10-25 12:17   ` Mark Brown
2019-10-25 15:26     ` Andrey Zhizhikin
2019-10-25 16:02       ` Andy Shevchenko
2019-10-25 16:21         ` Andrey Zhizhikin
2019-10-24 14:29 ` [PATCH 2/2] mfd: add regulator cell to Cherry Trail Whiskey Cove PMIC Andrey Zhizhikin
2019-10-25  8:06   ` Andy Shevchenko
2019-10-25  9:16     ` Andrey Zhizhikin
2019-10-25 10:49       ` Andy Shevchenko [this message]
2019-10-25 12:00         ` Andrey Zhizhikin
2019-10-25  7:53 ` [PATCH 0/2] add regulator driver and mfd cell for Intel " Andy Shevchenko
2019-10-25  7:55   ` Andy Shevchenko
2019-10-25  8:51     ` Andrey Zhizhikin
2019-10-28 12:41     ` Adrian Hunter
2019-10-28 12:45       ` Mark Brown
2019-10-28 13:26         ` Hans de Goede
2019-10-28 15:01           ` Andrey Zhizhikin
2019-10-29 12:03             ` Hans de Goede
2019-10-29 16:57               ` Andrey Zhizhikin
2019-10-29 17:14                 ` Hans de Goede
2019-10-28 16:28           ` Andy Shevchenko
2019-10-28 14:40       ` Andrey Zhizhikin
2019-10-25  9:38   ` Hans de Goede
2019-10-25 10:11     ` Andrey Zhizhikin
2019-10-25 10:45       ` Hans de Goede
2019-10-25 11:54         ` Andrey Zhizhikin
2019-10-25 12:05         ` Mark Brown
2019-10-25 12:18           ` Hans de Goede
2019-10-25 10:44     ` 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=20191025104925.GR32742@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=andrey.z@gmail.com \
    --cc=andrey.zhizhikin@leica-geosystems.com \
    --cc=broonie@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.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