linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Erik Schmauss <erik.schmauss@intel.com>,
	linux-acpi@vger.kernel.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	alsa-devel@alsa-project.org,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v3 0/3] ACPI, ASoC, gpio: Add and use acpi_dev_get_first_match_name()
Date: Fri, 12 Jan 2018 16:00:07 +0200	[thread overview]
Message-ID: <1515765607.7000.951.camel@linux.intel.com> (raw)
In-Reply-To: <21372380.qzqCkU0TZy@aspire.rjw.lan>

On Fri, 2018-01-12 at 14:24 +0100, Rafael J. Wysocki wrote:
> On Friday, January 5, 2018 5:09:32 PM CET Andy Shevchenko wrote:
> > It appears that at least one current user (patch 3) and upcoming one
> > (patch 2) need to get device name by ACPI HID.
> > 
> > Here we introduce acpi_dev_get_first_match_name() based on code
> > done for acpi_dev_present() and reuse it where appropriate.
> > 
> > The series has been tested on Intel Edison with non-ACPI and
> > ACPI enabled versions of U-Boot, while patches 1 and 3 were tested
> > by Pierre.
> > 
> > Since patch 1 and cross subsystem nature of the series I think
> > the best way is to push this (patches 1 and 2) via Rafael's linux-pm 
> > tree.
> > 
> > Taking into consideration that patch 3 requires not-yet-applied work
> > from Pierre, I left it for reference, in particular to show the LOC
> > statistics.
> > 
> > Changelog v3:
> > - add Pierre's tag (I dared to do this for both patches 1 and 3)
> > - address comment about function name (patch 1)
> > - add a reference to the first user (patch 1)
> > - consolidate pin control device possible names in one place (patch
> > 2)
> > - rebase ASoC patch on not-yet-applied series from Pierre (patch 3),
> > and
> > - thus reordered to make it last in the series (patch 3)
> > 
> > Andy Shevchenko (3):
> >   ACPI / utils: Introduce acpi_dev_get_first_match_name()
> >   gpio: merrifield: Add support of ACPI enabled platforms
> >   ASoC: Intel - Convert to use acpi_dev_get_first_match_name()
> > 
> >  drivers/acpi/utils.c                    | 41
> > +++++++++++++++++++++++++++------
> >  drivers/gpio/gpio-merrifield.c          | 11 ++++++++-
> >  include/acpi/acpi_bus.h                 |  3 +++
> >  include/linux/acpi.h                    |  6 +++++
> >  include/sound/soc-acpi.h                |  7 ------
> >  sound/soc/intel/boards/bytcht_da7213.c  |  2 +-
> >  sound/soc/intel/boards/bytcht_es8316.c  |  2 +-
> >  sound/soc/intel/boards/bytcr_rt5640.c   |  2 +-
> >  sound/soc/intel/boards/bytcr_rt5651.c   |  2 +-
> >  sound/soc/intel/boards/cht_bsw_rt5645.c |  2 +-
> >  sound/soc/intel/boards/cht_bsw_rt5672.c |  2 +-
> >  sound/soc/soc-acpi.c                    | 33 ----------------------
> > ----
> >  12 files changed, 59 insertions(+), 54 deletions(-)
> 
> [1-2/3] applied and I set up a git branch with them to pull from for
> Mark.

Thanks, Rafael!

So, the roadmap is as I see the following:
1) Mark applies (if no objection) latest version of the second patch
series from Pierre...
2) ...followed by PR from Rafael...
3) ...followed by the patch 3 from this series.

Mark, does it sound like a plan to you?

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      reply	other threads:[~2018-01-12 14:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 16:09 [PATCH v3 0/3] ACPI, ASoC, gpio: Add and use acpi_dev_get_first_match_name() Andy Shevchenko
2018-01-05 16:09 ` [PATCH v3 1/3] ACPI / utils: Introduce acpi_dev_get_first_match_name() Andy Shevchenko
2018-01-05 23:27   ` Rafael J. Wysocki
2018-01-08 13:09     ` Andy Shevchenko
2018-01-09  0:18       ` Rafael J. Wysocki
2018-01-09 13:34         ` Linus Walleij
2018-01-09 15:54       ` Mark Brown
2018-01-12 13:22         ` Rafael J. Wysocki
2018-01-12 20:01   ` Applied "ACPI: utils: Introduce acpi_dev_get_first_match_name()" to the asoc tree Mark Brown
2018-01-05 16:09 ` [PATCH v3 2/3] gpio: merrifield: Add support of ACPI enabled platforms Andy Shevchenko
2018-01-06  9:32   ` Mika Westerberg
2018-01-09 13:37   ` Linus Walleij
2018-01-12 20:01   ` Applied "gpio: merrifield: Add support of ACPI enabled platforms" to the asoc tree Mark Brown
2018-01-05 16:09 ` [PATCH v3 3/3] ASoC: Intel - Convert to use acpi_dev_get_first_match_name() Andy Shevchenko
2018-01-12 19:03   ` Mark Brown
2018-01-12 20:21     ` Andy Shevchenko
2018-01-12 21:01       ` Mark Brown
2018-01-12 21:03       ` Mark Brown
2018-01-05 16:13 ` [PATCH v3 0/3] ACPI, ASoC, gpio: Add and " Pierre-Louis Bossart
2018-01-05 17:08   ` Andy Shevchenko
2018-01-12 13:24 ` Rafael J. Wysocki
2018-01-12 14:00   ` Andy Shevchenko [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=1515765607.7000.951.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=erik.schmauss@intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=pierre-louis.bossart@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;
as well as URLs for NNTP newsgroup(s).