public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>, Lee Jones <lee.jones@linaro.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] ACPI / PMIC: Add byt prefix to Crystal Cove PMIC OpRegion driver
Date: Fri, 25 Oct 2019 10:48:09 +0300	[thread overview]
Message-ID: <20191025074809.GB32742@smile.fi.intel.com> (raw)
In-Reply-To: <20191025074154.GX32742@smile.fi.intel.com>

On Fri, Oct 25, 2019 at 10:41:54AM +0300, Andy Shevchenko wrote:
> On Thu, Oct 24, 2019 at 11:38:25PM +0200, Hans de Goede wrote:
> > Our current Crystal Cove OpRegion driver is only valid for the
> > Crystal Cove PMIC variant found on Bay Trail (BYT) boards,
> > Cherry Trail (CHT) based boards use another variant.
> > 
> > At least the regulator registers are different on CHT and these registers
> > are one of the things controlled by the custom PMIC OpRegion.
> > 
> > Commit 4d9ed62ab142 ("mfd: intel_soc_pmic: Export separate mfd-cell
> > configs for BYT and CHT") has disabled the intel_pmic_crc.c code for CHT
> > devices by removing the "crystal_cove_pmic" MFD cell on CHT devices.
> > 
> > This commit renames the intel_pmic_crc.c driver and the cell to be
> > prefixed with "byt" to indicate that this code is for BYT devices only.
> > 
> > This is a preparation patch for adding a separate PMIC OpRegion
> > driver for the CHT variant of the Crystal Cove PMIC (sometimes called
> > Crystal Cove Plus in Android kernel sources).
> 
> >  .../acpi/pmic/{intel_pmic_crc.c => intel_pmic_bytcrc.c}    | 4 ++--
> >  drivers/mfd/intel_soc_pmic_crc.c                           | 2 +-
> 
> I would go with previously established pattern, i.e. intel_pmic_bytcc.c.

That said you may use mine
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

> 
> > +++ b/drivers/mfd/intel_soc_pmic_crc.c
> > @@ -75,7 +75,7 @@ static struct mfd_cell crystal_cove_byt_dev[] = {
> >  		.resources = gpio_resources,
> >  	},
> >  	{
> > -		.name = "crystal_cove_pmic",
> > +		.name = "byt_crystal_cove_pmic",
> >  	},
> >  	{
> >  		.name = "crystal_cove_pwm",
> 
> I'm wondering shouldn't we rename the PWM and GPIO for the sake of consistency?
> Yes, if a driver is used on both CHT and BYT, let it provide two names.
> 
> -- 
> With Best Regards,
> Andy Shevchenko
> 
> 

-- 
With Best Regards,
Andy Shevchenko



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

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 21:38 [PATCH 1/4] ACPI / PMIC: Add partial support for Cherry Trail Crystal Cove PMIC Hans de Goede
2019-10-24 21:38 ` [PATCH 1/4] ACPI / PMIC: Do not register handlers for unhandled OpRegions Hans de Goede
2019-10-25  7:42   ` Andy Shevchenko
2019-10-24 21:38 ` [PATCH 2/4] ACPI / PMIC: Add byt prefix to Crystal Cove PMIC OpRegion driver Hans de Goede
2019-10-25  7:41   ` Andy Shevchenko
2019-10-25  7:48     ` Andy Shevchenko [this message]
2019-10-25  8:59     ` Hans de Goede
2019-10-25  9:33       ` Andy Shevchenko
2019-10-25  9:49         ` Rafael J. Wysocki
2019-10-24 21:38 ` [PATCH 3/4] ACPI / PMIC: Add Cherry Trail " Hans de Goede
2019-10-25  7:45   ` Andy Shevchenko
2019-10-25  9:06     ` Hans de Goede
2019-10-25  9:34       ` Andy Shevchenko
2019-10-24 21:38 ` [PATCH 4/4] mfd: intel_soc_pmic_crc: Add "cht_crystal_cove_pmic" cell to CHT cells Hans de Goede
2019-10-25  7:47   ` Andy Shevchenko
2019-11-01  9:01   ` Lee Jones
2019-11-05 23:11     ` Rafael J. Wysocki

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=20191025074809.GB32742@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=lee.jones@linaro.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    /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