From: Schrempf Frieder <frieder.schrempf@kontron.de>
To: "krzk@kernel.org" <krzk@kernel.org>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
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>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 01/10] ARM: dts: imx6ul-kontron-n6310: Move common SoM nodes to a separate file
Date: Mon, 21 Oct 2019 12:44:19 +0000 [thread overview]
Message-ID: <89a91b79-63f9-2a2d-30aa-d4447f1cbc96@kontron.de> (raw)
In-Reply-To: <20191021102809.GA1934@pi3>
On 21.10.19 12:28, krzk@kernel.org wrote:
> On Wed, Oct 16, 2019 at 03:07:19PM +0000, Schrempf Frieder wrote:
>> From: Frieder Schrempf <frieder.schrempf@kontron.de>
>>
>> The Kontron N6311 and N6411 SoMs are very similar to N6310. In
>> preparation to add support for them, we move the common nodes to a
>> separate file imx6ul-kontron-n6x1x-som-common.dtsi.
>>
>> Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de>
>> ---
>> .../boot/dts/imx6ul-kontron-n6310-som.dtsi | 95 +-------------
>> .../dts/imx6ul-kontron-n6x1x-som-common.dtsi | 123 ++++++++++++++++++
>> 2 files changed, 124 insertions(+), 94 deletions(-)
>> create mode 100644 arch/arm/boot/dts/imx6ul-kontron-n6x1x-som-common.dtsi
>>
>> diff --git a/arch/arm/boot/dts/imx6ul-kontron-n6310-som.dtsi b/arch/arm/boot/dts/imx6ul-kontron-n6310-som.dtsi
>> index a896b2348dd2..47d3ce5d255f 100644
>> --- a/arch/arm/boot/dts/imx6ul-kontron-n6310-som.dtsi
>> +++ b/arch/arm/boot/dts/imx6ul-kontron-n6310-som.dtsi
>> @@ -6,7 +6,7 @@
>> */
>>
>> #include "imx6ul.dtsi"
>> -#include <dt-bindings/gpio/gpio.h>
>> +#include "imx6ul-kontron-n6x1x-som-common.dtsi"
>>
>> / {
>> model = "Kontron N6310 SOM";
>> @@ -18,49 +18,7 @@
>> };
>> };
>>
>> -&ecspi2 {
>> - cs-gpios = <&gpio4 22 GPIO_ACTIVE_HIGH>;
>> - pinctrl-names = "default";
>> - pinctrl-0 = <&pinctrl_ecspi2>;
>> - status = "okay";
>> -
>> - spi-flash@0 {
>> - compatible = "mxicy,mx25v8035f", "jedec,spi-nor";
>> - spi-max-frequency = <50000000>;
>> - reg = <0>;
>> - };
>> -};
>> -
>> -&fec1 {
>> - pinctrl-names = "default";
>> - pinctrl-0 = <&pinctrl_enet1 &pinctrl_enet1_mdio>;
>> - phy-mode = "rmii";
>> - phy-handle = <ðphy1>;
>> - status = "okay";
>> -
>> - mdio {
>> - #address-cells = <1>;
>> - #size-cells = <0>;
>> -
>> - ethphy1: ethernet-phy@1 {
>> - reg = <1>;
>> - micrel,led-mode = <0>;
>> - clocks = <&clks IMX6UL_CLK_ENET_REF>;
>> - clock-names = "rmii-ref";
>> - };
>> - };
>> -};
>> -
>> -&fec2 {
>> - phy-mode = "rmii";
>> - status = "disabled";
>> -};
>> -
>> &qspi {
>> - pinctrl-names = "default";
>> - pinctrl-0 = <&pinctrl_qspi>;
>> - status = "okay";
>> -
>> spi-flash@0 {
>
> You left qspi and flash partitions here, while adding it later. It is
> not pure move then and some duplicated stuff remains.
Indeed, the spi-flash node is duplicated, as I forgot to remove it from
the common include file. I will change that.
next prev parent reply other threads:[~2019-10-21 12:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 15:06 [PATCH 00/10] Add support for more Kontron i.MX6UL/ULL SoMs and boards Schrempf Frieder
2019-10-16 15:07 ` [PATCH 01/10] ARM: dts: imx6ul-kontron-n6310: Move common SoM nodes to a separate file Schrempf Frieder
2019-10-21 10:28 ` krzk
2019-10-21 12:44 ` Schrempf Frieder [this message]
2019-10-16 15:07 ` [PATCH 02/10] ARM: dts: Add support for two more Kontron SoMs N6311 and N6411 Schrempf Frieder
2019-10-21 10:29 ` krzk
2019-10-16 15:07 ` [PATCH 03/10] ARM: dts: imx6ul-kontron-n6310-s: Move common nodes to a separate file Schrempf Frieder
2019-10-21 10:38 ` krzk
2019-10-21 12:44 ` Schrempf Frieder
2019-10-16 15:07 ` [PATCH 04/10] ARM: dts: Add support for two more Kontron evalkit boards 'N6311 S' and 'N6411 S' Schrempf Frieder
2019-10-21 10:41 ` krzk
2019-10-16 15:07 ` [PATCH 05/10] ARM: dts: imx6ul-kontron-n6x1x: Add 'chosen' node with 'stdout-path' Schrempf Frieder
2019-10-21 10:52 ` krzk
2019-10-16 15:07 ` [PATCH 06/10] ARM: dts: imx6ul-kontron-n6x1x-s: Specify bus-width for SD card and eMMC Schrempf Frieder
2019-10-16 15:07 ` [PATCH 07/10] ARM: dts: imx6ul-kontron-n6x1x-s: Add vbus-supply and overcurrent polarity to usb nodes Schrempf Frieder
2019-10-16 15:07 ` [PATCH 08/10] ARM: dts: imx6ul-kontron-n6x1x-s: Remove an obsolete comment and fix indentation Schrempf Frieder
2019-10-16 15:07 ` [PATCH 09/10] dt-bindings: arm: fsl: Add more Kontron i.MX6UL/ULL compatibles Schrempf Frieder
2019-10-21 10:44 ` krzk
2019-10-29 1:28 ` Rob Herring
2019-10-16 15:08 ` [PATCH 10/10] MAINTAINERS: Add an entry for Kontron Electronics ARM board support Schrempf Frieder
2019-10-17 8:14 ` [PATCH 00/10] Add support for more Kontron i.MX6UL/ULL SoMs and boards Marco Felsch
2019-10-17 8:24 ` Schrempf Frieder
2019-10-21 11:43 ` Marco Felsch
2019-10-21 12:24 ` Schrempf Frieder
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=89a91b79-63f9-2a2d-30aa-d4447f1cbc96@kontron.de \
--to=frieder.schrempf@kontron.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®