From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: <Steen.Hegelund@microchip.com>, <daniel.machon@microchip.com>,
<UNGLinuxDriver@microchip.com>, <herve.codina@bootlin.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] reset: mchp: sparx5: Fix for lan966x
Date: Thu, 27 Feb 2025 09:51:48 +0100 [thread overview]
Message-ID: <20250227085148.ulqc2n7xvc2fa745@DEN-DL-M31836.microchip.com> (raw)
In-Reply-To: <5cc5cd05e0a481773212fff0bce574dcfea3f74d.camel@pengutronix.de>
The 02/26/2025 17:32, Philipp Zabel wrote:
Hi,
>
> On Mi, 2025-02-26 at 15:46 +0100, Horatiu Vultur wrote:
> > With the blamed commit it seems that lan966x doesn't seem to boot
> > anymore when the internal CPU is used.
> > The reason seems to be the usage of the devm_of_iomap, if we replace
> > this with of_iomap, this seems to fix the issue as we use the same
> ^^^^^^^^
> The is not accurate anymore.
Good catch. I will update in the next version.
>
> > region also for other devices.
> >
> > Fixes: 0426a920d6269c ("reset: mchp: sparx5: Map cpu-syscon locally in case of LAN966x")
> > Reviewed-by: Herve Codina <herve.codina@bootlin.com>
> > Tested-by: Herve Codina <herve.codina@bootlin.com>
>
> Is this still correct?
>
> > Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> > ---
> > v2->v3:
> > - forward error from of_address_to_resource
> > - use devm_ioremap instead of_iomap
> > v1->v2:
> > - make sure to use iounmap when driver is removed
> > ---
> > drivers/reset/reset-microchip-sparx5.c | 16 +++++++++++-----
> > 1 file changed, 11 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/reset/reset-microchip-sparx5.c b/drivers/reset/reset-microchip-sparx5.c
> > index aa5464be7053b..176b3f46e9243 100644
> > --- a/drivers/reset/reset-microchip-sparx5.c
> > +++ b/drivers/reset/reset-microchip-sparx5.c
> > @@ -8,6 +8,7 @@
> > */
> > #include <linux/mfd/syscon.h>
> > #include <linux/of.h>
> > +#include <linux/of_address.h>
> > #include <linux/module.h>
> > #include <linux/platform_device.h>
> > #include <linux/property.h>
> > @@ -72,14 +73,19 @@ static struct regmap *mchp_lan966x_syscon_to_regmap(struct device *dev,
> > struct device_node *syscon_np)
> > {
> > struct regmap_config regmap_config = mchp_lan966x_syscon_regmap_config;
> > - resource_size_t size;
> > + struct resource res;
> > void __iomem *base;
> > + int err;
> > +
> > + err = of_address_to_resource(syscon_np, 0, &res);
> > + if (err)
> > + return ERR_PTR(err);
> >
> > - base = devm_of_iomap(dev, syscon_np, 0, &size);
> > - if (IS_ERR(base))
> > - return ERR_CAST(base);
>
> It would be nice to add a comment here that devm_of_iomap() can't be
> used because the resource is shared with other devices. Do you know
> which ones?
Yes, I will add a comment in the next version.
Looking at the device trees (lan966x.dtsi), it looks like it is shared
with the clock driver (clks).
>
> Otherwise, this looks good to me.
>
>
> regards
> Philipp
--
/Horatiu
prev parent reply other threads:[~2025-02-27 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 14:46 Horatiu Vultur
2025-02-26 16:32 ` Philipp Zabel
2025-02-26 17:24 ` Herve Codina
2025-02-27 10:25 ` Philipp Zabel
2025-02-27 8:51 ` Horatiu Vultur [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=20250227085148.ulqc2n7xvc2fa745@DEN-DL-M31836.microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=daniel.machon@microchip.com \
--cc=herve.codina@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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®