From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Rob Herring <robh@kernel.org>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Saravana Kannan <saravanak@google.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Subject: Re: [PATCH 1/2] of: property: add of_property_for_each_u64
Date: Fri, 28 Jun 2024 16:16:17 +0200 [thread overview]
Message-ID: <20240628161617.6bc9ca3c@booty> (raw)
In-Reply-To: <AM6PR04MB5941D30C26F2CB818FEC082C88D02@AM6PR04MB5941.eurprd04.prod.outlook.com>
Hello Peng,
On Fri, 28 Jun 2024 13:10:34 +0000
Peng Fan <peng.fan@nxp.com> wrote:
> > Subject: RE: [PATCH 1/2] of: property: add of_property_for_each_u64
> >
> > > Subject: Re: [PATCH 1/2] of: property: add of_property_for_each_u64
> > >
> > > +Luca
> > >
> > > On Fri, Jun 21, 2024 at 08:36:39PM +0800, Peng Fan (OSS) wrote:
> > > > From: Peng Fan <peng.fan@nxp.com>
> > > >
> > > > Preparing for assigned-clock-rates-u64 support, add function
> > > > of_property_for_each_u64 to iterate each u64 value
> > > >
> > > > Signed-off-by: Peng Fan <peng.fan@nxp.com>
> > > > ---
> > > > drivers/of/property.c | 23 +++++++++++++++++++++++
> > > > include/linux/of.h | 24 ++++++++++++++++++++++++
> > > > 2 files changed, 47 insertions(+)
> > > >
> > > > diff --git a/drivers/of/property.c b/drivers/of/property.c index
> > > > 164d77cb9445..b89c3ab01d44 100644
> > > > --- a/drivers/of/property.c
> > > > +++ b/drivers/of/property.c
> > > > @@ -548,6 +548,29 @@ const __be32 *of_prop_next_u32(struct
> > > property
> > > > *prop, const __be32 *cur, }
> > > EXPORT_SYMBOL_GPL(of_prop_next_u32);
> > > >
> > > > +const __be32 *of_prop_next_u64(struct property *prop, const
> > > __be32 *cur,
> > > > + u64 *pu)
> > >
> > > struct property can be const
> >
> > Fix in v2. BTW, I am thinking something as below:
> >
> > const __be64 *of_prop_next_u64(const struct property *prop, const
> > __be64 *cur,
> > u64 *pu)
> > {
> > const void *curv = cur;
> >
> > if (!prop)
> > return NULL;
> >
> > if (!cur) {
> > curv = prop->value;
> > goto out_val;
> > }
> >
> > curv += sizeof(*cur);
> > if (curv >= prop->value + prop->length)
> > return NULL;
> >
> > out_val:
> > *pu = be64_to_cpup(curv);
> > return curv;
> > }
> > EXPORT_SYMBOL_GPL(of_prop_next_u64);
> >
> > >
> > > > +{
> > > > + const void *curv = cur;
> > > > +
> > > > + if (!prop)
> > > > + return NULL;
> > > > +
> > > > + if (!cur) {
> > > > + curv = prop->value;
> > > > + goto out_val;
> > > > + }
> > > > +
> > > > + curv += sizeof(*cur) * 2;
> > > > + if (curv >= prop->value + prop->length)
> > > > + return NULL;
> > > > +
> > > > +out_val:
> > > > + *pu = of_read_number(curv, 2);
> > > > + return curv;
> > > > +}
> > > > +EXPORT_SYMBOL_GPL(of_prop_next_u64);
> > > > +
> > > > const char *of_prop_next_string(struct property *prop, const char
> > > > *cur) {
> > > > const void *curv = cur;
> > > > diff --git a/include/linux/of.h b/include/linux/of.h index
> > > > 13cf7a43b473..464eca6a4636 100644
> > > > --- a/include/linux/of.h
> > > > +++ b/include/linux/of.h
> > > > @@ -439,6 +439,18 @@ extern int of_detach_node(struct
> > > device_node *);
> > > > */
> > > > const __be32 *of_prop_next_u32(struct property *prop, const
> > > __be32 *cur,
> > > > u32 *pu);
> > > > +
> > > > +/*
> > > > + * struct property *prop;
> > > > + * const __be32 *p;
> > > > + * u64 u;
> > > > + *
> > > > + * of_property_for_each_u64(np, "propname", prop, p, u)
> > > > + * printk("U64 value: %llx\n", u);
> > > > + */
> > > > +const __be32 *of_prop_next_u64(struct property *prop, const
> > > __be32 *cur,
> > > > + u64 *pu);
> > > > +
> > > > /*
> > > > * struct property *prop;
> > > > * const char *s;
> > > > @@ -834,6 +846,12 @@ static inline const __be32
> > > *of_prop_next_u32(struct property *prop,
> > > > return NULL;
> > > > }
> > > >
> > > > +static inline const __be32 *of_prop_next_u64(struct property
> > *prop,
> > > > + const __be32 *cur, u64 *pu)
> > > > +{
> > > > + return NULL;
> > > > +}
> > > > +
> > > > static inline const char *of_prop_next_string(struct property *prop,
> > > > const char *cur)
> > > > {
> > > > @@ -1437,6 +1455,12 @@ static inline int
> > > of_property_read_s32(const struct device_node *np,
> > > > p; \
> > > > p = of_prop_next_u32(prop, p, &u))
> > > >
> > > > +#define of_property_for_each_u64(np, propname, prop, p, u) \
> > > > + for (prop = of_find_property(np, propname, NULL), \
> > > > + p = of_prop_next_u64(prop, NULL, &u); \
> > > > + p; \
> > > > + p = of_prop_next_u64(prop, p, &u))
> > >
> > > I think we want to define this differently to avoid exposing struct
> > > property and the property data directly. Like this:
> > >
> > > #define of_property_for_each_u64(np, propname, u) \
> > > for (struct property *_prop = of_find_property(np, propname, NULL),
> > > const __be32 *_p = of_prop_next_u64(_prop, NULL, &u);
> > > _p;
> > > _p = of_prop_next_u64(_prop, _p, &u))
>
> This will trigger a compilation error, because C not allow
> declare two variables with different types as for loop expression 1.
> Need to think about other methods.
I have a working draft here where I solved it somehow, let me just find
the proper branch and send it. Perhaps next week, but I'm striving to do
that by Mon-Tue.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-06-28 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 12:36 [PATCH 0/2] clk: add assigned-clock-rates-u64 Peng Fan (OSS)
2024-06-21 12:36 ` [PATCH 1/2] of: property: add of_property_for_each_u64 Peng Fan (OSS)
2024-06-27 21:43 ` Rob Herring
2024-06-28 12:33 ` Peng Fan
2024-06-28 13:10 ` Peng Fan
2024-06-28 14:16 ` Luca Ceresoli [this message]
2024-07-03 10:42 ` Luca Ceresoli
2024-06-21 12:36 ` [PATCH 2/2] clk: clk-conf: support assigned-clock-rates-u64 Peng Fan (OSS)
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=20240628161617.6bc9ca3c@booty \
--to=luca.ceresoli@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.