From: "Stefan Riedmüller" <s.riedmueller@phytec.de>
To: linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>
Cc: devicetree@vger.kernel.org,
Andrew Smirnov <andrew.smirnov@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-imx@nxp.com,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: fsl: Add PHYTEC i.MX6 UL/ULL devicetree bindings
Date: Mon, 9 Dec 2019 14:33:02 +0100 [thread overview]
Message-ID: <f2084e4d-8e62-80fc-e578-d3d4be50af2f@phytec.de> (raw)
In-Reply-To: <1568980346-385840-1-git-send-email-s.riedmueller@phytec.de>
Hi,
I just wanted to send a gentle ping for these two patches.
Regards,
Stefan
On 20.09.19 13:52, Stefan Riedmueller wrote:
> Add devicetree bindings for i.MX6 UL/ULL based phyCORE-i.MX6 UL/ULL and
> phyBOARD-Segin.
>
> Signed-off-by: Stefan Riedmueller <s.riedmueller@phytec.de>
> ---
> Changes in v2:
> - Use seperate description for each board instead of squashing them into
> the standard board.
> ---
> Documentation/devicetree/bindings/arm/fsl.yaml | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml
> index 1b4b4e6573b5..c926ff6eac67 100644
> --- a/Documentation/devicetree/bindings/arm/fsl.yaml
> +++ b/Documentation/devicetree/bindings/arm/fsl.yaml
> @@ -164,6 +164,15 @@ properties:
> - kontron,imx6ul-n6310-som # Kontron N6310 SOM
> - const: fsl,imx6ul
>
> + - description: i.MX6UL PHYTEC phyBOARD-Segin
> + items:
> + - enum:
> + - phytec,imx6ul-pbacd10-emmc
> + - phytec,imx6ul-pbacd10-nand
> + - const: phytec,imx6ul-pbacd10 # PHYTEC phyBOARD-Segin with i.MX6 UL
> + - const: phytec,imx6ul-pcl063 # PHYTEC phyCORE-i.MX 6UL
> + - const: fsl,imx6ul
> +
> - description: Kontron N6310 S Board
> items:
> - const: kontron,imx6ul-n6310-s
> @@ -183,6 +192,15 @@ properties:
> - fsl,imx6ull-14x14-evk # i.MX6 UltraLiteLite 14x14 EVK Board
> - const: fsl,imx6ull
>
> + - description: i.MX6ULL PHYTEC phyBOARD-Segin
> + items:
> + - enum:
> + - phytec,imx6ull-pbacd10-emmc
> + - phytec,imx6ull-pbacd10-nand
> + - const: phytec,imx6ull-pbacd10 # PHYTEC phyBOARD-Segin with i.MX6 ULL
> + - const: phytec,imx6ull-pcl063 # PHYTEC phyCORE-i.MX 6ULL
> + - const: fsl,imx6ull
> +
> - description: i.MX6ULZ based Boards
> items:
> - enum:
>
prev parent reply other threads:[~2019-12-09 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 11:52 [PATCH v2 1/2] dt-bindings: arm: fsl: Add PHYTEC i.MX6 UL/ULL devicetree bindings Stefan Riedmueller
2019-09-20 11:52 ` [PATCH v2 2/2] dt-bindings: arm: fsl: Add PHYTEC i.MX6 " Stefan Riedmueller
2019-10-01 22:18 ` Rob Herring
2019-10-01 22:18 ` [PATCH v2 1/2] dt-bindings: arm: fsl: Add PHYTEC i.MX6 UL/ULL " Rob Herring
2019-12-09 13:33 ` Stefan Riedmüller [this message]
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=f2084e4d-8e62-80fc-e578-d3d4be50af2f@phytec.de \
--to=s.riedmueller@phytec.de \
--cc=andrew.smirnov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mark.rutland@arm.com \
--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: 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