lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 29 Sep 2021 13:48:45 +0200
From:   Michal Simek <michal.simek@...inx.com>
To:     Rob Herring <robh@...nel.org>,
        Michal Simek <michal.simek@...inx.com>
CC:     <monstr@...str.eu>, <devicetree@...r.kernel.org>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        <linux-arm-kernel@...ts.infradead.org>,
        "Michael Walle" <michael@...le.cc>,
        Rob Herring <robh+dt@...nel.org>,
        "Krzysztof Kozlowski" <krzk@...nel.org>,
        Viresh Kumar <viresh.kumar@...aro.org>, <git@...inx.com>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5] arm64: zynqmp: Add support for Xilinx Kria SOM board



On 9/27/21 8:35 PM, Rob Herring wrote:
> On Wed, 22 Sep 2021 09:07:32 +0200, Michal Simek wrote:
>> There are couple of revisions of SOMs (k26) and associated carrier cards
>> (kv260).
>> SOM itself has two major versions:
>> sm-k26 - SOM with EMMC
>> smk-k26 - SOM without EMMC used on starter kit with preprogrammed firmware
>> in QSPI.
>>
>> SOMs are describing only devices available on the SOM or connections which
>> are described in specification (for example UART, fwuen).
>>
>> When SOM boots out of QSPI it uses limited number of peripherals defined by
>> the specification and present in sm(k)-k26 dtses.
>> Then a carrier card (CC) detection is happening and DT overlay is applied
>> to brings new functionality. That's why DT overlays are used. The name is
>> composed together with SOM name and CC name that's why DT overlays with
>> these names are generated to make sure they can be used together.
>>
>> Signed-off-by: Michal Simek <michal.simek@...inx.com>
>> ---
>>
>> Changes in v5:
>> - Extend commit message.
>>
>> Changes in v4:
>> - Remove ina260 and usb5744 nodes
>> - Remove compatible string from overlays
>>
>> Changes in v3:
>> - Fix led node name
>> - Fix compatible string for xlnx,zynqmp-sk-kv260-revA/Y/Z
>> - Fix headers alignment
>> - Move USB3 PHY properties from DWC3 node to USB node - reported by Manish
>>   Narani
>> - Change dtb names generated with dtbo
>> - Fix emmc comment style
>>
>> Changes in v2:
>> - Use sugar syntax - reported by Geert
>> - Update copyright years
>> - Fix SD3.0 comment alignment
>> - Remove one newline from Makefile
>>
>> https://www.xilinx.com/products/som/kria.html
>> Based on
>> https://lore.kernel.org/r/cover.1628244703.git.michal.simek@xilinx.com
>>
>> ---
>>  .../devicetree/bindings/arm/xilinx.yaml       |  16 +
>>  arch/arm64/boot/dts/xilinx/Makefile           |  13 +
>>  .../boot/dts/xilinx/zynqmp-sck-kv-g-revA.dts  | 315 ++++++++++++++++++
>>  .../boot/dts/xilinx/zynqmp-sck-kv-g-revB.dts  | 298 +++++++++++++++++
>>  .../boot/dts/xilinx/zynqmp-sm-k26-revA.dts    | 289 ++++++++++++++++
>>  .../boot/dts/xilinx/zynqmp-smk-k26-revA.dts   |  21 ++
>>  6 files changed, 952 insertions(+)
>>  create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revA.dts
>>  create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revB.dts
>>  create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-sm-k26-revA.dts
>>  create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-smk-k26-revA.dts
>>
> 
> Reviewed-by: Rob Herring <robh@...nel.org>
> 

Applied.
M

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ