From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: Hoan Tran <hoan@os.amperecomputing.com>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Mark Brown <broonie@kernel.org>,
Thomas Lin <thomas_lin@lecomputing.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-spi@vger.kernel.org,
braden_zhang@lecomputing.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: (subset) [PATCH 0/2] Subject: [PATCH v5 0/2] arm64: Add LECARC ACPI IDs for DesignWare GPIO, SPI
Date: Thu, 21 May 2026 10:49:55 +0200 [thread overview]
Message-ID: <177935339258.17744.11531359965950896952.b4-ty@oss.qualcomm.com> (raw)
In-Reply-To: <20260521-lecarc-acpi-ids-v1-0-ae0ae90b2817@lecomputing.com>
On Thu, 21 May 2026 10:34:48 +0800, Thomas Lin wrote:
> This patch series adds ACPI identification for LECARC SoCs that
> integrate Synopsys DesignWare peripherals.
>
> LECARC platforms use the following ACPI HIDs:
>
> GPIO: LECA0001 (V1 register offsets)
>
> [...]
Applied, thanks!
[1/2] gpio: dwapb: Add ACPI ID LECA0001 for LECARC SoCs
https://git.kernel.org/brgl/c/d01bf517cbbd5a4b0c16ba2d5107bda0e361b00c
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
next prev parent reply other threads:[~2026-05-21 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 2:34 Thomas Lin
2026-05-21 2:34 ` [PATCH 1/2] gpio: dwapb: Add ACPI ID LECA0001 for LECARC SoCs Thomas Lin
2026-05-21 2:34 ` [PATCH 2/2] spi: dw-mmio: Add ACPI ID LECA0002 " Thomas Lin
2026-05-21 8:49 ` Bartosz Golaszewski [this message]
2026-05-21 10:08 ` (subset) [PATCH 0/2] Subject: [PATCH v5 0/2] arm64: Add LECARC ACPI IDs for DesignWare GPIO, SPI Mark Brown
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=177935339258.17744.11531359965950896952.b4-ty@oss.qualcomm.com \
--to=bartosz.golaszewski@oss.qualcomm.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=braden_zhang@lecomputing.com \
--cc=brgl@kernel.org \
--cc=broonie@kernel.org \
--cc=hoan@os.amperecomputing.com \
--cc=lenb@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=thomas_lin@lecomputing.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®