linux-kernel - Re: [PATCH 0/4] arm64: Initial support for Texas Instrument's J7200 Platform

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <c700e177-1fbe-cba0-8fc8-846caba0734d@ti.com>
Date:   Tue, 28 Jul 2020 22:50:47 +0300
From:   Grygorii Strashko <grygorii.strashko@...com>
To:     Lokesh Vutla <lokeshvutla@...com>, Tero Kristo <t-kristo@...com>,
        Nishanth Menon <nm@...com>, Rob Herring <robh+dt@...nel.org>
CC:     Sekhar Nori <nsekhar@...com>, <linux-kernel@...r.kernel.org>,
        Linux ARM Mailing List <linux-arm-kernel@...ts.infradead.org>,
        Kishon Vijay Abraham I <kishon@...com>
Subject: Re: [PATCH 0/4] arm64: Initial support for Texas Instrument's J7200
 Platform



On 28/07/2020 22:19, Grygorii Strashko wrote:
> 
> 
> On 23/07/2020 11:46, Lokesh Vutla wrote:
>> This series adds initial support for latest new SoC, J7200, from Texas Instruments.
>>
>> The J7200 SoC is a part of the K3 Multicore SoC architecture platform.
>> It is targeted for for automotive gateway, vehicle compute systems,
>> Vehicle-to-Vehicle (V2V) and Vehicle-to-Everything (V2X) applications.
>> The SoC aims to meet the complex processing needs of modern embedded products.
>>
>> See J7200 Technical Reference Manual (SPRUIU1, June 2020)
>> for further details: https://www.ti.com/lit/pdf/spruiu1
>>
>> Testing:
>> - Boot log: https://pastebin.ubuntu.com/p/FvpzWjf7tw/
>> - ./scripts/checkpatch --strict
>>     - Few warningns about Line length exceeding 100 columns.
>>       But these are corresponding to comments
>> - v8make dtbs_check
>> - DT_SCHEMA_FLAGS="-u"
>>    DT_SCHEMA_FILES="Documentation/devicetree/bindings/arm/ti/k3.yaml"
>>    v8make dtbs_check
>> - DT_SCHEMA_FLAGS="-u"
>>    DT_SCHEMA_FILES="Documentation/devicetree/bindings/arm/ti/k3.yaml"
>>    v8make dt_binding_check
>>
>> Lokesh Vutla (4):
>>    dt-bindings: arm: ti: Add bindings for J7200 SoC
>>    dt-bindings: arm: ti: Convert K3 board/soc bindings to DT schema
>>    arm64: dts: ti: Add support for J7200 SoC
>>    arm64: dts: ti: Add support for J7200 Common Processor Board
>>
>>   .../devicetree/bindings/arm/ti/k3.txt         |  26 ---
>>   .../devicetree/bindings/arm/ti/k3.yaml        |  28 +++
>>   MAINTAINERS                                   |   2 +-
>>   arch/arm64/boot/dts/ti/Makefile               |   3 +-
>>   .../dts/ti/k3-j7200-common-proc-board.dts     |  64 ++++++
>>   arch/arm64/boot/dts/ti/k3-j7200-main.dtsi     | 199 ++++++++++++++++++
>>   .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi      |  84 ++++++++
>>   arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi   |  29 +++
>>   arch/arm64/boot/dts/ti/k3-j7200.dtsi          | 165 +++++++++++++++
>>   9 files changed, 572 insertions(+), 28 deletions(-)
>>   delete mode 100644 Documentation/devicetree/bindings/arm/ti/k3.txt
>>   create mode 100644 Documentation/devicetree/bindings/arm/ti/k3.yaml
>>   create mode 100644 arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts
>>   create mode 100644 arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
>>   create mode 100644 arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
>>   create mode 100644 arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi
>>   create mode 100644 arch/arm64/boot/dts/ti/k3-j7200.dtsi
>>
> 
> I have networking enabled on top of this series here.
> 
> ssh://git@...bucket.itg.ti.com/~x1045550/ti-priv-linux-kernel.git ti-linux-5.4.y-for-next-pull
> 
> But DMA failed for Main domain.
>      0.781005] ti-udma 31150000.dma-controller: NAVSS ti,sci-dev-id read failure -22
> [    0.788684] ti-udma: probe of 31150000.dma-controller failed with error -22
> 
> http://lcpdresults.itg.ti.com/launcher/results/8013
> 
> Is there anything (except my comment for patch 3) which prevents this from been merged?
> 

Sry. Pls. ignore this mail.

-- 
Best regards,
grygorii