From: Jacky Bai <ping.bai@nxp.com> To: lee@kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org, s.hauer@pengutronix.de, dmitry.torokhov@gmail.com, a.zummo@towertech.it, alexandre.belloni@bootlin.com Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-input@vger.kernel.org, linux-rtc@vger.kernel.org, kernel@pengutronix.de, linux-imx@nxp.com, festevam@gmail.com Subject: [PATCH v4 4/4] arm64: dts: imx93: Add the bbnsm dts node Date: Sun, 29 Jan 2023 15:08:23 +0800 [thread overview] Message-ID: <20230129070823.1945489-5-ping.bai@nxp.com> (raw) In-Reply-To: <20230129070823.1945489-1-ping.bai@nxp.com> Add the bbnsm node for RTC & ON/OFF button support Signed-off-by: Jacky Bai <ping.bai@nxp.com> --- - v2 changes: - update the regmap property to align with binding doc - v3 changes: - remove 'nxp,bbnsm-regmap' property to align with binding doc - v4 changes: - update the compatible string to align with binding file --- arch/arm64/boot/dts/freescale/imx93.dtsi | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/arch/arm64/boot/dts/freescale/imx93.dtsi b/arch/arm64/boot/dts/freescale/imx93.dtsi index 5d79663b3b84..36be18165d4b 100644 --- a/arch/arm64/boot/dts/freescale/imx93.dtsi +++ b/arch/arm64/boot/dts/freescale/imx93.dtsi @@ -229,6 +229,22 @@ iomuxc: pinctrl@443c0000 { status = "okay"; }; + bbnsm: bbnsm@44440000 { + compatible = "nxp,imx93-bbnsm", "syscon", "simple-mfd"; + reg = <0x44440000 0x10000>; + + bbnsm_rtc: rtc { + compatible = "nxp,imx93-bbnsm-rtc"; + interrupts = <GIC_SPI 73 IRQ_TYPE_LEVEL_HIGH>; + }; + + bbnsm_pwrkey: pwrkey { + compatible = "nxp,imx93-bbnsm-pwrkey"; + interrupts = <GIC_SPI 73 IRQ_TYPE_LEVEL_HIGH>; + linux,code = <KEY_POWER>; + }; + }; + clk: clock-controller@44450000 { compatible = "fsl,imx93-ccm"; reg = <0x44450000 0x10000>; -- 2.37.1
WARNING: multiple messages have this Message-ID (diff)
From: Jacky Bai <ping.bai@nxp.com> To: lee@kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org, s.hauer@pengutronix.de, dmitry.torokhov@gmail.com, a.zummo@towertech.it, alexandre.belloni@bootlin.com Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-input@vger.kernel.org, linux-rtc@vger.kernel.org, kernel@pengutronix.de, linux-imx@nxp.com, festevam@gmail.com Subject: [PATCH v4 4/4] arm64: dts: imx93: Add the bbnsm dts node Date: Sun, 29 Jan 2023 15:08:23 +0800 [thread overview] Message-ID: <20230129070823.1945489-5-ping.bai@nxp.com> (raw) In-Reply-To: <20230129070823.1945489-1-ping.bai@nxp.com> Add the bbnsm node for RTC & ON/OFF button support Signed-off-by: Jacky Bai <ping.bai@nxp.com> --- - v2 changes: - update the regmap property to align with binding doc - v3 changes: - remove 'nxp,bbnsm-regmap' property to align with binding doc - v4 changes: - update the compatible string to align with binding file --- arch/arm64/boot/dts/freescale/imx93.dtsi | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/arch/arm64/boot/dts/freescale/imx93.dtsi b/arch/arm64/boot/dts/freescale/imx93.dtsi index 5d79663b3b84..36be18165d4b 100644 --- a/arch/arm64/boot/dts/freescale/imx93.dtsi +++ b/arch/arm64/boot/dts/freescale/imx93.dtsi @@ -229,6 +229,22 @@ iomuxc: pinctrl@443c0000 { status = "okay"; }; + bbnsm: bbnsm@44440000 { + compatible = "nxp,imx93-bbnsm", "syscon", "simple-mfd"; + reg = <0x44440000 0x10000>; + + bbnsm_rtc: rtc { + compatible = "nxp,imx93-bbnsm-rtc"; + interrupts = <GIC_SPI 73 IRQ_TYPE_LEVEL_HIGH>; + }; + + bbnsm_pwrkey: pwrkey { + compatible = "nxp,imx93-bbnsm-pwrkey"; + interrupts = <GIC_SPI 73 IRQ_TYPE_LEVEL_HIGH>; + linux,code = <KEY_POWER>; + }; + }; + clk: clock-controller@44450000 { compatible = "fsl,imx93-ccm"; reg = <0x44450000 0x10000>; -- 2.37.1 _______________________________________________ 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:[~2023-01-29 7:07 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-29 7:08 [PATCH v4 0/4] Add nxp bbnsm module support Jacky Bai 2023-01-29 7:08 ` Jacky Bai 2023-01-29 7:08 ` [PATCH v4 1/4] dt-bindings: mfd: Add nxp bbnsm Jacky Bai 2023-01-29 7:08 ` Jacky Bai 2023-01-30 22:09 ` Rob Herring 2023-01-30 22:09 ` Rob Herring 2023-01-31 9:15 ` Lee Jones 2023-01-31 9:15 ` Lee Jones 2023-01-29 7:08 ` [PATCH v4 2/4] input: bbnsm_pwrkey: Add bbnsm power key support Jacky Bai 2023-01-29 7:08 ` Jacky Bai 2023-02-03 15:03 ` Mattijs Korpershoek 2023-02-03 15:03 ` Mattijs Korpershoek 2023-02-03 20:11 ` Dmitry Torokhov 2023-02-03 20:11 ` Dmitry Torokhov 2023-02-10 7:11 ` Jacky Bai 2023-02-10 7:11 ` Jacky Bai 2023-01-29 7:08 ` [PATCH v4 3/4] rtc: bbnsm: Add the bbnsm rtc support Jacky Bai 2023-01-29 7:08 ` Jacky Bai 2023-01-29 7:08 ` Jacky Bai [this message] 2023-01-29 7:08 ` [PATCH v4 4/4] arm64: dts: imx93: Add the bbnsm dts node Jacky Bai
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=20230129070823.1945489-5-ping.bai@nxp.com \ --to=ping.bai@nxp.com \ --cc=a.zummo@towertech.it \ --cc=alexandre.belloni@bootlin.com \ --cc=devicetree@vger.kernel.org \ --cc=dmitry.torokhov@gmail.com \ --cc=festevam@gmail.com \ --cc=kernel@pengutronix.de \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=lee@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-imx@nxp.com \ --cc=linux-input@vger.kernel.org \ --cc=linux-rtc@vger.kernel.org \ --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: linkBe 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.