From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1 2/2] ACPI: LPSS: Advertise number of chip selects via property
Date: Tue, 2 Apr 2024 18:28:53 +0300 [thread overview]
Message-ID: <20240402152952.3578659-3-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20240402152952.3578659-1-andriy.shevchenko@linux.intel.com>
Advertise number of chip selects via property for Intel Braswell.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
drivers/acpi/acpi_lpss.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/acpi/acpi_lpss.c b/drivers/acpi/acpi_lpss.c
index 5b56f198d005..a3d2d94be5c0 100644
--- a/drivers/acpi/acpi_lpss.c
+++ b/drivers/acpi/acpi_lpss.c
@@ -325,6 +325,7 @@ static const struct lpss_device_desc bsw_i2c_dev_desc = {
static const struct property_entry bsw_spi_properties[] = {
PROPERTY_ENTRY_U32("intel,spi-pxa2xx-type", LPSS_BSW_SSP),
+ PROPERTY_ENTRY_U32("num-cs", 2),
{ }
};
--
2.43.0.rc1.1.gbec44491f096
next prev parent reply other threads:[~2024-04-02 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 15:28 [PATCH v1 0/2] ACPI: LPSS: Prepare for SPI code cleanup Andy Shevchenko
2024-04-02 15:28 ` [PATCH v1 1/2] ACPI: LPSS: Remove nested ifdeffery for CONFIG_PM Andy Shevchenko
2024-04-02 15:28 ` Andy Shevchenko [this message]
2024-04-04 10:58 ` [PATCH v1 2/2] ACPI: LPSS: Advertise number of chip selects via property Rafael J. Wysocki
2024-04-04 11:57 ` Andy Shevchenko
2024-04-02 18:58 ` [PATCH v1 0/2] ACPI: LPSS: Prepare for SPI code cleanup Andy Shevchenko
2024-04-02 21:18 ` Kuppuswamy Sathyanarayanan
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=20240402152952.3578659-3-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
/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