From: Daniel Vetter <daniel@ffwll.ch>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: Leonard Crestez <leonard.crestez@nxp.com>,
"festevam@gmail.com" <festevam@gmail.com>,
"stefan@agner.ch" <stefan@agner.ch>,
"marex@denx.de" <marex@denx.de>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"marcofrk@gmail.com" <marcofrk@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] drm: mxsfb: Change driver.name to mxsfb-drm
Date: Mon, 18 Jun 2018 09:43:20 +0200 [thread overview]
Message-ID: <20180618074320.GS3438@phenom.ffwll.local> (raw)
In-Reply-To: <6995fa4b-47a9-887b-5e4f-4284ca6a2c79@gmail.com>
On Sat, Jun 16, 2018 at 01:32:44AM +0200, Marek Vasut wrote:
> On 06/16/2018 12:42 AM, Leonard Crestez wrote:
> > On Fri, 2018-06-15 at 23:36 +0200, Marek Vasut wrote:
> >> On 06/15/2018 10:58 PM, Leonard Crestez wrote:
> >>> On Fri, 2018-06-15 at 16:47 -0300, Fabio Estevam wrote:
> >>>> On Fri, Jun 15, 2018 at 4:43 PM, Leonard Crestez
> >>>> <leonard.crestez@nxp.com> wrote:
> >
> >>>>> The FBDEV driver uses the same name and both can't be registered at the
> >>>>> same time. Fix this by renaming the drm driver to mxsfb-drm
> >>>>
> >>>> Stefan sent the same patch a few days ago:
> >>>
> >>> In that thread there is a proposal for removing the old fbdev/mxsfb
> >>> driver entirely.
> >>>
> >>> That would break old DTBs, isn't this generally considered bad? Also,
> >>> are we sure the removal of fbdev/mxsfb wouldn't lose any features?
> >>>
> >>> What my series does is make both drivers work with the same kernel
> >>> image and turns the choice into a board-level dtb decision. Supporting
> >>> everything at once seems desirable to me and it allows for a very
> >>> smooth upgrade path.
> >>
> >> Having two drivers in the kernel with different set of bugs is always bad.
> >>
> >>> The old driver could be removed later, after all users are converted.
> >>
> >> Both drivers were in for long enough already. And let's be realistic,
> >> how many MX23/MX28 users of old DTs with new kernels are there who
> >> cannot update the DT as well ?
> >
> > Grepping for "display =" in arch/arm/boot/dts/imx* I see that old
> > bindings are also used by 3rd-party boards for imx6/7:
> > * imx6sx-nitrogen6sx
> > * imx6ul-geam
> > * imx6ul-isiot
> > * imx6ul-opos6uldev
> > * imx6ul-pico-hobbit
> > * imx6ul-tx6ul
> > * imx7d-nitrogen7
>
> Er, yes, a handful of boards which could be updated :)
>
> > Converting everything might be quite a bit of work, and explicitly
> > supporting old bindings is also work.
>
> Does adding support for old bindings justify the effort invested ? I
> doubt so, it only adds more code to maintain.
>
> > It is very confusing that there is a whole set of displays for imx6/7
> > which are supported by upstream but only with a non-default config.
> > While it is extremely common in the embedded field to have custom
> > configs the default one in the kernel should try to "just work".
> >
> > Couldn't this patch series be considered a bugfix? It was also
> > surprisingly small.
>
> I think it's just a workaround which allows you to postpone the real
> fix, and I don't like that.
Yeah agreed, imo the proper fix here would be to either update the dts for
the affected boards and/or make mxsfb accept the old dt bindings for
backwards compat. Artificially extending the life of the fbdev drivers
seems silly.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2018-06-18 7:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 19:43 [PATCH 0/3] ARM: imx: Make DRM_MXSFB and FB_MXS coexist Leonard Crestez
2018-06-15 19:43 ` [PATCH 1/3] drm: mxsfb: Change driver.name to mxsfb-drm Leonard Crestez
2018-06-15 19:47 ` Fabio Estevam
2018-06-15 20:58 ` Leonard Crestez
2018-06-15 21:05 ` Fabio Estevam
2018-06-15 21:36 ` Marek Vasut
2018-06-15 22:22 ` Fabio Estevam
2018-06-15 23:29 ` Marek Vasut
2018-06-15 22:42 ` Leonard Crestez
2018-06-15 23:32 ` Marek Vasut
2018-06-18 7:43 ` Daniel Vetter [this message]
2018-06-18 8:13 ` Stefan Agner
2018-07-10 9:06 ` Stefan Agner
2018-07-10 9:11 ` Marek Vasut
2018-07-12 9:21 ` Stefan Agner
2018-07-12 13:03 ` Leonard Crestez
2018-07-12 13:14 ` Marek Vasut
2018-07-13 7:25 ` Daniel Vetter
2018-07-12 13:46 ` Stefan Agner
2018-07-12 12:15 ` Stefan Agner
2018-06-15 19:43 ` [PATCH 2/3] fbdev: mxsfb: Return ENODEV on missing display node Leonard Crestez
2018-06-15 19:43 ` [PATCH 3/3] ARM: imx_v6_v7_defconfig: Enable DRM_MXSFB Leonard Crestez
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=20180618074320.GS3438@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcofrk@gmail.com \
--cc=marek.vasut@gmail.com \
--cc=marex@denx.de \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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