From: leonard.crestez@nxp.com (Leonard Crestez)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] drm: mxsfb: Change driver.name to mxsfb-drm
Date: Fri, 15 Jun 2018 20:58:06 +0000 [thread overview]
Message-ID: <07be6d9a85b6be655fc2b084be81d8bf9715b57a.camel@nxp.com> (raw)
In-Reply-To: <CAOMZO5B8i0gN+rCq-yPrd112NkwJWTxYCtsLVeLhD1JLRuX6EQ@mail.gmail.com>
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
> >
> > Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
>
> Stefan sent the same patch a few days ago:
> http://www.spinics.net/lists/dri-devel/msg179489.html
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.
The old driver could be removed later, after all users are converted.
--
Regards,
Leonard
next prev parent reply other threads:[~2018-06-15 20:58 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 [this message]
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
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=07be6d9a85b6be655fc2b084be81d8bf9715b57a.camel@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).