[lkml]   [2023]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] dt-bindings: mmc: fsl-imx-esdhc: allow more compatible combinations
On Sat, 7 Jan 2023 15:09:24 +0100
Krzysztof Kozlowski <> wrote:

> On 07/01/2023 15:07, Andreas Kemnade wrote:
> > On Sat, 7 Jan 2023 15:00:56 +0100
> > Krzysztof Kozlowski <> wrote:
> >
> > [...]
> >>>> I asked to remove half-compatible. Not to enforce.
> >>>>
> > so you are saying that allowing
> > compatible = "A", "B"
> > is not ok, if B is not fully compatible. I agree with that
> > one.
> I did not say that. It's not related to this problem.
You said "I asked to remove half-compatible" that means to me
remove "B" if not fully compatible with A which sounds sane to me.

> Again - you cannot have device which is and is not compatible with
> something else. It's not a Schroedinger's cat to be in two states,
> unless you explicitly document the cases (there are exception). If this
> is such exception, it requires it's own documentation.
so conclusion:
If having A and B half-compatible with A:

compatible = "A" only: is allowed to specifiy it the binding (status quo),
but not allowed to make the actual dtsi match the binding documentation

compatible = "A", "B" in the binding definition: is not allowed ("I asked to remove
half-compatible" (= removing B))

having mismatch between binding definition and devicetree causes dtbs_check errors
-> also not nice.

I rather drop this patch and learn to live with dtbs_check errors
for this one since I have no idea how to proceed. All roads are blocked.
This all causes too much churn.


 \ /
  Last update: 2023-03-26 23:31    [W:0.049 / U:1.268 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site