From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: devicetree@vger.kernel.org,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
soc@kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: imx6qdl: Add Variscite VAR-SOM-MX6 SoM support
Date: Wed, 19 Jul 2023 21:24:19 +0200 [thread overview]
Message-ID: <792641d2-3a27-4f87-fa90-2490a302685e@linaro.org> (raw)
In-Reply-To: <CADvTj4pgA_XjYZyU+D+J2QdC4NPFTxPSBCvrpK8WNjFkzkz-KQ@mail.gmail.com>
On 19/07/2023 20:57, James Hilliard wrote:
> On Wed, Jul 19, 2023 at 11:16 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>>
>>> +
>>> +/ {
>>> + model = "Variscite i.MX6 QUAD/DUAL VAR-SOM-MX6";
>>> + compatible = "fsl,imx6q";
>>
>> That's not correct compatible. It's not Imx6 soc. It's a som.
>
> I'm confused, AFAIU the VAR-SOM-MX6 uses an imx6q SoC.
True, I should say - that's incomplete compatible. You claim here this
is imx6q. Not that it uses imx6q... Add your own compatible and document
all of them.
>
>>
>>> +...
>>> +
>>> + sound: sound {
>>> + compatible = "simple-audio-card";
>>> + simple-audio-card,name = "var-som-audio";
>>> + simple-audio-card,format = "i2s";
>>> + simple-audio-card,bitclock-master = <&sound_codec>;
>>> + simple-audio-card,frame-master = <&sound_codec>;
>>> + simple-audio-card,widgets = "Headphone", "Headphone Jack",
>>> + "Line", "Line In", "Microphone", "Mic Jack";
>>> + simple-audio-card,routing = "Headphone Jack", "HPLOUT",
>>> + "Headphone Jack", "HPROUT",
>>> + "LINE1L", "Line In",
>>> + "LINE1R", "Line In";
>>> +
>>> + sound_cpu: simple-audio-card,cpu {
>>> + sound-dai = <&ssi2>;
>>> + };
>>> +
>>> + sound_codec: simple-audio-card,codec {
>>> + sound-dai = <&tlv320aic3106>;
>>> + clocks = <&clks IMX6QDL_CLK_CKO>;
>>> + };
>>> + };
>>> +
>>> + wlan_bt_rfkill {
>>
>> No underscores in node names.
>>
>> Just "rfkill"
>>
>>
>>> + compatible = "rfkill-gpio";
>>> + name = "wlan_bt_rfkill";
>>> + type = <2>; /* bluetooth */
>>> + gpios = <&gpio6 18 GPIO_ACTIVE_HIGH>;
>>> + };
>>> +};
>>> +
>>
>> ...
>>
>>> + tlv320aic3106: codec@1b {
>>> + compatible = "ti,tlv320aic3106";
>>> + reg = <0x1b>;
>>> + #sound-dai-cells = <0>;
>>> + DRVDD-supply = <®_3p3v>;
>>> + AVDD-supply = <®_3p3v>;
>>> + IOVDD-supply = <®_3p3v>;
>>> + DVDD-supply = <®_3p3v>;
>>> + ai3x-ocmv = <0>;
>>> + reset-gpios = <&gpio4 5 GPIO_ACTIVE_LOW>;
>>> + ai3x-gpio-func = <
>>> + 0 /* AIC3X_GPIO1_FUNC_DISABLED */
>>> + 5 /* AIC3X_GPIO2_FUNC_DIGITAL_MIC_INPUT */
>>> + >;
>>> + };
>>> +};
>>> +
>>> +&iomuxc {
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&pinctrl_hog>;
>>> +
>>> + imx6qdl-var-som-mx6 {
>>> + pinctrl_hog: hoggrp {
>>> + fsl,pins = <
>>> + /* CTW6120 IRQ */
>>> + MX6QDL_PAD_EIM_DA7__GPIO3_IO07 0x80000000
>>> + /* SDMMC2 CD/WP */
>>> + MX6QDL_PAD_KEY_COL4__GPIO4_IO14 0x80000000
>>> + MX6QDL_PAD_KEY_ROW4__GPIO4_IO15 0x80000000
>>> + >;
>>> + };
>>> +
>>> + pinctrl_audmux: audmux {
>>
>> It does not look like you tested the DTS against bindings. Please run
>> `make dtbs_check` (see
>> Documentation/devicetree/bindings/writing-schema.rst or
>> https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/
>> for instructions).
>>
>> AFAIR, all of them end with grp
>
> Ah, that's def throwing a bunch of warnings, although quite a few look
> to be existing
> issues in dependent dtsi files. I'll clean up what I can there.
>
>>
>>
>> ...
>>
>>> +
>>> +&usdhc3 {
>>> + pinctrl-names = "default", "state_100mhz", "state_200mhz";
>>> + pinctrl-0 = <&pinctrl_usdhc3>;
>>> + pinctrl-1 = <&pinctrl_usdhc3_100mhz>;
>>> + pinctrl-2 = <&pinctrl_usdhc3_200mhz>;
>>> + bus-width = <4>;
>>> + vmmc-supply = <®_wl18xx_vmmc>;
>>> + non-removable;
>>> + wakeup-source;
>>> + keep-power-in-suspend;
>>> + cap-power-off-card;
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> + status = "okay";
>>> +
>>> + wlcore: wlcore@0 {
>>
>> Generic node names. Is this wifi?
>
> I think it also supports bluetooth technically, although that might be
> under a different node.
>
Bluetooths are usually under serial, so this is just wifi.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-19 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 16:00 [PATCH 1/2] ARM: dts: imx6qdl: Add Variscite VAR-SOM-MX6 SoM support James Hilliard
2023-07-19 16:00 ` [PATCH 2/2] ARM: dts: imx6q: Add Variscite MX6 Custom board support James Hilliard
2023-07-19 17:18 ` Krzysztof Kozlowski
2023-07-19 19:11 ` James Hilliard
2023-07-19 19:22 ` Krzysztof Kozlowski
2023-07-19 19:32 ` Fabio Estevam
2023-07-19 20:04 ` James Hilliard
2023-07-19 22:43 ` James Hilliard
2023-07-20 1:29 ` Fabio Estevam
2023-07-19 17:16 ` [PATCH 1/2] ARM: dts: imx6qdl: Add Variscite VAR-SOM-MX6 SoM support Krzysztof Kozlowski
2023-07-19 18:57 ` James Hilliard
2023-07-19 19:24 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-11 15:36 [PATCH 0/2] ARM: Add support for VAR-SOM-MX6 Gregory CLEMENT
2022-03-11 15:36 ` [PATCH 1/2] ARM: dts: imx6qdl: Add Variscite VAR-SOM-MX6 SoM support Gregory CLEMENT
2022-03-11 15:59 ` Krzysztof Kozlowski
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=792641d2-3a27-4f87-fa90-2490a302685e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=james.hilliard1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=soc@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).