linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Rob Herring <robh@kernel.org>, Michal Simek <michal.simek@xilinx.com>
Cc: devicetree@vger.kernel.org,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Will Deacon <will.deacon@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/8] arm64: zynqmp: Add support for Xilinx zcu102
Date: Fri, 2 Mar 2018 19:39:22 +0100	[thread overview]
Message-ID: <f935102d-149f-cc67-e811-ab62caf4abd1@monstr.eu> (raw)
In-Reply-To: <20180302164803.nb45aqgqvnzxuyn5@rob-hp-laptop>


[-- Attachment #1.1: Type: text/plain, Size: 2974 bytes --]

On 2.3.2018 17:48, Rob Herring wrote:
> On Fri, Feb 23, 2018 at 03:40:25PM +0100, Michal Simek wrote:
>> This patch is adding revA, revB and rev1.0. There are also other
>> revisions between which should be backward compatible with previous
>> versions. Unfortunately all revs are still in use.
>>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>> ---
>>
>> Changes in v2:
>> - Remove i2c mw u-boot commands
>> - Use i2c-mux instead of i2cswitch
>> - Use clock generator without numbers.
>> - Use dash in node name zcu102 rev1.0
>> - Record compatible string to xilinx.txt
>>
>>  Documentation/devicetree/bindings/arm/xilinx.txt   |   5 +
>>  arch/arm64/boot/dts/xilinx/Makefile                |   3 +
>>  .../arm64/boot/dts/xilinx/zynqmp-zcu102-rev1.0.dts |  36 ++
>>  arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revA.dts  | 550 +++++++++++++++++++++
>>  arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revB.dts  |  42 ++
>>  5 files changed, 636 insertions(+)
>>  create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-zcu102-rev1.0.dts
>>  create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revA.dts
>>  create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revB.dts
> 
> Reviewed-by: Rob Herring <robh@kernel.org> 
> 
> but...
> 
> 
>> diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revB.dts b/arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revB.dts
>> new file mode 100644
>> index 000000000000..ed3cc684931f
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revB.dts
>> @@ -0,0 +1,42 @@
>> +// SPDX-License-Identifier: GPL-2.0+
>> +/*
>> + * dts file for Xilinx ZynqMP ZCU102 RevB
>> + *
>> + * (C) Copyright 2016 - 2018, Xilinx, Inc.
>> + *
>> + * Michal Simek <michal.simek@xilinx.com>
>> + */
>> +
>> +#include "zynqmp-zcu102-revA.dts"
>> +
>> +/ {
>> +	model = "ZynqMP ZCU102 RevB";
>> +	compatible = "xlnx,zynqmp-zcu102-revB", "xlnx,zynqmp-zcu102", "xlnx,zynqmp";
>> +};
>> +
>> +&gem3 {
>> +	phy-handle = <&phyc>;
>> +	phyc: phy@c {
>> +		reg = <0xc>;
>> +		ti,rx-internal-delay = <0x8>;
>> +		ti,tx-internal-delay = <0xa>;
>> +		ti,fifo-depth = <0x1>;
>> +	};
>> +	/* Cleanup from RevA */
>> +	/delete-node/ phy@21;
>> +};
>> +
>> +/* Different qspi 512Mbit version */
> 
> Stray comment

will remove.

> 
>> +
>> +/* Fix collision with u61 */
>> +&i2c0 {
>> +	i2cswitch@75 {
> 
> Missed this name.
> 
> This probably creates a new node rather than going into the existing 
> tree. If this compiles, we should fix it to not allow the same 
> unit-address twice.

hmm interesting I didn't see that before I sent this. There is a warning
but not error.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2018-03-02 18:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-23 14:40 [PATCH v2 0/8] arm64: zynqmp: Add support for existing Xilinx ZynqMP based boards Michal Simek
2018-02-23 14:40 ` [PATCH v2 1/8] dt-bindings: xilinx: Add description for ZynqMP Michal Simek
2018-03-02 16:36   ` Rob Herring
2018-02-23 14:40 ` [PATCH v2 2/8] arm64: zynqmp: Add support for Xilinx zcu100-revC Michal Simek
2018-03-02 16:40   ` Rob Herring
2018-03-02 18:34     ` Michal Simek
2018-02-23 14:40 ` [PATCH v2 3/8] arm64: zynqmp: Add support for Xilinx zcu102 Michal Simek
2018-03-02 16:48   ` Rob Herring
2018-03-02 18:39     ` Michal Simek [this message]
2018-02-23 14:40 ` [PATCH v2 4/8] arm64: zynqmp: Add support for Xilinx zcu104-revA Michal Simek
2018-03-02 18:02   ` Rob Herring
2018-03-02 18:42     ` Michal Simek
2018-02-23 14:40 ` [PATCH v2 5/8] arm64: zynqmp: Add support for Xilinx zcu106-revA Michal Simek
2018-02-23 14:40 ` [PATCH v2 6/8] arm64: zynqmp: Add support for Xilinx zcu111-revA Michal Simek
2018-03-02 18:04   ` Rob Herring
2018-03-02 18:06   ` Rob Herring
2018-02-23 14:40 ` [PATCH v2 7/8] arm64: zynqmp: Add support for Xilinx zc12XX boards Michal Simek
2018-03-02 18:06   ` Rob Herring
2018-02-23 14:40 ` [PATCH v2 8/8] arm64: zynqmp: Add support for Xilinx zc1751 Michal Simek
2018-03-02 18:12   ` Rob Herring

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=f935102d-149f-cc67-e811-ab62caf4abd1@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=robh@kernel.org \
    --cc=will.deacon@arm.com \
    --cc=yamada.masahiro@socionext.com \
    /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).