From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jyri Sarha <jsarha@ti.com>
Cc: dri-devel@lists.freedesktop.org, tony@atomide.com,
sam@ravnborg.org, robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, tomi.valkeinen@ti.com,
peter.ujfalusi@ti.com, bparrot@ti.com
Subject: Re: [PATCH v2 2/3] dt-bindings: display: Add obsolete note to "ti,tilcdc,panel" binding
Date: Fri, 13 Dec 2019 12:36:50 +0200 [thread overview]
Message-ID: <20191213103650.GA4860@pendragon.ideasonboard.com> (raw)
In-Reply-To: <5f585e0b-be58-b474-f27b-875e254426a8@ti.com>
Hi Jyri,
On Fri, Dec 13, 2019 at 11:04:49AM +0200, Jyri Sarha wrote:
> On 09/12/2019 16:50, Laurent Pinchart wrote:
> > On Mon, Dec 09, 2019 at 04:42:15PM +0200, Jyri Sarha wrote:
> >> The "ti,tilcdc,panel" binding should not be used anymore, since tilcdc
> >> is fully capable of using generic drm panels like panel-simple and
> >> panel-common binding. However, the obsolete binding is still widely
> >> used in many mainline supported platforms that I do not have access to
> >> and who knows how many custom platforms. So I am afraid we have to
> >> keep the old bundled tilcdc panel driver around.
> >
> > But can't we drop the bindings instead of marking them as obsolete, even
> > if we keep the driver around for some time ?
> >
>
> I guess that would be alright too.
>
> > Also, would it make sense to set a date for the removal of the driver,
> > and add it to the WARN() message in patch 3/3 ?
> >
>
> Not sure about a date. I would feel quite uncomfortable of removing the
> driver, while there is still mainline DTSes using "ti,tilcdc,panel". I
> guess the next step would be putting the legacy panel driver behind a
> default = N config option. Then I would probably hear something if there
> are people actively using those DTSes. Maybe the date could be about
> that too.
The mainline DTSes are not really an issue, they should be fixed in
mainline to use new bindings, and all will be good. The problem is
systems using out-of-tree DTSes, or systems that will upgrade the kernel
but not the DT.
> >> Signed-off-by: Jyri Sarha <jsarha@ti.com>
> >> ---
> >> Documentation/devicetree/bindings/display/tilcdc/panel.txt | 6 ++++++
> >> 1 file changed, 6 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/display/tilcdc/panel.txt b/Documentation/devicetree/bindings/display/tilcdc/panel.txt
> >> index 808216310ea2..54963f9173cc 100644
> >> --- a/Documentation/devicetree/bindings/display/tilcdc/panel.txt
> >> +++ b/Documentation/devicetree/bindings/display/tilcdc/panel.txt
> >> @@ -1,5 +1,11 @@
> >> Device-Tree bindings for tilcdc DRM generic panel output driver
> >>
> >> +NOTE: This binding (and the related driver) is obsolete and should not
> >> + be used anymore. Please refer to drm panel-common binding (and
> >> + to a generic drm panel driver like panel-simple).
> >> + Documentation/devicetree/bindings/display/panel/panel-common.yaml
> >> + (drivers/gpu/drm/panel/panel-simple.c)
> >> +
> >> Required properties:
> >> - compatible: value should be "ti,tilcdc,panel".
> >> - panel-info: configuration info to configure LCDC correctly for the panel
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2019-12-13 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 14:42 [PATCH v2 0/3] drm/tilcdc: Remove "ti,tilcdc,tfp410" and mark "ti,tilcdc,panel" obsolete Jyri Sarha
2019-12-09 14:42 ` [PATCH v2 1/3] drm/tilcdc: Remove obsolete bundled tilcdc tfp410 driver Jyri Sarha
2019-12-09 14:42 ` [PATCH v2 2/3] dt-bindings: display: Add obsolete note to "ti,tilcdc,panel" binding Jyri Sarha
2019-12-09 14:50 ` Laurent Pinchart
2019-12-13 9:04 ` Jyri Sarha
2019-12-13 10:36 ` Laurent Pinchart [this message]
2019-12-09 14:42 ` [PATCH v2 3/3] drm/tilcdc: panel: Add WARN() with a comment to tilcdc-panel probe Jyri Sarha
2019-12-09 14:48 ` Laurent Pinchart
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=20191213103650.GA4860@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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).