From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
acopo Mondi <jacopo+renesas@jmondi.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH v1 1/1] media: i2c: rdacm2x: Make use of device properties
Date: Mon, 31 Mar 2025 15:07:48 +0300 [thread overview]
Message-ID: <20250331120748.GB28722@pendragon.ideasonboard.com> (raw)
In-Reply-To: <174340899625.3687388.14660711739063778026@ping.linuxembedded.co.uk>
On Mon, Mar 31, 2025 at 09:16:36AM +0100, Kieran Bingham wrote:
> Quoting Andy Shevchenko (2025-03-31 08:34:35)
> > Convert the module to be property provider agnostic and allow
> > it to be used on non-OF platforms.
>
> Looks reasonable to me.
Is that going to work out of the box though ? The calls below read the
"reg" property to get the device I2C addresses. AFAIK, ACPI handles I2C
addresses using ACPI-specific methods.
Andy, have you tested this patch on an ACPI system ?
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> > drivers/media/i2c/rdacm20.c | 5 ++---
> > drivers/media/i2c/rdacm21.c | 5 ++---
> > 2 files changed, 4 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/media/i2c/rdacm20.c b/drivers/media/i2c/rdacm20.c
> > index b8bd8354d100..dcab63d19baf 100644
> > --- a/drivers/media/i2c/rdacm20.c
> > +++ b/drivers/media/i2c/rdacm20.c
> > @@ -16,10 +16,10 @@
> > */
> >
> > #include <linux/delay.h>
> > -#include <linux/fwnode.h>
> > #include <linux/init.h>
> > #include <linux/i2c.h>
> > #include <linux/module.h>
> > +#include <linux/property.h>
> > #include <linux/slab.h>
> > #include <linux/videodev2.h>
> >
> > @@ -575,8 +575,7 @@ static int rdacm20_probe(struct i2c_client *client)
> > dev->dev = &client->dev;
> > dev->serializer.client = client;
> >
> > - ret = of_property_read_u32_array(client->dev.of_node, "reg",
> > - dev->addrs, 2);
> > + ret = device_property_read_u32_array(&client->dev, "reg", dev->addrs, 2);
> > if (ret < 0) {
> > dev_err(dev->dev, "Invalid DT reg property: %d\n", ret);
>
> But this is no longer a DT reg property ?
>
> > return -EINVAL;
> > diff --git a/drivers/media/i2c/rdacm21.c b/drivers/media/i2c/rdacm21.c
> > index 3e22df36354f..5ea6988de48b 100644
> > --- a/drivers/media/i2c/rdacm21.c
> > +++ b/drivers/media/i2c/rdacm21.c
> > @@ -11,10 +11,10 @@
> > */
> >
> > #include <linux/delay.h>
> > -#include <linux/fwnode.h>
> > #include <linux/init.h>
> > #include <linux/i2c.h>
> > #include <linux/module.h>
> > +#include <linux/property.h>
> > #include <linux/slab.h>
> > #include <linux/videodev2.h>
> >
> > @@ -551,8 +551,7 @@ static int rdacm21_probe(struct i2c_client *client)
> > dev->dev = &client->dev;
> > dev->serializer.client = client;
> >
> > - ret = of_property_read_u32_array(client->dev.of_node, "reg",
> > - dev->addrs, 2);
> > + ret = device_property_read_u32_array(&client->dev, "reg", dev->addrs, 2);
> > if (ret < 0) {
> > dev_err(dev->dev, "Invalid DT reg property: %d\n", ret);
>
> Same here ...
>
> With those fixed,
>
> Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
>
> > return -EINVAL;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2025-03-31 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 7:34 Andy Shevchenko
2025-03-31 8:16 ` Kieran Bingham
2025-03-31 12:07 ` Laurent Pinchart [this message]
2025-03-31 12:23 ` Andy Shevchenko
2025-03-31 15:34 ` Laurent Pinchart
2025-03-31 16:22 ` Andy Shevchenko
2025-03-31 16:27 ` Laurent Pinchart
2025-03-31 16:33 ` 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=20250331120748.GB28722@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jacopo+renesas@jmondi.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®