From: Javier Martinez Canillas <javierm@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Sam Ravnborg" <sam@ravnborg.org>,
linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org,
"Noralf Trønnes" <noralf@tronnes.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Maxime Ripard" <maxime@cerno.tech>
Subject: Re: [PATCH 3/4] drm/tiny: Add driver for Solomon SSD1307 OLED displays
Date: Tue, 1 Feb 2022 16:10:49 +0100 [thread overview]
Message-ID: <b4fe0d36-c4ef-6f7e-e47d-f98f6055ea92@redhat.com> (raw)
In-Reply-To: <Yfk9fuazUSgI6C9n@smile.fi.intel.com>
On 2/1/22 15:02, Andy Shevchenko wrote:
> On Tue, Feb 01, 2022 at 12:45:53PM +0100, Javier Martinez Canillas wrote:
>> On 2/1/22 10:44, Andy Shevchenko wrote:
>>> On Tue, Feb 01, 2022 at 01:14:22AM +0100, Javier Martinez Canillas wrote:
>
> ...
>
>>> The problem with no backward compatibility means that removal of old driver
>>> makes users unhappy since DT is kinda ABI and we do not break it.
>>>
>>
>> I think that's the crux of the issue. Do we want people to update their
>> kernel but using their existing Device Tree and be able to switch to the
>> DRM driver ?
>>
>> My take is that we should and that's why I kept the backward compatibility.
>>
>> Maybe we could do that in the meantime and at some point introduce new DT
>> bindings (with a different compatible string) that would use the latest
>> and greatest conventions in DT ? That seems to be a good compromise.
>
> I have over-read in this discussion that current binding is not fully
> correct from hw perspective. If it's indeed the case (and I believe it's),
> then probably we should come with brand new driver with ssd130x name and
> incompatible bindingas (*).
>
> Otherwise in this driver we continue to be incorrect in them.
>
See the comment from Geert. I believe we should use the existing binding.
> *) But even though I think it would be good if you take the old one under your
> maintainership.
>
Sure, now that I got familiar with the ssd130x devices, I'll be happy to
help with the ssd1307fb driver maintainership.
Best regards,
--
Javier Martinez Canillas
Linux Engineering
Red Hat
next prev parent reply other threads:[~2022-02-01 15:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 20:29 [PATCH 3/4] drm/tiny: Add driver for Solomon SSD1307 OLED displays Javier Martinez Canillas
2022-02-01 9:33 ` Thomas Zimmermann
2022-02-01 9:48 ` Andy Shevchenko
2022-02-01 13:01 ` Javier Martinez Canillas
2022-02-01 14:05 ` Geert Uytterhoeven
2022-02-01 14:36 ` Javier Martinez Canillas
2022-02-02 8:23 ` Thomas Zimmermann
2022-02-02 8:29 ` Javier Martinez Canillas
[not found] ` <YfhVBtv1UIA7bJja@ravnborg.org>
2022-02-01 0:14 ` Javier Martinez Canillas
2022-02-01 9:44 ` Andy Shevchenko
2022-02-01 11:45 ` Javier Martinez Canillas
2022-02-01 14:02 ` Andy Shevchenko
2022-02-01 15:10 ` Javier Martinez Canillas [this message]
2022-02-01 9:41 ` Andy Shevchenko
2022-02-01 11:40 ` Javier Martinez Canillas
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=b4fe0d36-c4ef-6f7e-e47d-f98f6055ea92@redhat.com \
--to=javierm@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=noralf@tronnes.org \
--cc=sam@ravnborg.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).