From: Tero Kristo <t-kristo@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
Jyri Sarha <jsarha@ti.com>, Nishanth Menon <nm@ti.com>,
Rob Herring <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] arm64: dts: ti: k3-j721e-main.dtsi: Add DSS node
Date: Mon, 27 Apr 2020 14:41:37 +0300 [thread overview]
Message-ID: <6427a827-9175-75ab-72fb-a62a21795bf3@ti.com> (raw)
In-Reply-To: <3eb05f6d-523f-f7e5-a0e9-d47b852fe079@ti.com>
On 27/04/2020 14:37, Tomi Valkeinen wrote:
> On 27/04/2020 14:15, Tomi Valkeinen wrote:
>> On 27/04/2020 14:10, Jyri Sarha wrote:
>>> On 27/04/2020 13:51, Tomi Valkeinen wrote:
>>>> On 27/04/2020 13:37, Jyri Sarha wrote:
>>>>> On 27/04/2020 13:09, Tero Kristo wrote:
>>>>>>> + status = "disabled";
>>>>>>
>>>>>> Again, why disabled by default?
>>>>>>
>>>>>
>>>>> tidss device is not functional without a defined video-port. The
>>>>> driver
>>>>> is not implemented in a way that it would handle a broken
>>>>> configuration
>>>>> gracefully.
>>>>
>>>> Then we need to fix it. The driver should handle the case where there
>>>> are no ports defined just fine.
>>>>
>>>
>>> Just by reading the code, I would say that currently the probe would
>>> fail with returned -ENOMEM after calling drm_vblank_init() with zero
>>> CRTCs.
>>>
>>> So should the probe fail gracefully and silently, or should we try to
>>> register a DRM device with no CRTCs? Is that even possible?
>>
>> My first thought is that the driver should exit probe silently with
>> ENODEV if there are no outputs defined (but, of course, with
>> EPROBE_DEFER if there are outputs which haven't been probed yet).
>>
>> It gets a bit more complex if we ever support writeback, as that can
>> be used as mem-to-mem without any displays, but I think we can ignore
>> that for now.
>
> In any case, that's not the reason for status = "disabled", so that
> discussion is not related to these patches as such.
>
> The reason to have DSS disabled is just to prevent pointless driver
> probing. When a board dts or a DT overlay adds a display, the DSS DT
> node has to be modified anyway to add the DT graph and the panel/bridge
> data. So one can as well add the single line of "status = enabled" there.
Ok, thanks for the explanation, queued all three patches towards 5.8
based on that.
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2020-04-27 11:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 9:15 [PATCH 1/3] arm64: dts: ti: am654: Add DSS node Tomi Valkeinen
2020-04-22 9:15 ` [PATCH 2/3] arm64: dts: ti: k3-j721e-main.dtsi: " Tomi Valkeinen
2020-04-27 10:09 ` Tero Kristo
2020-04-27 10:37 ` Jyri Sarha
2020-04-27 10:41 ` Tero Kristo
2020-04-27 10:49 ` Jyri Sarha
2020-04-27 10:51 ` Tomi Valkeinen
2020-04-27 11:10 ` Jyri Sarha
2020-04-27 11:15 ` Tomi Valkeinen
2020-04-27 11:37 ` Tomi Valkeinen
2020-04-27 11:41 ` Tero Kristo [this message]
2020-04-22 9:15 ` [PATCH 3/3] arm64: dts: ti: k3-j721e-common-proc-board: add assigned clks for DSS Tomi Valkeinen
2020-04-27 10:08 ` [PATCH 1/3] arm64: dts: ti: am654: Add DSS node Tero Kristo
2020-04-27 10:50 ` Tomi Valkeinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6427a827-9175-75ab-72fb-a62a21795bf3@ti.com \
--to=t-kristo@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jsarha@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=tomi.valkeinen@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).