From: "Nuno Sá" <noname.nuno@gmail.com>
To: "Angelo Dureghello" <adureghello@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Olivier Moysan" <olivier.moysan@foss.st.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, dlechner@baylibre.com,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v7 8/8] iio: dac: adi-axi-dac: add registering of child fdt node
Date: Tue, 22 Oct 2024 14:02:44 +0200 [thread overview]
Message-ID: <8cba678ee61eb221f8d5deb786a69b547371f11c.camel@gmail.com> (raw)
In-Reply-To: <20241021-wip-bl-ad3552r-axi-v0-iio-testing-v7-8-969694f53c5d@baylibre.com>
On Mon, 2024-10-21 at 14:40 +0200, Angelo Dureghello wrote:
> From: Angelo Dureghello <adureghello@baylibre.com>
>
> Change to obtain the fdt use case as reported in the
> adi,ad3552r.yaml file in this patchset.
>
> The DAC device is defined as a child node of the backend.
> Registering the child fdt node as a platform devices.
>
> Signed-off-by: Angelo Dureghello <adureghello@baylibre.com>
> ---
> drivers/iio/dac/adi-axi-dac.c | 53
> +++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 53 insertions(+)
>
> diff --git a/drivers/iio/dac/adi-axi-dac.c b/drivers/iio/dac/adi-axi-dac.c
> index 9d6809fe7a67..7f7ef3e219ba 100644
> --- a/drivers/iio/dac/adi-axi-dac.c
> +++ b/drivers/iio/dac/adi-axi-dac.c
> @@ -29,6 +29,8 @@
> #include <linux/iio/buffer.h>
> #include <linux/iio/iio.h>
>
> +#include "ad3552r-hs.h"
> +
> /*
> * Register definitions:
> * https://wiki.analog.com/resources/fpga/docs/axi_dac_ip#register_map
> @@ -97,6 +99,7 @@ struct axi_dac_info {
> unsigned int version;
> const struct iio_backend_info *backend_info;
> bool has_dac_clk;
> + bool has_child_nodes;
> };
>
> struct axi_dac_state {
> @@ -723,6 +726,35 @@ static int axi_dac_bus_reg_read(struct iio_backend *back,
> u32 reg, u32 *val,
> return regmap_read(st->regmap, AXI_DAC_CUSTOM_RD_REG, val);
> }
>
> +static void axi_dac_child_remove(void *data)
> +{
> + platform_device_unregister(data);
> +}
> +
> +static int axi_dac_create_platform_device(struct axi_dac_state *st,
> + struct fwnode_handle *child)
> +{
> + struct ad3552r_hs_platform_data pdata = {
> + .bus_reg_read = axi_dac_bus_reg_read,
> + .bus_reg_write = axi_dac_bus_reg_write,
> + };
> + struct platform_device_info pi = {
> + .parent = st->dev,
> + .name = fwnode_get_name(child),
> + .id = PLATFORM_DEVID_AUTO,
> + .fwnode = child,
> + .data = &pdata,
> + .size_data = sizeof(pdata),
> + };
> + struct platform_device *pdev;
> +
> + pdev = platform_device_register_full(&pi);
> + if (IS_ERR(pdev))
> + return PTR_ERR(pdev);
> +
> + return devm_add_action_or_reset(st->dev, axi_dac_child_remove, pdev);
> +}
> +
> static const struct iio_backend_ops axi_dac_generic_ops = {
> .enable = axi_dac_enable,
> .disable = axi_dac_disable,
> @@ -865,6 +897,26 @@ static int axi_dac_probe(struct platform_device *pdev)
> return dev_err_probe(&pdev->dev, ret,
> "failed to register iio backend\n");
>
> + if (st->info->has_child_nodes) {
I would prefer to not be silent on possible misconfigurations. IOW, moving the
check inside the loop and error out if (!st->info->has_child_nodes)
- Nuno Sá
prev parent reply other threads:[~2024-10-22 11:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 12:40 [PATCH v7 0/8] iio: add support for the ad3552r AXI DAC IP Angelo Dureghello
2024-10-21 12:40 ` [PATCH v7 1/8] dt-bindings: iio: dac: ad3552r: add iio backend support Angelo Dureghello
2024-10-21 12:40 ` [PATCH v7 2/8] dt-bindings: iio: dac: adi-axi-dac: add ad3552r axi variant Angelo Dureghello
2024-10-22 17:22 ` Conor Dooley
2024-10-24 9:28 ` Angelo Dureghello
2024-10-24 12:37 ` Nuno Sá
2024-10-24 14:43 ` David Lechner
2024-10-24 16:45 ` Conor Dooley
2024-10-21 12:40 ` [PATCH v7 3/8] iio: backend: extend features Angelo Dureghello
2024-10-21 12:40 ` [PATCH v7 4/8] iio: dac: adi-axi-dac: " Angelo Dureghello
2024-10-22 12:36 ` Nuno Sá
2024-10-22 17:21 ` Conor Dooley
2024-10-23 14:56 ` Nuno Sá
2024-10-23 15:22 ` Conor Dooley
2024-10-24 7:04 ` Nuno Sá
2024-10-24 10:29 ` Angelo Dureghello
2024-10-26 17:31 ` Jonathan Cameron
2024-10-21 12:40 ` [PATCH v7 5/8] iio: dac: ad3552r: changes to use FIELD_PREP Angelo Dureghello
2024-10-21 12:40 ` [PATCH v7 6/8] iio: dac: ad3552r: extract common code (no changes in behavior intended) Angelo Dureghello
2024-10-21 12:40 ` [PATCH v7 7/8] iio: dac: ad3552r: add high-speed platform driver Angelo Dureghello
2024-10-22 12:28 ` Nuno Sá
2024-10-22 16:40 ` Angelo Dureghello
2024-10-24 13:05 ` Nuno Sá
2024-10-24 15:02 ` Angelo Dureghello
2024-10-24 15:13 ` David Lechner
2024-10-26 17:35 ` Jonathan Cameron
2024-10-25 6:13 ` Nuno Sá
2024-10-21 12:40 ` [PATCH v7 8/8] iio: dac: adi-axi-dac: add registering of child fdt node Angelo Dureghello
2024-10-22 12:02 ` Nuno Sá [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=8cba678ee61eb221f8d5deb786a69b547371f11c.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=adureghello@baylibre.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.com \
--cc=robh@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).