From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Marek Vasut <marex@denx.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Fabio Estevam <festevam@denx.de>,
NXP Linux Team <linux-imx@nxp.com>,
kernel <kernel@dh-electronics.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 2/2] ARM: dts: imx6ull-dhcor: Add Marantec maveo box
Date: Wed, 5 Apr 2023 18:24:01 +0000 [thread overview]
Message-ID: <e7aa3b3220e148ee96f5a1c361721845@dh-electronics.com> (raw)
In-Reply-To: <05fa147c-116b-59b4-d14b-760bbefd7602@denx.de>
From: Marek Vasut [mailto:marex@denx.de]
Sent: Wednesday, April 5, 2023 6:25 PM
> On 4/5/23 18:02, Christoph Niedermaier wrote:
>
> [...]
>
>> +/ {
>> + model = "DH electronics i.MX6ULL DHCOR on maveo box";
>> + compatible = "dh,imx6ull-dhcor-maveo-box", "dh,imx6ull-dhcor-som",
>> + "fsl,imx6ull";
>> +
>> + aliases {
>> + /delete-property/ mmc0; /* Avoid double definitions */
>> + /delete-property/ mmc1;
>> + mmc2 = &usdhc2; /* eMMC should be mmc2 */
>
> Why not mmc0 ?
>
> Use root=PARTUUID= when booting to avoid any dependency on
> root=/dev/mmcblk2pN enumeration.
This is due to software interchangeability with the DHCOM
i.MX6ULL, where the eMMC is always mmc2.
>
>> + spi0 = &ecspi4;
>> + spi3 = &ecspi1;
>> + };
>
> [...]
>
>> +&iomuxc {
>> + pinctrl-0 = <&pinctrl_hog_maveo_box>;
>> + pinctrl-names = "default";
>> +
>> + pinctrl_hog_maveo_box: hog-maveo-box-grp {
>> + fsl,pins = <
>> + MX6UL_PAD_GPIO1_IO05__GPIO1_IO05 0x400120b0 /* BUTTON_USER */
>> + MX6UL_PAD_GPIO1_IO08__GPIO1_IO08 0x400120b0 /* BUTTON_RESET */
>> + MX6UL_PAD_CSI_PIXCLK__GPIO4_IO18 0x400120b0 /* LED_G */
>> + MX6UL_PAD_CSI_DATA02__GPIO4_IO23 0x400120b0 /* LED_B */
>
> Should the "SION(1 << 30): Software Input On Field." bit really be set
> on GPIOs which are OUTPUT (like LEDs) ?
I think for INPUT it doesn't matter, but for OUTPUT I then have a feedback.
Regards
Christoph
next prev parent reply other threads:[~2023-04-05 18:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 16:02 [PATCH 1/2] dt-bindings: arm: fsl: Add Marantec maveo box as a DHCOR i.MX6ULL SoM based board Christoph Niedermaier
2023-04-05 16:02 ` [PATCH 2/2] ARM: dts: imx6ull-dhcor: Add Marantec maveo box Christoph Niedermaier
2023-04-05 16:25 ` Marek Vasut
2023-04-05 18:24 ` Christoph Niedermaier [this message]
2023-04-05 18:46 ` Marek Vasut
2023-04-06 8:37 ` Christoph Niedermaier
2023-04-06 14:10 ` Marek Vasut
2023-04-06 15:44 ` Christoph Niedermaier
2023-04-06 16:04 ` Marek Vasut
2023-04-06 16:36 ` Krzysztof Kozlowski
2023-04-06 17:32 ` Marek Vasut
2023-04-06 18:03 ` Krzysztof Kozlowski
2023-04-05 16:26 ` [PATCH 1/2] dt-bindings: arm: fsl: Add Marantec maveo box as a DHCOR i.MX6ULL SoM based board Marek Vasut
2023-04-05 18:13 ` Christoph Niedermaier
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=e7aa3b3220e148ee96f5a1c361721845@dh-electronics.com \
--to=cniedermaier@dh-electronics.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=kernel@dh-electronics.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--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).