From: <tanureal@opensource.cirrus.com>
To: Takashi Iwai <tiwai@suse.de>, Hans de Goede <hdegoede@redhat.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Mark Gross <markgross@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
moderated list: "SOUND - SOC LAYER / DYNAMIC AUDIO POWER
MANAGEM..." <alsa-devel@alsa-project.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
<patches@opensource.cirrus.com>,
Platform Driver <platform-driver-x86@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>;
Subject: Re: [PATCH 5/5] ACPI / scan: Create platform device for CLSA0100
Date: Mon, 17 Jan 2022 10:47:32 +0000 [thread overview]
Message-ID: <605c6a69-0542-458c-2ea0-1ed26f6e28f5@opensource.cirrus.com> (raw)
In-Reply-To: <s5hy23h32mq.wl-tiwai@suse.de>
On 1/15/22 6:59 AM, Takashi Iwai <tiwai@suse.de> wrote:
> On Fri, 14 Jan 2022 19:56:04 +0100,
> Hans de Goede wrote:
> >
> > Hi,
> >
> > On 1/14/22 18:51, Rafael J. Wysocki wrote:
> >> On Fri, Jan 14, 2022 at 5:19 PM Takashi Iwai <tiwai@suse.de> wrote:
> >>>
> >>> On Thu, 13 Jan 2022 18:07:28 +0100,
> >>> Lucas Tanure wrote:
> >>>>
> >>>> The ACPI device with CLSA0100 is a sound card with
> >>>> multiple instances of CS35L41 connected by I2C to
> >>>> the main CPU.
> >>>>
> >>>> We add an ID to the i2c_multi_instantiate_idsi list
> >>>> to enumerate all I2C slaves correctly.
> >>>>
> >>>> Signed-off-by: Lucas Tanure <tanureal@opensource.cirrus.com>
> >>>
> >>> I think it's better to merge this from sound git tree together with
> >>> others in the patch set, presumably for rc1.
> >>>
> >>> It'd be great if ACPI people can take a review and give an ack/nack.
> >>
> >> Hans, what do you think?
> >
> > This patch (5/5) applies on top of:
> >
> > https://lore.kernel.org/linux-acpi/20211210154050.3713-1-sbinding@opensource.cirrus.com/
> >
> > Which still needs some work and which really should be merged
> > through the ACPI tree. IMHO it would be best to simply drop
> > this (5/5) from this series and move it to the v3 of the
> > series which I've linked to above.
> >
> > 1-4 can be merged through the alsa tree independently of 5/5 AFAIK.
>
> OK, that's fine.
>
> Lucas, could you submit v3 patches in the suggested way?
Yes, we will do that.
Thanks
>
>
> thanks,
>
> Takashi
>
next prev parent reply other threads:[~2022-01-17 10:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 17:07 [PATCH 1/5] ALSA: hda: cs35l41: Avoid overwriting register patch Lucas Tanure
2022-01-13 17:07 ` [PATCH 2/5] ALSA: hda: cs35l41: Add calls to newly added test key function Lucas Tanure
2022-01-14 16:14 ` Cezary Rojewski
2022-01-13 17:07 ` [PATCH 3/5] ALSA: hda: cs35l41: Move cs35l41* calls to its own symbol namespace Lucas Tanure
2022-01-13 17:07 ` [PATCH 4/5] ALSA: hda: cs35l41: Tidyup code and add default cases Lucas Tanure
2022-01-14 13:04 ` Lucas tanure
2022-01-14 16:15 ` Takashi Iwai
2022-01-13 17:07 ` [PATCH 5/5] ACPI / scan: Create platform device for CLSA0100 Lucas Tanure
2022-01-14 16:19 ` Takashi Iwai
2022-01-14 17:51 ` Rafael J. Wysocki
2022-01-14 18:56 ` Hans de Goede
2022-01-15 6:59 ` Takashi Iwai
2022-01-17 10:47 ` tanureal [this message]
2022-01-14 16:06 ` [PATCH 1/5] ALSA: hda: cs35l41: Avoid overwriting register patch Cezary Rojewski
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=605c6a69-0542-458c-2ea0-1ed26f6e28f5@opensource.cirrus.com \
--to=tanureal@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=hdegoede@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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).