From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Lee Jones <lee.jones@linaro.org>, <patches@opensource.cirrus.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] mfd: arizona-spi: Split Windows ACPI init code into its own function
Date: Mon, 28 Feb 2022 11:34:13 +0000 [thread overview]
Message-ID: <20220228113413.GI38351@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <20220223134222.730886-1-hdegoede@redhat.com>
On Wed, Feb 23, 2022 at 02:42:21PM +0100, Hans de Goede wrote:
> x86/ACPI boards with an arizona WM5102 codec ship with either Windows or
> Android as factory installed OS.
>
> The ACPI fwnode describing the codec differs depending on the factory OS,
> and the current arizona_spi_acpi_probe() function is tailored for use
> with the Windows board ACPI tables.
>
> Split out the Windows board ACPI tables specific bits into a new
> arizona_spi_acpi_windows_probe() function in preparation for also
> adding support for the Android board ACPI tables.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
prev parent reply other threads:[~2022-02-28 11:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 13:42 [PATCH 1/2] mfd: arizona-spi: Split Windows ACPI init code into its own function Hans de Goede
2022-02-23 13:42 ` [PATCH 2/2] mfd: arizona-spi: Add Android board ACPI table handling Hans de Goede
2022-02-28 11:35 ` Charles Keepax
2022-03-07 14:51 ` Lee Jones
2022-03-07 14:55 ` Hans de Goede
2022-03-07 15:19 ` Lee Jones
2022-03-07 17:34 ` Hans de Goede
2022-03-08 8:15 ` Lee Jones
2022-02-28 11:34 ` Charles Keepax [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=20220228113413.GI38351@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=hdegoede@redhat.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.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).