From: Fabio Estevam <festevam@gmail.com>
To: Lucas Stach <dev@lynxeye.de>
Cc: "Shawn Guo" <shawnguo@kernel.org>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Guido Günther" <agx@sigxcpu.org>,
"Martin Kepplinger" <martink@posteo.de>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: imx8mq: disable DDRC node by default
Date: Sun, 12 Dec 2021 16:29:20 -0300 [thread overview]
Message-ID: <CAOMZO5An-zYdETHS5u99=YLLRmRDz4dOLBVOR0JHmk4WDg5_Zw@mail.gmail.com> (raw)
In-Reply-To: <20211212191541.2148178-1-dev@lynxeye.de>
Hi Lucas,
On Sun, Dec 12, 2021 at 4:16 PM Lucas Stach <dev@lynxeye.de> wrote:
>
> Without a OPP table or a downstream TF-A running on the system the DDRC will
> fail to probe, as it has no means to scale the DRAM frequency in that case.
> This however will block the bus scaling driver to come up and this in turn
> prevents other devices that hook into the interconnect from probing.
>
> If the DDRC is disabled, the interconnect driver will simply ignore it. As
> most systems don't want to scale the DRAM frequency, disable the node by
> default and only enable it on the systems that actually uses this
> capability and provides a valid OPP table in the DT.
>
> Signed-off-by: Lucas Stach <dev@lynxeye.de>
Reviewed-by: Fabio Estevam <festevam@gmail.com>
Should we do the same on imx8mm too?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-12 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 19:15 [PATCH] arm64: dts: imx8mq: disable DDRC node by default Lucas Stach
2021-12-12 19:29 ` Fabio Estevam [this message]
2021-12-13 14:36 ` Lucas Stach
2021-12-13 8:31 ` Martin Kepplinger
2021-12-13 8:34 ` Guido Günther
2021-12-16 5:58 ` Shawn Guo
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='CAOMZO5An-zYdETHS5u99=YLLRmRDz4dOLBVOR0JHmk4WDg5_Zw@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=agx@sigxcpu.org \
--cc=dev@lynxeye.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=martink@posteo.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.