From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: dillon.minfei@gmail.com, robh+dt@kernel.org, shawnguo@kernel.org,
krzk@kernel.org, linux@rempel-privat.de, s.riedmueller@phytec.de,
matthias.schiffer@ew.tq-group.com, leoyang.li@nxp.com,
arnd@arndb.de, olof@lixom.net, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com,
prabhakar.csengg@gmail.com, mchehab@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
linux-media@vger.kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: arm: imx: Add i.mx6q DaSheng COM-9XX SBC board dts support
Date: Wed, 14 Apr 2021 15:00:00 +0200 [thread overview]
Message-ID: <6d8a5d4c-b741-dc7a-7cfb-eb66a642cb6f@canonical.com> (raw)
In-Reply-To: <1618383117-17179-2-git-send-email-dillon.minfei@gmail.com>
On 14/04/2021 08:51, dillon.minfei@gmail.com wrote:
> From: dillon min <dillon.minfei@gmail.com>
>
> The DaSheng Com-9xx is and ARM based signle board computer (SBC)
> featuring:
> - i.MX6Q
> - 2GiB LPDDR3 DRAM
> - 8GiB eMMC 5.0 FLASH
> - 4MiB SPI Flash
> - USB 2.0 Host/Device
> - Multiple multi-protocol RS232/RS485 Serial ports
> - microSD socket
> - 5V DC power input
> - HDMI1.4a,1080p@60
> - RGMIIx1 Gigabit Ethernet
> - CSI0x1, connect with ov2659
>
> Signed-off-by: dillon min <dillon.minfei@gmail.com>
> Cc: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> ---
> v2: no changes
>
> Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml
> index 297c87f45db8..24bdfbd4853f 100644
> --- a/Documentation/devicetree/bindings/arm/fsl.yaml
> +++ b/Documentation/devicetree/bindings/arm/fsl.yaml
> @@ -206,6 +206,7 @@ properties:
> - fsl,imx6q-sabreauto
> - fsl,imx6q-sabrelite
> - fsl,imx6q-sabresd
> + - ds,imx6q-sbc # Da Sheng COM-9XX Modules
You break here the alphabetical order. Should be after dmo,imx6q-edmqmx6.
Best regards,
Krzysztof
next prev parent reply other threads:[~2021-04-14 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 6:51 [PATCH v2 0/4] arm: imx: Add i.mx6q DaSheng COM-9XX SBC board support dillon.minfei
2021-04-14 6:51 ` [PATCH v2 1/4] dt-bindings: arm: imx: Add i.mx6q DaSheng COM-9XX SBC board dts support dillon.minfei
2021-04-14 13:00 ` Krzysztof Kozlowski [this message]
2021-04-15 3:22 ` dillon min
2021-04-14 6:51 ` [PATCH v2 2/4] arm: dts: imx: Add i.mx6q DaSheng COM-9XX SBC board support dillon.minfei
2021-04-14 6:51 ` [PATCH v2 3/4] media: i2c: ov2659: Add clk_prepare_enable(), clk_disable_unprepare() to handle xvclk dillon.minfei
2021-04-14 6:51 ` [PATCH v2 4/4] dt-bindings: add dasheng vendor prefix dillon.minfei
2021-04-14 13:01 ` Krzysztof Kozlowski
2021-04-15 3:24 ` dillon min
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=6d8a5d4c-b741-dc7a-7cfb-eb66a642cb6f@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=dillon.minfei@gmail.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.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=linux-media@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=mchehab@kernel.org \
--cc=olof@lixom.net \
--cc=prabhakar.csengg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s.riedmueller@phytec.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: 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).