Hi Geert,
On 15/02/18 09:07, Geert Uytterhoeven wrote:
> Hi Kieran,
>
> On Thu, Feb 15, 2018 at 9:38 AM, Kieran Bingham <kbingham@xxxxxxxxxx> wrote:
>> From: Kieran Bingham <kieran.bingham+renesas@xxxxxxxxxxxxxxxx>
>>
>> The r8a77995 D3 platform has 2 LVDS channels connected to the DU.
>>
>> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@xxxxxxxxxxxxxxxx>
>
> I love your patch!
> Yet something to improve...
>
>> --- a/arch/arm64/boot/dts/renesas/r8a77995.dtsi
>> +++ b/arch/arm64/boot/dts/renesas/r8a77995.dtsi
>> @@ -773,18 +773,70 @@
>> port@1 {
>> reg = <1>;
>> du_out_lvds0: endpoint {
>> + remote-endpoint = <&du_out_lvds0>;
>> };
>> };
>>
>> port@2 {
>> reg = <2>;
>> du_out_lvds1: endpoint {
>> + remote-endpoint = <&du_out_lvds1>;
>> };
>> };
>> };
>> };
>> };
>>
>> + lvds0: lvds@feb90000 {
>> + compatible = "renesas,lvds-r8a77995";
>> + reg = <0 0xfeb90000 0 0x20>;
>> + clocks = <&cpg CPG_MOD 727>;
>> + status = "disabled";
>
> Missing resets, power-domains
Both lvds0, and lvds1 are actually the same 'module' (just different mappings
within the same IP block).
That means they will share clock, reset etc.
Will specifying the resets cause one to affect the other unduly?
like if one becomes un-used, will it power down? or is it refcounted, and will
gracefully handle both device nodes from the same device?
I'm already fairly sure clocks is fine for this - but it's just the reset's that
worry me. If the reset module tries to reset lvds0 for some reason - would lvds1
get reset as a side effect ...
Or perhaps that won't ever happen with an :
power-domains = <&sysc R8A77995_PD_ALWAYS_ON>;
resets = <&cpg 727>;
Regards
--
Kieran
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
