On 09/04/2022 15:05, H. Nikolaus Schaller wrote:
>>
>> This looks wrong, the block usually should have a specific compatible.
>> Please mention why it does not.
>
> Well, I did not even have that idea that it could need an explanation.
>
> There is no "ingenic,jz4780-otg" and none is needed here to make it work.
Make it work in what terms? We talk about hardware description, right?
>
> Therefore the generic "snps,dwc2" is sufficient.
No, you are mixing now driver behavior (is sufficient) with hardware
description. Most of licensed blocks require the specific compatible to
differentiate it.
Best regards,
Krzysztof
> Am 09.04.2022 um 15:15 schrieb Krzysztof Kozlowski <[email protected]>:
>
> On 09/04/2022 15:05, H. Nikolaus Schaller wrote:
>>>
>>> This looks wrong, the block usually should have a specific compatible.
>>> Please mention why it does not.
>>
>> Well, I did not even have that idea that it could need an explanation.
>>
>> There is no "ingenic,jz4780-otg" and none is needed here to make it work.
>
> Make it work in what terms? We talk about hardware description, right?
Yes.
>
>>
>> Therefore the generic "snps,dwc2" is sufficient.
>
> No, you are mixing now driver behavior (is sufficient) with hardware
> description.
No. "snps,dwc2" is a hardware description for a licensed block.
Not a driver behavior.
> Most of licensed blocks require the specific compatible to
> differentiate it.
If there is a need to differentiate.