Received-SPF: pass (google.com: domain of linux-kernel+bounces-138375-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Message-ID: <dd78b1ef-366a-41e4-8046-e368539839df@gmail.com>
Date: Wed, 10 Apr 2024 13:57:06 +0300
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH v2 1/2] dt-bindings: mfd: Add ROHM BD71879
Content-Language: en-US, en-GB
To: Conor Dooley <conor@kernel.org>
Cc: Andreas Kemnade <andreas@kemnade.info>, lee@kernel.org,
 robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
 devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
References: <20240404195423.666446-1-andreas@kemnade.info>
 <20240404195423.666446-2-andreas@kemnade.info>
 <3d5df067-ec94-42c6-bbd0-43ce8cd53e40@gmail.com>
 <20240410-possum-lecturer-716185901aa5@spud>
From: Matti Vaittinen <mazziesaccount@gmail.com>
In-Reply-To: <20240410-possum-lecturer-716185901aa5@spud>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 4/10/24 13:03, Conor Dooley wrote:
> On Wed, Apr 10, 2024 at 10:57:08AM +0300, Matti Vaittinen wrote:
>> On 4/4/24 22:54, Andreas Kemnade wrote:
>>> As this chip was seen in several devices in the wild, add it.
>>>
>>> Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
>>> Suggested-by: Matti Vaittinen <mazziesaccount@gmail.com>
>>> ---
>>>    .../devicetree/bindings/mfd/rohm,bd71828-pmic.yaml         | 7 ++++++-
>>>    1 file changed, 6 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml b/Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml
>>> index 0b62f854bf6b..07f99738fcf6 100644
>>> --- a/Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml
>>> +++ b/Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml
>>> @@ -17,7 +17,12 @@ description: |
>>>    properties:
>>>      compatible:
>>> -    const: rohm,bd71828
>>> +    oneOf:
>>> +      - const: rohm,bd71828
>>> +
>>> +      - items:
>>> +          - const: rohm,bd71879
>>> +          - const: rohm,bd71828
>>>      reg:
>>>        description:
>>
>> Am I correct, this reads as:
>>
>> Either
>> 	compatible = rohm,bd71828
>> or
>> 	compatible = rohm,bd71879, rohm,bd71828
>>
>> but not compatible = rohm,bd71879?
> 
> Correct.

Thanks Conor!

I guess that if we later find out that there is a 'gizmo' in BD71828 
which is not present on BD71879 - and if we write driver supporting 
this, then we need to have handling for both the BD71879 and BD71828 in 
this driver to ensure the fall-back wont happen. It's a bit ugly as I 
think the fall-back compatible should be used only in case where the 
"fall-back" HW can be guaranteed to have exactly same, or a subset of, 
features of the "full board".

Well, I've been told these are similar by HW colleagues. I have my 
doubts if 'similar' really is '_similar_', or if it's 'similar, except 
of course...' - but let's trust the HW guys on this. We have the above 
mentioned workaround if we should not have trusted...

Acked-By: Matti Vaittinen <mazziesaccount@gmail.com>

-- 
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland

~~ When things go utterly wrong vim users can always type :help! ~~