From: Krzysztof Kozlowski <krzk@kernel.org>
To: Adrien Grassein <adrien.grassein@gmail.com>
Cc: robh+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
catalin.marinas@arm.com, will@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/9] arm64: dts: imx8mm-nitrogen-r2: add wifi/bt chip
Date: Sat, 20 Feb 2021 20:22:48 +0100 [thread overview]
Message-ID: <20210220192248.2x4zk4zvorxbjsen@kozik-lap> (raw)
In-Reply-To: <20210219143028.207975-2-adrien.grassein@gmail.com>
On Fri, Feb 19, 2021 at 03:30:20PM +0100, Adrien Grassein wrote:
> Add usdhc3 description which corresponds to the wifi/bt chip
>
> Signed-off-by: Adrien Grassein <adrien.grassein@gmail.com>
> ---
> .../boot/dts/freescale/imx8mm-nitrogen-r2.dts | 38 +++++++++++++++++++
> 1 file changed, 38 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mm-nitrogen-r2.dts b/arch/arm64/boot/dts/freescale/imx8mm-nitrogen-r2.dts
> index c0c384d76147..4a3dabeb8c85 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mm-nitrogen-r2.dts
> +++ b/arch/arm64/boot/dts/freescale/imx8mm-nitrogen-r2.dts
> @@ -9,6 +9,24 @@
> / {
> model = "Boundary Devices i.MX8MMini Nitrogen8MM Rev2";
> compatible = "boundary,imx8mm-nitrogen8mm", "fsl,imx8mm";
> +
> + reg_vref_1v8: regulator-vref-1v8 {
> + compatible = "regulator-fixed";
> + regulator-name = "vref-1v8";
> + regulator-min-microvolt = <1800000>;
> + regulator-max-microvolt = <1800000>;
> + };
> +
> + reg_wlan_vmmc: regulator-wlan-vmmc {
> + compatible = "regulator-fixed";
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_reg_wlan_vmmc>;
> + regulator-name = "reg_wlan_vmmc";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + gpio = <&gpio3 20 GPIO_ACTIVE_HIGH>;
> + enable-active-high;
> + };
> };
>
> &A53_0 {
> @@ -206,6 +224,20 @@ &usdhc2 {
> status = "okay";
> };
>
> +/* wlan */
> +&usdhc3 {
> + bus-width = <4>;
> + sdhci-caps-mask = <0x2 0x0>;
> + non-removable;
> + pinctrl-names = "default", "state_100mhz", "state_200mhz";
> + pinctrl-0 = <&pinctrl_usdhc3>;
> + pinctrl-1 = <&pinctrl_usdhc3_100mhz>;
> + pinctrl-2 = <&pinctrl_usdhc3_200mhz>;
> + vmmc-supply = <®_wlan_vmmc>;
> + vqmmc-supply = <®_vref_1v8>;
You sent v3 before I replied on your comments. I don't think there is
any benefit in fixed-regulator which cannot be controlled. Are you sure
vqmmc (the bus clock, host interface, controller core?) does not go from
the PMIC?
Best regards,
Krzysztof
next prev parent reply other threads:[~2021-02-20 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 14:30 [PATCH v3 0/9] Add peripheral support for imx8mm-nitrogen-r2 board Adrien Grassein
2021-02-19 14:30 ` [PATCH v3 1/9] arm64: dts: imx8mm-nitrogen-r2: add wifi/bt chip Adrien Grassein
2021-02-20 19:22 ` Krzysztof Kozlowski [this message]
2021-02-19 14:30 ` [PATCH v3 2/9] arm64: dts: imx8mm-nitrogen-r2: add USB support Adrien Grassein
2021-02-19 14:30 ` [PATCH v3 3/9] arm64: dts: imx8mm-nitrogen-r2: add espi2 support Adrien Grassein
2021-02-19 14:30 ` [PATCH v3 4/9] arm64: dts: imx8mm-nitrogen-r2: add UARTs Adrien Grassein
2021-02-20 19:23 ` Krzysztof Kozlowski
2021-02-19 14:30 ` [PATCH v3 5/9] arm64: dts: imx8mm-nitrogen-r2: rework UART 2 Adrien Grassein
2021-02-20 19:54 ` Krzysztof Kozlowski
2021-02-19 14:30 ` [PATCH v3 6/9] arm64: dts: imx8mm-nitrogen-r2: add PWMs Adrien Grassein
2021-02-19 14:30 ` [PATCH v3 7/9] arm64: dts: imx8mm-nitrogen-r2: add FlexSPI Adrien Grassein
2021-02-19 14:30 ` [PATCH v3 8/9] arm64: dts: imx8mm-nitrogen-r2: add audio Adrien Grassein
2021-02-19 14:30 ` [PATCH v3 9/9] arm64: defconfig: Enable wm8960 audio driver Adrien Grassein
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=20210220192248.2x4zk4zvorxbjsen@kozik-lap \
--to=krzk@kernel.org \
--cc=adrien.grassein@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=will@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).