[<prev] [next>] [day] [month] [year] [list]
Message-ID: <9f197b20-499a-7437-bff3-c5fbd39b5387@linaro.org>
Date: Sun, 12 Mar 2023 18:29:47 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Sergey Lisov <sleirsgoevy@...il.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Jaehoon Chung <jh80.chung@...sung.com>
Cc: linux-mmc@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: exynos-dw-mshc-common: add exynos78xx
variants
On 12/03/2023 18:26, Sergey Lisov wrote:
>> Thanks for letting me know.
>>
>> https://elixir.bootlin.com/linux/v6.1-rc1/source/Documentation/devicetree/bindings/writing-bindings.rst#L42
>
> OK, at least its codified somewhere.
You got feedback from Devicetree maintainer. It should have been enough.
> Still, this results in the opposite
> effect: DTBs written for one SoC, using compatibles from other SoCs just
> because "they are the same anyway". And doing this properly, well, results
> in essentially duplicate compatibles.
>
> And "fallback compatibles" won't solve this case anyway, as there is no
> common compatible that denotes "Exynos7 DW-MMC that has the bug".
Your explanation is not correct and we talked about this so many times.
No wildcards in compatibles. That's the rule. You cannot find any
argument good enough to break that rule.
Best regards,
Krzysztof
Powered by blists - more mailing lists