All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saravana Kannan <saravanak@google.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org,
	Shawn Guo <shawnguo@kernel.org>,
	 kernel@pengutronix.de
Subject: Re: [PATCH] ARM: imx: drop devlinks to reset-controller node
Date: Tue, 21 Sep 2021 09:47:43 -0700	[thread overview]
Message-ID: <CAGETcx_wr0=FKRNmbGfN7Emg=2XooWFZx5jwX4ZfbTPZCMaPEQ@mail.gmail.com> (raw)
In-Reply-To: <30a8de2b70fba9046dfcc8d19faf5b44870493e2.camel@pengutronix.de>

Hi Philipp,

On Tue, Sep 21, 2021 at 8:05 AM Philipp Zabel <p.zabel@pengutronix.de> wrote:
>
> Hi Saravana,
>
> On Tue, 2021-09-21 at 07:45 -0700, Saravana Kannan wrote:
> > On Tue, Sep 21, 2021 at 5:50 AM Philipp Zabel <p.zabel@pengutronix.de> wrote:
> > > Starting with commit 6b2117ad65f1 ("of: property: fw_devlink: Add
> > > support for "resets" and "pwms""), the imx-drm driver fails to load
> > > due to forever dormant devlinks to the reset-controller node. This
> > > node is never associated with a struct device.
> > >
> > > Drop those links, the reset controller is always available.
> > >
> > > Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> > > ---
> > >  arch/arm/mach-imx/src.c | 10 +++++++++-
> > >  1 file changed, 9 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/arch/arm/mach-imx/src.c b/arch/arm/mach-imx/src.c
> > > index 95fd1fbb0826..6924ac19a762 100644
> > > --- a/arch/arm/mach-imx/src.c
> > > +++ b/arch/arm/mach-imx/src.c
> > > @@ -178,9 +178,17 @@ void __init imx_src_init(void)
> > >         WARN_ON(!src_base);
> > >
> > >         imx_reset_controller.of_node = np;
> > > -       if (IS_ENABLED(CONFIG_RESET_CONTROLLER))
> > > +       if (IS_ENABLED(CONFIG_RESET_CONTROLLER)) {
> > >                 reset_controller_register(&imx_reset_controller);
> > >
> > > +               /*
> > > +                * The reset-controller node is never associated with a struct
> > > +                * device, which trips up fw_devlink=on. As a workaround, drop
> > > +                * all devlinks to/from this node.
> > > +                */
> > > +               fw_devlink_purge_absent_suppliers(&np->fwnode);
> > > +       }
> > > +
> >
> > Hey Philipp,
> >
> > Can you point me to the .dts file that corresponds to this platform? I
> > want to take a closer look.
>
> Thank you, the relevant file is arch/arm/boot/dts/imx6qdl.dtsi, device
> nodes labeled as &src and &ipu1. This is for example included by
> arch/arm/boot/dts/imx6q-nitrogen6x.dts. There's a second &ipu2 added in
> arch/arm/boot/dts/imx6qd.dtsi as well.

I took a closer look at the DT. Is there really no struct device for
this node? Based on the DT, it looks like a device would automatically
get created for this node. So it looks like it's more of an issue with
the device not being probed by a real driver? Why can't you convert
the reset controller driver to a proper platform driver instead of
this patch? I think that's the right fix.

-Saravana

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-09-21 16:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21 12:50 [PATCH] ARM: imx: drop devlinks to reset-controller node Philipp Zabel
2021-09-21 13:19 ` Fabio Estevam
2021-09-21 15:19   ` Philipp Zabel
2021-09-21 15:38     ` Saravana Kannan
2021-09-21 14:45 ` Saravana Kannan
2021-09-21 15:04   ` Philipp Zabel
2021-09-21 15:45     ` Saravana Kannan
2021-09-21 16:47     ` Saravana Kannan [this message]
2021-09-22 14:12       ` Philipp Zabel
2021-09-22 15:38         ` Saravana Kannan
2021-09-22 16:31           ` Philipp Zabel
2021-09-22 17:30             ` Saravana Kannan
2021-09-23  8:17             ` Michael Tretter

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='CAGETcx_wr0=FKRNmbGfN7Emg=2XooWFZx5jwX4ZfbTPZCMaPEQ@mail.gmail.com' \
    --to=saravanak@google.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=p.zabel@pengutronix.de \
    --cc=shawnguo@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.