From: Marek Vasut <marex@denx.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Paul Elder <paul.elder@ideasonboard.com>,
Lucas Stach <l.stach@pengutronix.de>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 1/4] dt-bindings: soc: Add i.MX8MP media block control DT bindings
Date: Tue, 22 Mar 2022 22:29:56 +0100 [thread overview]
Message-ID: <3f7bdca8-0da7-fe2d-7bcb-9768b12bb759@denx.de> (raw)
In-Reply-To: <20220322190324.12589-2-laurent.pinchart@ideasonboard.com>
On 3/22/22 20:03, Laurent Pinchart wrote:
> From: Paul Elder <paul.elder@ideasonboard.com>
>
> The i.MX8MP Media Block Control (MEDIA BLK_CTRL) is a top-level
> peripheral providing access to the NoC and ensuring proper power
> sequencing of the peripherals within the MEDIAMIX domain. Add DT
> bindings for it.
>
> There is already a driver for block controls of other SoCs in the i.MX8M
> family, so these bindings will expand upon that.
>
> Signed-off-by: Paul Elder <paul.elder@ideasonboard.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Marek Vasut <marex@denx.de>
[...]
> + power-domain-names = "bus", "mipi-dsi1", "mipi-csi1", "lcdif1", "isi",
> + "mipi-csi2", "lcdif2", "isp2", "isp1", "dwe",
> + "mipi-dsi2";
Nit, I cannot say I'm a big fan of calling the power domain "mipi-csi1"
and "mipi-csi2", they are both MIPI CSI2, except there are two of them
CSI2 (#1 and #2).
Maybe mipi-csi2-1 and mipi-csi2-2 would be better ? DTTO for the LCDIF,
where we have lcdifv3 and then mx8mp lcdifv3 and eventually we will have
power domain for lcdif #3 instance in this SoC in hdmimix, so maybe some
lcdif-1/lcdif-2 would be a better name ?
[...]
next prev parent reply other threads:[~2022-03-22 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 19:03 [PATCH v2 0/4] imx8mp: Add media block control Laurent Pinchart
2022-03-22 19:03 ` [PATCH v2 1/4] dt-bindings: soc: Add i.MX8MP media block control DT bindings Laurent Pinchart
2022-03-22 21:29 ` Marek Vasut [this message]
2022-03-22 21:57 ` Laurent Pinchart
2022-03-22 22:01 ` Marek Vasut
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=3f7bdca8-0da7-fe2d-7bcb-9768b12bb759@denx.de \
--to=marex@denx.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=paul.elder@ideasonboard.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox