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]
Date:   Mon, 21 Mar 2022 09:59:52 +0100
From:   Krzysztof Kozlowski <krzk@...nel.org>
To:     Tony Huang 黃懷厚 <tony.huang@...plus.com>,
        Tony Huang <tonyhuang.sunplus@...il.com>,
        "ulf.hansson@...aro.org" <ulf.hansson@...aro.org>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "lhjeff911@...il.com" <lhjeff911@...il.com>,
        "linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "p.zabel@...gutronix.de" <p.zabel@...gutronix.de>
Cc:     Wells Lu 呂芳騰 <wells.lu@...plus.com>
Subject: Re: [PATCH v4 1/2] dt-binding: mmc: Add mmc yaml file for Sunplus
 SP7021

On 21/03/2022 03:35, Tony Huang 黃懷厚 wrote:
> Dear Krzysztof:
> 
>>> +++ b/Documentation/devicetree/bindings/mmc/sunplus,mmc.yaml
>>> @@ -0,0 +1,79 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) # Copyright
>>> +(C) Sunplus Ltd. Co. 2021 %YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/mmc/sunplus,mmc.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: sunplus MMC controller
>>
>> s/sunplus/Sunplus/
>>
> 
> Below is my modification:
> title: Sunplus MMC Controller
> 
>>> +
>>> +allOf:
>>> +  - $ref: "mmc-controller.yaml"
>>
>> allOf below maintainers,
>>
> 
> I will modify it.
> 
>>> +
>>> +maintainers:
>>> +  - Tony Huang <tonyhuang.sunplus@...il.com>
>>> +  - Li-hao Kuo <lhjeff911@...il.com>
>>> +
>>> +properties:
>>> +  compatible:
>>> +    enum:
>>> +      - sunplus,mmc-v1
>>> +      - sunplus,mmc-v2
>>
>> How did this happen? Versions of blocks are usually discouraged, unless you
>> have clear specification,. The previous discussion did not end with "add v1 and
>> v2".
>>
>> Do you have clear documentation/specification of these blocks? If no, please
>> use SoC compatibles.
>>
> 
> v1: support SDIO 2.0							
> v2: support eMMC 4.41		

That's spec is not enough. You need to provide detailed specification of
each of them. See for example versioned blocks of Synopsys DeisgnWare
(e.g. eMMC/SDHCI).

					
> The register base address and offset address of emmc and sd card are different.							
> eMMC and sdcard are individual hardware settings							
> We need version to distinguish different speeds	

That's not the answer. How did it happen that you have now versions and
before there were SoC compatibles? No one pointed to this and you did
not mention it in description of changes.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ