From: Miquel Raynal <miquel.raynal@bootlin.com>
To: POPESCU Catalin <catalin.popescu@leica-geosystems.com>
Cc: "srinivas.kandagatla@linaro.org" <srinivas.kandagatla@linaro.org>,
"michael@walle.cc" <michael@walle.cc>,
"rafal@milecki.pl" <rafal@milecki.pl>,
"robh@kernel.org" <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
GEO-CHHER-bsp-development
<bsp-development.geo@leica-geosystems.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Luca Ceresoli <luca.ceresoli@bootlin.com>
Subject: Re: [PATCH] nvmem: fix issue within nvmem_register with fixed-layout.
Date: Tue, 5 Dec 2023 10:05:02 +0100 [thread overview]
Message-ID: <20231205100502.623863ff@xps-13> (raw)
In-Reply-To: <16c4c272-1a19-4fb8-8a2d-b2cf61ba37f2@leica-geosystems.com>
Hi Catalin,
+ GKH
+ Luca (who initially reported this issue)
catalin.popescu@leica-geosystems.com wrote on Tue, 5 Dec 2023 08:48:27
+0000:
> Adding more people.
>
> On 30.11.23 17:29, Catalin Popescu wrote:
> > fixed-layout is natively supported by NVMEM framework.
> > Yet, it's not been declared as a supported layout. As a
> > result, nvmem_register always returns -EPROBE_DEFER if
> > configuration has no layout and the NVMEM provider DT
> > uses a fixed layout.
> >
> > As a fix, declare fixed-layout as a supported layout
> > and use add_cells callback to parse the cells. This adds
> > consistency over layouts parsing as fixed-layout parsing
> > is handled in the same way than others nvmem layouts.
I believe this patch (not taken yet) should fix your issue and should be
queued to fixes.
Link: https://lore.kernel.org/lkml/20231124193814.360552-1-miquel.raynal@bootlin.com/
However I like your approach which should probably be taken into
consideration for the next cycle, as I think it fits Rafal's
original idea pretty well.
> >
> > Signed-off-by: Catalin Popescu <catalin.popescu@leica-geosystems.com>
> > ---
> > drivers/nvmem/core.c | 24 +++++++++++++++++-------
> > 1 file changed, 17 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
> > index bf42b7e826db..3467c94207e8 100644
> > --- a/drivers/nvmem/core.c
> > +++ b/drivers/nvmem/core.c
> > @@ -746,7 +746,9 @@ static int nvmem_add_cells_from_legacy_of(struct nvmem_device *nvmem)
> > return nvmem_add_cells_from_dt(nvmem, nvmem->dev.of_node);
> > }
> >
> > -static int nvmem_add_cells_from_fixed_layout(struct nvmem_device *nvmem)
> > +static int nvmem_add_cells_from_fixed_layout(struct device *dev,
> > + struct nvmem_device *nvmem,
> > + struct nvmem_layout *layout)
I've sent another series (on top of the fix mentioned above) to
simplify a bit this list of parameters, so both will conflict. But that
will be easy to solve.
Link: https://lore.kernel.org/lkml/20231129163737.698317-1-miquel.raynal@bootlin.com/
> > {
> > struct device_node *layout_np;
> > int err = 0;
> > @@ -755,8 +757,7 @@ static int nvmem_add_cells_from_fixed_layout(struct nvmem_device *nvmem)
> > if (!layout_np)
> > return 0;
> >
> > - if (of_device_is_compatible(layout_np, "fixed-layout"))
> > - err = nvmem_add_cells_from_dt(nvmem, layout_np);
> > + err = nvmem_add_cells_from_dt(nvmem, layout_np);
> >
> > of_node_put(layout_np);
> >
> > @@ -1003,10 +1004,6 @@ struct nvmem_device *nvmem_register(const struct nvmem_config *config)
> > goto err_remove_cells;
> > }
> >
> > - rval = nvmem_add_cells_from_fixed_layout(nvmem);
> > - if (rval)
> > - goto err_remove_cells;
> > -
> > rval = nvmem_add_cells_from_layout(nvmem);
> > if (rval)
> > goto err_remove_cells;
> > @@ -2126,6 +2123,19 @@ const char *nvmem_dev_name(struct nvmem_device *nvmem)
> > }
> > EXPORT_SYMBOL_GPL(nvmem_dev_name);
> >
> > +static const struct of_device_id fixed_layout_of_match_table[] = {
> > + { .compatible = "fixed-layout", },
> > + {},
> > +};
> > +MODULE_DEVICE_TABLE(of, fixed_layout_of_match_table);
> > +
> > +static struct nvmem_layout fixed_layout = {
> > + .name = "NVMEM fixed layout",
> > + .of_match_table = fixed_layout_of_match_table,
> > + .add_cells = nvmem_add_cells_from_fixed_layout,
> > +};
> > +module_nvmem_layout_driver(fixed_layout);
> > +
> > static int __init nvmem_init(void)
> > {
> > return bus_register(&nvmem_bus_type);
>
>
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
Thanks,
Miquèl
next prev parent reply other threads:[~2023-12-05 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 16:29 [PATCH] nvmem: fix issue within nvmem_register with fixed-layout Catalin Popescu
2023-12-05 8:48 ` POPESCU Catalin
2023-12-05 9:05 ` Miquel Raynal [this message]
2024-01-03 8:40 ` Miquel Raynal
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=20231205100502.623863ff@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=bsp-development.geo@leica-geosystems.com \
--cc=catalin.popescu@leica-geosystems.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=michael@walle.cc \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.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.