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:   Fri, 3 Mar 2023 14:00:21 +0530
From:   Ravi Gunasekaran <r-gunasekaran@...com>
To:     Andrew Davis <afd@...com>, <nm@...com>, <vigneshr@...com>,
        <kristo@...nel.org>, <robh+dt@...nel.org>,
        <krzysztof.kozlowski+dt@...aro.org>, <s-vadapalli@...com>,
        <vaishnav.a@...com>, Ravi Gunasekaran <r-gunasekaran@...com>
CC:     <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v12 3/8] arm64: dts: ti: k3-j721s2-mcu-wakeup: Add support
 of OSPI

Andrew,

On 02/03/23 9:03 am, Ravi Gunasekaran wrote:
> 
> 
> On 01/03/23 9:27 pm, Andrew Davis wrote:
>> On 3/1/23 3:11 AM, Ravi Gunasekaran wrote:
>>> From: Aswath Govindraju <a-govindraju@...com>
>>>
>>> Add support for two instance of OSPI in J721S2 SoC.
>>>
>>> Reviewed-by: Vaishnav Achath <vaishnav.a@...com>
>>> Signed-off-by: Aswath Govindraju <a-govindraju@...com>
>>> Signed-off-by: Matt Ranostay <mranostay@...com>
>>> Signed-off-by: Ravi Gunasekaran <r-gunasekaran@...com>
>>> ---

[...]

>>>
>>>   .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi     | 46 +++++++++++++++++++
>>>   1 file changed, 46 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
>>> index 0af242aa9816..ab3ce8be7216 100644
>>> --- a/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
>>> +++ b/arch/arm64/boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi
>>> @@ -306,4 +306,50 @@
>>>               ti,cpts-periodic-outputs = <2>;
>>>           };
>>>       };
>>> +
>>> +    fss: bus@...00000 {
>>> +        compatible = "simple-bus";
>>> +        #address-cells = <2>;
>>> +        #size-cells = <2>;
>>> +        ranges = <0x00 0x47000000 0x00 0x47000000 0x00 0x00068400>,
>>> +             <0x05 0x00000000 0x05 0x00000000 0x01 0x00000000>,
>>> +             <0x07 0x00000000 0x07 0x00000000 0x01 0x00000000>;
>>> +
>>> +        status = "disabled";
>>
>> Since this node doesn't need pinmux, why is it default disabled? Same for
>> the other parent nodes in this series.
>>
>> Andrew
> 
> In this patch and others in this series, since child node is disabled,
> I thought of disabling the parent as well. And to later enable the
> parent node at the time when the child node needs to be enabled.
> 

Could you please provide your input on this?

If the preferred way is to keep the parent node enabled, then I will
do so. For the IPs added in this series, if the parent node needs additional
information such as pinmux, gpio, I will disable both parent and child.
And if only child node(s) need additional info, then I will keep the parent
enabled and children disabled. 

>>
>>> +
>>> +        ospi0: spi@...40000 {
>>> +            compatible = "ti,am654-ospi", "cdns,qspi-nor";
>>> +            reg = <0x00 0x47040000 0x00 0x100>,
>>> +                  <0x05 0x00000000 0x01 0x00000000>;
>>> +            interrupts = <GIC_SPI 840 IRQ_TYPE_LEVEL_HIGH>;
>>> +            cdns,fifo-depth = <256>;
>>> +            cdns,fifo-width = <4>;
>>> +            cdns,trigger-address = <0x0>;
>>> +            clocks = <&k3_clks 109 5>;
>>> +            assigned-clocks = <&k3_clks 109 5>;
>>> +            assigned-clock-parents = <&k3_clks 109 7>;
>>> +            assigned-clock-rates = <166666666>;
>>> +            power-domains = <&k3_pds 109 TI_SCI_PD_EXCLUSIVE>;
>>> +            #address-cells = <1>;
>>> +            #size-cells = <0>;
>>> +
>>> +            status = "disabled"; /* Needs pinmux */
>>> +        };
>>> +
>>> +        ospi1: spi@...50000 {
>>> +            compatible = "ti,am654-ospi", "cdns,qspi-nor";
>>> +            reg = <0x00 0x47050000 0x00 0x100>,
>>> +                  <0x07 0x00000000 0x01 0x00000000>;
>>> +            interrupts = <GIC_SPI 841 IRQ_TYPE_LEVEL_HIGH>;
>>> +            cdns,fifo-depth = <256>;
>>> +            cdns,fifo-width = <4>;
>>> +            cdns,trigger-address = <0x0>;
>>> +            clocks = <&k3_clks 110 5>;
>>> +            power-domains = <&k3_pds 110 TI_SCI_PD_EXCLUSIVE>;
>>> +            #address-cells = <1>;
>>> +            #size-cells = <0>;
>>> +
>>> +            status = "disabled"; /* Needs pinmux */
>>> +        };
>>> +    };
>>>   };
> 

-- 
Regards,
Ravi

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ