On 8.1.2019 16:00, Vokáč Michal wrote:
> On 8.1.2019 15:56, Rob Herring wrote:
>> On Tue, Jan 8, 2019 at 5:43 AM Vokáč Michal <Michal.Vokac@xxxxxxxxx> wrote:
>>>
>>> On 29.12.2018 00:25, Rob Herring wrote:
>>>> On Tue, Dec 18, 2018 at 02:42:11PM +0000, Vokáč Michal wrote:
>>>>> These are i.MX6S/DL based SBCs embedded in various Y Soft products.
>>>>> All share the same board design but have slightly different HW
>>>>> configuration.
>>
>> [...]
>>
>>>>> +/ {
>>>>> + model = "Y Soft IOTA Draco i.MX6Solo board";
>>>>> + compatible = "ysoft,imx6dl-yapp4-draco", "fsl,imx6dl";
>>>>
>>>> All compatible strings should be documented, not just SoC vendor boards.
>>>
>>> OK, I will add a Documentation/devicetree/bindings/arm/ysoft.yaml file for that.
>>
>> Actually, it should go in fsl.yaml. The file for every board vendor is
>> gone. i.MX was pretty much the only platform doing that.
>
> OK, I will do so. Thank you.
I am sorry for the noise Rob, but your "dt-bindings: arm: Convert FSL
board/soc bindings to json-schema" patch is not in mainline yet. So
there is no arm/fsl.yaml file to add my compatible strings into.
Now I do not know how to respin. Should I send this updated dts/dtsi
patch as usual and create another patch with the ysoft compatible
strings against your yaml-bindings-v2 branch, where the fsl.yaml file
exist? Or something else?
Thank you,
Michal
