From: Liu Ying <victor.liu@nxp.com>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
saravanak@google.com, gregkh@linuxfoundation.org,
geert+renesas@glider.be, krzysztof.kozlowski@linaro.org,
robh@kernel.org
Subject: [PATCH v3 0/3] drivers: bus: Add Freescale i.MX8qxp pixel link MSI bus support
Date: Thu, 4 Aug 2022 14:11:30 +0800 [thread overview]
Message-ID: <20220804061133.4110734-1-victor.liu@nxp.com> (raw)
Hi,
This series aims to add Freescale i.MX8qxp pixel link MSI bus support
by using the existing simple-pm-bus driver. A power domain and two input
clocks need to be enabled before the MSI bus accesses it's child devices,
which matches what a simple power-managed bus is(See simple-pm-bus.yaml).
Patch 1 adds support to populate simple MFD child devices in the
simple-pm-bus driver, since the MSI bus may connect those devices.
Patch 2 enables/disables functional clock(s) as a bulk in the
simple-pm-bus driver when the simple-pm-bus is being power managed,
since the MSI bus takes the two input clocks as functional clocks.
Patch 3 adds dt-bindings for the MSI bus.
v2->v3:
* Add a pattern property to allow child nodes in the MSI bus dt-binding. (Rob)
v1->v2:
Address Krzysztof's comments on patch 3:
* Add a select to explicitly select the MSI bus dt-binding.
* List 'simple-pm-bus' explicitly as one item of compatible strings.
* Require compatible and reg properties.
* Put reg property just after compatible property in example.
Liu Ying (3):
drivers: bus: simple-pm-bus: Populate simple MFD child devices
drivers: bus: simple-pm-bus: Use clocks
dt-bindings: bus: Add Freescale i.MX8qxp pixel link MSI bus binding
.../bus/fsl,imx8qxp-pixel-link-msi-bus.yaml | 108 ++++++++++++++++++
drivers/bus/simple-pm-bus.c | 61 +++++++++-
2 files changed, 168 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/bus/fsl,imx8qxp-pixel-link-msi-bus.yaml
--
2.25.1
next reply other threads:[~2022-08-04 6:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 6:11 Liu Ying [this message]
2022-08-04 6:11 ` [PATCH v3 1/3] drivers: bus: simple-pm-bus: Populate simple MFD child devices Liu Ying
2022-08-04 12:18 ` Rob Herring
2022-08-04 18:26 ` Saravana Kannan
2022-08-05 10:06 ` Liu Ying
2022-08-05 17:55 ` Saravana Kannan
2022-08-06 16:23 ` Liu Ying
2022-08-04 6:11 ` [PATCH v3 2/3] drivers: bus: simple-pm-bus: Use clocks Liu Ying
2022-08-11 12:34 ` Geert Uytterhoeven
2022-08-12 8:13 ` Liu Ying
2022-08-12 8:58 ` Geert Uytterhoeven
2022-08-12 9:42 ` Liu Ying
2022-08-12 9:49 ` Geert Uytterhoeven
2022-08-12 12:25 ` Liu Ying
2022-08-04 6:11 ` [PATCH v3 3/3] dt-bindings: bus: Add Freescale i.MX8qxp pixel link MSI bus binding Liu Ying
2022-08-04 11:17 ` Krzysztof Kozlowski
2022-08-05 10:18 ` Liu Ying
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=20220804061133.4110734-1-victor.liu@nxp.com \
--to=victor.liu@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=saravanak@google.com \
--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;
as well as URLs for NNTP newsgroup(s).