From: chengwei <foxfly.lai.tw@gmail.com>
To: lee@kernel.org, broonie@kernel.org, rafael@kernel.org,
mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com, linus.walleij@linaro.org,
brgl@bgdev.pl
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-gpio@vger.kernel.org, GaryWang@aaeon.com.tw,
musa.lin@yunjingtech.com, jack.chang@yunjingtech.com,
chengwei <larry.lai@yunjingtech.com>
Subject: [PATCH 3/5] ACPI: acpi_node_add_pin_mapping added to header file
Date: Wed, 19 Oct 2022 10:24:48 +0800 [thread overview]
Message-ID: <20221019022450.16851-4-larry.lai@yunjingtech.com> (raw)
In-Reply-To: <20221019022450.16851-1-larry.lai@yunjingtech.com>
Declare acpi_node_add_pin_mapping added for pinctrl-upboard
reference.
Signed-off-by: chengwei <larry.lai@yunjingtech.com>
---
include/linux/acpi.h | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/include/linux/acpi.h b/include/linux/acpi.h
index 6f64b2f3dc54..7b4668342de0 100644
--- a/include/linux/acpi.h
+++ b/include/linux/acpi.h
@@ -1203,6 +1203,11 @@ bool acpi_gpio_get_irq_resource(struct acpi_resource *ares,
bool acpi_gpio_get_io_resource(struct acpi_resource *ares,
struct acpi_resource_gpio **agpio);
int acpi_dev_gpio_irq_get_by(struct acpi_device *adev, const char *name, int index);
+int acpi_node_add_pin_mapping(struct fwnode_handle *fwnode,
+ const char *propname,
+ const char *pinctl_name,
+ unsigned int pin_offset,
+ unsigned int npins);
#else
static inline bool acpi_gpio_get_irq_resource(struct acpi_resource *ares,
struct acpi_resource_gpio **agpio)
@@ -1219,6 +1224,15 @@ static inline int acpi_dev_gpio_irq_get_by(struct acpi_device *adev,
{
return -ENXIO;
}
+
+static inline int acpi_node_add_pin_mapping(struct fwnode_handle *fwnode,
+ const char *propname,
+ const char *pinctl_name,
+ unsigned int pin_offset,
+ unsigned int npins)
+{
+ return -ENXIO;
+}
#endif
static inline int acpi_dev_gpio_irq_get(struct acpi_device *adev, int index)
--
2.17.1
next prev parent reply other threads:[~2022-10-19 2:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 2:24 [PATCH 0/5] Add support control UP board CPLD/FPGA pin control chengwei
2022-10-19 2:24 ` [PATCH 1/5] mfd: Add support for UP board CPLD/FPGA chengwei
2022-10-31 14:58 ` Lee Jones
[not found] ` <SG2PR06MB37422173908A6584B3D6D349F93F9@SG2PR06MB3742.apcprd06.prod.outlook.com>
2022-11-08 15:53 ` 回覆: " gregkh
[not found] ` <SG2PR06MB3742D3714B6A255914DC73E4F93F9@SG2PR06MB3742.apcprd06.prod.outlook.com>
2022-11-08 17:24 ` gregkh
2022-11-14 10:09 ` Lee Jones
2022-10-19 2:24 ` [PATCH 2/5] regmap: Expose regmap_writeable function to check if a register is writable chengwei
2022-10-19 11:57 ` Mark Brown
2022-10-19 2:24 ` chengwei [this message]
2022-10-19 13:32 ` [PATCH 3/5] ACPI: acpi_node_add_pin_mapping added to header file Andy Shevchenko
2022-10-19 2:24 ` [PATCH 4/5] GPIO ACPI: Add support to map GPIO resources to ranges chengwei
2022-10-19 13:36 ` Andy Shevchenko
2022-10-19 2:24 ` [PATCH 5/5] pinctrl: Add support pin control for UP board CPLD/FPGA chengwei
2022-10-20 16:58 ` Andy Shevchenko
2022-10-21 9:09 ` Linus Walleij
2022-10-21 10:55 ` Andy Shevchenko
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=20221019022450.16851-4-larry.lai@yunjingtech.com \
--to=foxfly.lai.tw@gmail.com \
--cc=GaryWang@aaeon.com.tw \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jack.chang@yunjingtech.com \
--cc=larry.lai@yunjingtech.com \
--cc=lee@kernel.org \
--cc=lenb@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=musa.lin@yunjingtech.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;
as well as URLs for NNTP newsgroup(s).