linux-kernel - Re: [PATCH v2 2/9] dt-bindings: riscv: microchip: document the aries m100pfsevp

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: <69027950-f18d-c9a7-9f0b-d73ef68197c7@microchip.com>
Date:   Tue, 30 Aug 2022 16:59:19 +0000
From:   <Conor.Dooley@...rochip.com>
To:     <krzysztof.kozlowski@...aro.org>, <Conor.Dooley@...rochip.com>,
        <robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
        <Daire.McNamara@...rochip.com>, <Shravan.Chippa@...rochip.com>
CC:     <paul.walmsley@...ive.com>, <palmer@...belt.com>,
        <aou@...s.berkeley.edu>, <Cyril.Jean@...rochip.com>,
        <Lewis.Hanly@...rochip.com>, <Praveen.Kumar@...rochip.com>,
        <wg@...es-embedded.de>, <Hugh.Breslin@...rochip.com>,
        <devicetree@...r.kernel.org>, <linux-riscv@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 2/9] dt-bindings: riscv: microchip: document the aries
 m100pfsevp

On 30/08/2022 17:55, Krzysztof Kozlowski wrote:
> On 30/08/2022 18:25, Conor.Dooley@...rochip.com wrote:
>> On 30/08/2022 15:37, Krzysztof Kozlowski wrote:
>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>>
>>> On 30/08/2022 13:17, Conor Dooley wrote:
>>>> Add compatibles for both configurations of the Aries Embedded
>>>> M100PFSEVP SOM + EVK platform.
>>>>
>>>> Link: https://www.aries-embedded.com/polarfire-soc-fpga-microsemi-m100pfs-som-mpfs025t-pcie-serdes
>>>> Signed-off-by: Conor Dooley <conor.dooley@...rochip.com>
>>>> ---
>>>>  Documentation/devicetree/bindings/riscv/microchip.yaml | 3 +++
>>>>  1 file changed, 3 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/riscv/microchip.yaml b/Documentation/devicetree/bindings/riscv/microchip.yaml
>>>> index 485981fbfb4b..04ebd48caaa7 100644
>>>> --- a/Documentation/devicetree/bindings/riscv/microchip.yaml
>>>> +++ b/Documentation/devicetree/bindings/riscv/microchip.yaml
>>>> @@ -27,9 +27,12 @@ properties:
>>>>
>>>>        - items:
>>>>            - enum:
>>>> +              - aries,m100pfsevp-emmc
>>>> +              - aries,m100pfsevp-sdcard
>>>
>>> Usually sd card is pluggable, so what is the actual difference here? For
>>> example this one:
>>> https://shop.aries-embedded.de/evaluation-kit/m/m100pfsevp/445/m100pfsevp-250baab
>>> has eMMC and SD card...
>>
>> Yeah, both are there but it is muxed by the bootloader using a GPIO. For
>> icicle this is done by a mux in the FPGA fabric instead. T
> 
> Ah, this is still just one MMC controller - either as eMMC or as SD-card?

Yes.

> 
>> w dts were
>> needed so that the gpio-hog could be set correctly. Out of curiosity, I can
>> have the same compatible in multiple devicetrees right? In that case, it
>> would just be "aries,m100pfsevp" here and I could put that in both?
>> Would make things easier..
> 
> Depends, but I would say for this case rather not. The compatible should
> identify the board. If the boards are different, one compatible should
> not identify both of them. Imagine U-Boot (or something else) trying to
> match the DTS.

It is the same board though, the way the bootloader works is that if it
detects an SD-card it will use that to boot from, and if not will fall back
to the emmc.