From: Maciej Strozek <mstrozek@opensource.cirrus.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
acpica-devel@lists.linux.dev, patches@opensource.cirrus.com
Subject: Re: [PATCH v2] ACPICA: Add SoundWire File Table (SWFT) signature
Date: Wed, 16 Jul 2025 12:53:24 +0000 [thread overview]
Message-ID: <6339d75ec6e4211eb96f0d313c923656a2360097.camel@opensource.cirrus.com> (raw)
In-Reply-To: <CAJZ5v0i24A5N5bwJE-zqw_afcPk2a3OvnPNDCTCCd2tRTy7zBA@mail.gmail.com>
W dniu śro, 16.07.2025 o godzinie 14∶29 +0200, użytkownik Rafael J.
Wysocki napisał:
> On Wed, Jul 16, 2025 at 12:04 PM Maciej Strozek
> <mstrozek@opensource.cirrus.com> wrote:
> >
> > The File Download (FDL) process of SoundWire Class Audio (SDCA)
> > driver,
> > which provides code/data which may be required by an SDCA device,
> > utilizes SWFT to obtain that code/data. There is a single SWFT for
> > the
> > system, and SWFT can contain multiple files (information about the
> > file
> > as well as its binary contents). The SWFT has a standard ACPI
> > Descriptor
> > Table Header, followed by SoundWire File definitions as described
> > in
> > Discovery and Configuration (DisCo) Specification for SoundWire®
> >
> > Signed-off-by: Maciej Strozek <mstrozek@opensource.cirrus.com>
>
> The canonical way to change ACPICA is to submit a PR to the upstream
> ACPICA project on GitHub, wait until it is merged and then
> (optionally) submit a Linux kernel patch based on it and pointing
> back
> to the original upstream ACPICA commit.
>
> Thanks!
I was unaware of this, going to submit the PR then, sorry for the
noise!
--
Regards,
Maciej
prev parent reply other threads:[~2025-07-16 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 10:03 Maciej Strozek
2025-07-16 10:18 ` Charles Keepax
2025-07-16 12:29 ` Rafael J. Wysocki
2025-07-16 12:53 ` Maciej Strozek [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=6339d75ec6e4211eb96f0d313c923656a2360097.camel@opensource.cirrus.com \
--to=mstrozek@opensource.cirrus.com \
--cc=acpica-devel@lists.linux.dev \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.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
all inboxes | Powered by JetHome®