From: Javier Martinez Canillas <javierm@redhat.com>
To: Simon Ser <contact@emersion.fr>, Sam Ravnborg <sam@ravnborg.org>
Cc: "Noralf Trønnes" <noralf@tronnes.org>,
linux-fbdev@vger.kernel.org, "David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Emil Velikov" <emil.l.velikov@gmail.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Maxime Ripard" <maxime@cerno.tech>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH 1/4] drm: Add I2C connector type
Date: Wed, 2 Feb 2022 09:46:01 +0100 [thread overview]
Message-ID: <570d4384-b838-2bf6-1ff5-f8956ba7cee5@redhat.com> (raw)
In-Reply-To: <0yOiGD-56rTdV--oDietLeMO46Z8iFNnCNVVRg3Yh9D13AghGCYm5aP67SoswHY7Ye3vc3UEKzgtI02-F6vJ4b5xGLlE5yg6n2HznaWzYvg=@emersion.fr>
On 2/1/22 23:29, Simon Ser wrote:
> On Tuesday, February 1st, 2022 at 21:57, Sam Ravnborg <sam@ravnborg.org> wrote:
>
>> As I wrote in another part of this thread(s) - typing the patch is easy.
>> But I do not understand the userspace implications so I need someone
>> else to say go.
>
> User-space shouldn't really use the connector for anything except making it
> easier for the user to understand where to plug the display cable. I think a
> generic "panel" connector type makes sense.
>
I'll drop this patch from the series. I didn't have all the context and thought
that was an opportunity to add an I2C type, since there was a SPI type already.
But seems to be more controversial than I expected and shouldn't really matter
for a tiny driver like this. I will just go ahead and use the Unknown type.
Best regards,
--
Javier Martinez Canillas
Linux Engineering
Red Hat
WARNING: multiple messages have this Message-ID (diff)
From: Javier Martinez Canillas <javierm@redhat.com>
To: Simon Ser <contact@emersion.fr>, Sam Ravnborg <sam@ravnborg.org>
Cc: linux-fbdev@vger.kernel.org, "David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Emil Velikov" <emil.l.velikov@gmail.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Noralf Trønnes" <noralf@tronnes.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Maxime Ripard" <maxime@cerno.tech>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH 1/4] drm: Add I2C connector type
Date: Wed, 2 Feb 2022 09:46:01 +0100 [thread overview]
Message-ID: <570d4384-b838-2bf6-1ff5-f8956ba7cee5@redhat.com> (raw)
In-Reply-To: <0yOiGD-56rTdV--oDietLeMO46Z8iFNnCNVVRg3Yh9D13AghGCYm5aP67SoswHY7Ye3vc3UEKzgtI02-F6vJ4b5xGLlE5yg6n2HznaWzYvg=@emersion.fr>
On 2/1/22 23:29, Simon Ser wrote:
> On Tuesday, February 1st, 2022 at 21:57, Sam Ravnborg <sam@ravnborg.org> wrote:
>
>> As I wrote in another part of this thread(s) - typing the patch is easy.
>> But I do not understand the userspace implications so I need someone
>> else to say go.
>
> User-space shouldn't really use the connector for anything except making it
> easier for the user to understand where to plug the display cable. I think a
> generic "panel" connector type makes sense.
>
I'll drop this patch from the series. I didn't have all the context and thought
that was an opportunity to add an I2C type, since there was a SPI type already.
But seems to be more controversial than I expected and shouldn't really matter
for a tiny driver like this. I will just go ahead and use the Unknown type.
Best regards,
--
Javier Martinez Canillas
Linux Engineering
Red Hat
next prev parent reply other threads:[~2022-02-02 8:46 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 20:12 [PATCH 0/4] drm/tiny: Add driver for Solomon SSD1307 OLED displays Javier Martinez Canillas
2022-01-31 20:12 ` Javier Martinez Canillas
2022-01-31 20:12 ` [PATCH 1/4] drm: Add I2C connector type Javier Martinez Canillas
2022-01-31 20:12 ` Javier Martinez Canillas
2022-01-31 20:52 ` Sam Ravnborg
2022-01-31 23:26 ` Javier Martinez Canillas
2022-01-31 23:26 ` Javier Martinez Canillas
2022-02-01 12:58 ` Noralf Trønnes
2022-02-01 12:58 ` Noralf Trønnes
2022-02-01 13:06 ` Javier Martinez Canillas
2022-02-01 13:20 ` Noralf Trønnes
2022-02-01 13:55 ` Javier Martinez Canillas
2022-02-01 13:38 ` Simon Ser
2022-02-01 13:38 ` Simon Ser
2022-02-01 14:20 ` Noralf Trønnes
2022-02-01 14:20 ` Noralf Trønnes
2022-02-01 20:57 ` Sam Ravnborg
2022-02-01 22:29 ` Simon Ser
2022-02-01 22:29 ` Simon Ser
2022-02-02 8:46 ` Javier Martinez Canillas [this message]
2022-02-02 8:46 ` Javier Martinez Canillas
2022-02-02 9:14 ` Thomas Zimmermann
2022-02-02 9:14 ` Thomas Zimmermann
2022-02-02 9:45 ` Noralf Trønnes
2022-02-02 9:45 ` Noralf Trønnes
2022-02-02 15:04 ` Pekka Paalanen
2022-02-02 15:04 ` Pekka Paalanen
2022-02-02 16:00 ` Noralf Trønnes
2022-02-02 16:00 ` Noralf Trønnes
2022-01-31 20:12 ` [PATCH 2/4] drm/format-helper: Add drm_fb_gray8_to_mono_reversed() Javier Martinez Canillas
2022-01-31 20:12 ` Javier Martinez Canillas
2022-02-01 9:59 ` Thomas Zimmermann
2022-02-01 9:59 ` Thomas Zimmermann
2022-02-01 11:13 ` Pekka Paalanen
2022-02-01 11:13 ` Pekka Paalanen
2022-02-01 11:48 ` Javier Martinez Canillas
2022-02-01 11:48 ` Javier Martinez Canillas
2022-03-14 13:40 ` Geert Uytterhoeven
2022-03-14 13:40 ` Geert Uytterhoeven
2022-03-14 14:07 ` Javier Martinez Canillas
2022-03-14 14:07 ` Javier Martinez Canillas
2022-01-31 20:36 ` [PATCH 0/4] drm/tiny: Add driver for Solomon SSD1307 OLED displays Simon Ser
2022-01-31 20:36 ` Simon Ser
2022-01-31 20:39 ` Simon Ser
2022-01-31 20:39 ` Simon Ser
2022-01-31 23:21 ` Javier Martinez Canillas
2022-01-31 23:21 ` Javier Martinez Canillas
2022-02-01 8:26 ` Geert Uytterhoeven
2022-02-01 8:26 ` Geert Uytterhoeven
2022-02-01 8:34 ` Simon Ser
2022-02-01 8:34 ` Simon Ser
2022-02-01 8:36 ` Geert Uytterhoeven
2022-02-01 8:36 ` Geert Uytterhoeven
2022-02-01 10:08 ` Thomas Zimmermann
2022-02-01 10:08 ` Thomas Zimmermann
2022-02-01 10:11 ` Simon Ser
2022-02-01 10:11 ` Simon Ser
2022-02-01 10:17 ` Thomas Zimmermann
2022-02-01 10:17 ` Thomas Zimmermann
2022-02-01 8:38 ` Daniel Vetter
2022-02-01 8:38 ` Daniel Vetter
2022-02-01 9:49 ` Javier Martinez Canillas
2022-02-01 9:49 ` Javier Martinez Canillas
2022-02-01 10:42 ` Pekka Paalanen
2022-02-01 10:42 ` Pekka Paalanen
2022-02-01 11:07 ` Geert Uytterhoeven
2022-02-01 11:07 ` Geert Uytterhoeven
2022-02-02 9:19 ` Pekka Paalanen
2022-02-02 9:19 ` Pekka Paalanen
2022-02-02 10:55 ` Geert Uytterhoeven
2022-02-02 10:55 ` Geert Uytterhoeven
2022-01-31 20:56 ` Sam Ravnborg
2022-01-31 23:37 ` Javier Martinez Canillas
2022-01-31 23:37 ` Javier Martinez Canillas
2022-02-01 9:37 ` Andy Shevchenko
2022-02-01 9:37 ` Andy Shevchenko
2022-02-01 11:31 ` Javier Martinez Canillas
2022-02-01 11:31 ` Javier Martinez Canillas
2022-02-01 11:38 ` Geert Uytterhoeven
2022-02-01 11:38 ` Geert Uytterhoeven
2022-02-01 13:09 ` Javier Martinez Canillas
2022-02-01 13:09 ` Javier Martinez Canillas
2022-02-01 14:14 ` Geert Uytterhoeven
2022-02-01 14:14 ` Geert Uytterhoeven
2022-02-01 15:03 ` Javier Martinez Canillas
2022-02-01 15:03 ` Javier Martinez Canillas
2022-02-01 20:40 ` Sam Ravnborg
2022-02-01 20:40 ` Sam Ravnborg
2022-02-02 8:38 ` Javier Martinez Canillas
2022-02-02 8:38 ` Javier Martinez Canillas
2022-02-02 11:06 ` Andy Shevchenko
2022-02-02 11:06 ` Andy Shevchenko
2022-02-02 11:39 ` Javier Martinez Canillas
2022-02-02 11:39 ` Javier Martinez Canillas
2022-02-02 11:50 ` Andy Shevchenko
2022-02-02 11:50 ` Andy Shevchenko
2022-02-02 11:54 ` Javier Martinez Canillas
2022-02-02 11:54 ` Javier Martinez Canillas
2022-02-02 12:21 ` Andy Shevchenko
2022-02-02 12:21 ` Andy Shevchenko
2022-02-01 8:43 ` Geert Uytterhoeven
2022-02-01 8:43 ` Geert Uytterhoeven
2022-02-01 9:27 ` Simon Ser
2022-02-01 9:27 ` Simon Ser
2022-02-01 10:36 ` Javier Martinez Canillas
2022-02-01 10:36 ` 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=570d4384-b838-2bf6-1ff5-f8956ba7cee5@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=andriy.shevchenko@linux.intel.com \
--cc=contact@emersion.fr \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--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 \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.