From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Anand Ashok Dumbre <anand.ashok.dumbre@xilinx.com>
Cc: linux-kernel@vger.kernel.org, jic23@kernel.org, lars@metafoo.de,
linux-iio@vger.kernel.org, git@xilinx.com,
michal.simek@xilinx.com, gregkh@linuxfoundation.org,
rafael@kernel.org, linux-acpi@vger.kernel.org,
heikki.krogerus@linux.intel.com
Subject: Re: [PATCH v9 1/5] device property: Add fwnode_iomap()
Date: Tue, 16 Nov 2021 19:07:33 +0200 [thread overview]
Message-ID: <YZPlVfYjXWiOm+Mg@smile.fi.intel.com> (raw)
In-Reply-To: <20211116150842.1051-2-anand.ashok.dumbre@xilinx.com>
On Tue, Nov 16, 2021 at 03:08:38PM +0000, Anand Ashok Dumbre wrote:
> This patch introduces a new helper routine - fwnode_iomap(), which
> allows to map the memory mapped IO for a given device node.
>
> This implementation does not cover the ACPI case and may be expanded
> in the future. The main purpose here is to be able to develop resource
> provider agnostic drivers.
Thanks! LGTM,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
TWIMC I have some ideas about ACPI implementation. Just let this one
settled first.
> Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Signed-off-by: Anand Ashok Dumbre <anand.ashok.dumbre@xilinx.com>
> ---
> drivers/base/property.c | 16 ++++++++++++++++
> include/linux/property.h | 2 ++
> 2 files changed, 18 insertions(+)
>
> diff --git a/drivers/base/property.c b/drivers/base/property.c
> index 453918eb7390..d2cca7ffea18 100644
> --- a/drivers/base/property.c
> +++ b/drivers/base/property.c
> @@ -1021,6 +1021,22 @@ int fwnode_irq_get(const struct fwnode_handle *fwnode, unsigned int index)
> }
> EXPORT_SYMBOL(fwnode_irq_get);
>
> +/**
> + * fwnode_iomap - Maps the memory mapped IO for a given fwnode
> + * @fwnode: Pointer to the firmware node
> + * @index: Index of the IO range
> + *
> + * Returns a pointer to the mapped memory.
> + */
> +void __iomem *fwnode_iomap(struct fwnode_handle *fwnode, int index)
> +{
> + if (is_of_node(fwnode))
> + return of_iomap(to_of_node(fwnode), index);
> +
> + return NULL;
> +}
> +EXPORT_SYMBOL(fwnode_iomap);
> +
> /**
> * fwnode_graph_get_next_endpoint - Get next endpoint firmware node
> * @fwnode: Pointer to the parent firmware node
> diff --git a/include/linux/property.h b/include/linux/property.h
> index 357513a977e5..9bb0b0155402 100644
> --- a/include/linux/property.h
> +++ b/include/linux/property.h
> @@ -121,6 +121,8 @@ void fwnode_handle_put(struct fwnode_handle *fwnode);
>
> int fwnode_irq_get(const struct fwnode_handle *fwnode, unsigned int index);
>
> +void __iomem *fwnode_iomap(struct fwnode_handle *fwnode, int index);
> +
> unsigned int device_get_child_node_count(struct device *dev);
>
> static inline bool device_property_read_bool(struct device *dev,
> --
> 2.17.1
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-11-16 17:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 15:08 [PATCH v9 0/5] Add Xilinx AMS Driver Anand Ashok Dumbre
2021-11-16 15:08 ` [PATCH v9 1/5] device property: Add fwnode_iomap() Anand Ashok Dumbre
2021-11-16 17:07 ` Andy Shevchenko [this message]
2021-11-16 15:08 ` [PATCH v9 2/5] arm64: zynqmp: DT: Add Xilinx AMS node Anand Ashok Dumbre
2021-11-16 17:39 ` Andy Shevchenko
2021-11-16 18:55 ` Anand Ashok Dumbre
2021-11-16 15:08 ` [PATCH v9 3/5] iio: adc: Add Xilinx AMS driver Anand Ashok Dumbre
2021-11-16 17:38 ` Andy Shevchenko
2021-11-16 20:29 ` Anand Ashok Dumbre
2021-11-17 12:48 ` Andy Shevchenko
2021-11-16 15:08 ` [PATCH v9 4/5] dt-bindings: iio: adc: Add Xilinx AMS binding documentation Anand Ashok Dumbre
2021-11-16 15:08 ` [PATCH v9 5/5] MAINTAINERS: Add maintainer for xilinx-ams Anand Ashok Dumbre
2021-11-16 17:41 ` Andy Shevchenko
2021-11-17 14:34 ` Anand Ashok Dumbre
2021-11-17 15:17 ` Andy Shevchenko
2021-11-17 16:05 ` Joe Perches
2021-11-17 17:08 ` Andy Shevchenko
2021-11-17 18:46 ` Joe Perches
2021-11-17 19:28 ` Andy Shevchenko
2021-11-17 23:06 ` Joe Perches
2021-11-17 21:57 ` Anand Ashok Dumbre
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=YZPlVfYjXWiOm+Mg@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=anand.ashok.dumbre@xilinx.com \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.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