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: <5ad2d9a8-d60f-6541-6efd-2fa036ec7517@ti.com>
Date:   Mon, 18 Jan 2021 10:28:34 +0530
From:   Sekhar Nori <nsekhar@...com>
To:     David Lechner <david@...hnology.com>, Suman Anna <s-anna@...com>,
        <linux-arm-kernel@...ts.infradead.org>
CC:     Rob Herring <robh+dt@...nel.org>,
        Santosh Shilimkar <ssantosh@...nel.org>,
        Grzegorz Jaszczyk <grzegorz.jaszczyk@...aro.org>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: soc: ti: ti,pruss: add ti,am1806-pruss

On 17/01/21 1:48 AM, David Lechner wrote:
> On 1/15/21 10:45 AM, Suman Anna wrote:
>> + Sekhar and Bartosz
>>
>> Hi David,
>>
>> On 1/4/21 12:30 PM, David Lechner wrote:
>>> This adds a "ti,am1806-pruss" compatible type for the PRUSS found in
>>> TI AM18xx/OMAP-L138 SoCs.
>>>
>>> Signed-off-by: David Lechner <david@...hnology.com>
>>> ---
>>>   Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 2 ++
>>>   1 file changed, 2 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>> b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>> index 037c51b2f972..a6ed23fdbc00 100644
>>> --- a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>> +++ b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>>> @@ -61,6 +61,7 @@ properties:
>>>       compatible:
>>>       enum:
>>> +      - ti,am1806-pruss  # for AM18xx/OMAP-L138 SoC family
>>
>> Almost all the drivers for these SoCs use the prefix "ti,da850-xxx"
>> for the
>> compatibles. Can we switch to using those instead of ti,am1806?
> 
> I wasn't sure which chips exactly are "DA850". If someone can tell
> me, I can look at the docs to see if they have a PRUSS.

Hi David, you can treat DA850 is same as OMAP-L138 for all purposes in
kernel.

Thanks,
Sekhar

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ