From: Daniel Vetter <daniel@ffwll.ch>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: linux-fbdev@vger.kernel.org, Jani Nikula <jani.nikula@intel.com>,
Robin van der Gracht <robin@protonic.nl>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 14/14] auxdisplay: constify fb ops
Date: Fri, 29 Nov 2019 20:30:07 +0000 [thread overview]
Message-ID: <20191129203007.GV624164@phenom.ffwll.local> (raw)
In-Reply-To: <CANiq72kRGg1AZHC-pR_uKykMxmcMPM2+qbXVPVQhHrZRzu723Q@mail.gmail.com>
On Fri, Nov 29, 2019 at 09:16:42PM +0100, Miguel Ojeda wrote:
> On Fri, Nov 29, 2019 at 4:24 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> >
> > Oh, another display subsystem? Intriguing ...
> >
> > Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> It is intended for displays that are not intended as the usual/main
> display, e.g. very small LCDs :)
Well we do have very small lcd display drivers in drm, and before that in
fbdev. And you have a fbdev framebuffer driver in there, which looks a bit
misplaced ...
Afaiui you also have some even tinier lcd drivers where you don't address
pixels, but just directly upload text, and those obviously don't fit into
drm/fbdev world. But anything where you can address pixels very much does.
-Daniel
>
> Reviewed-by: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
>
> Cheers,
> Miguel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2019-11-29 20:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 10:29 [PATCH v2 00/14] video, drm, etc: constify fbops in struct fb_info Jani Nikula
2019-11-29 10:29 ` [PATCH v2 01/14] video: fb_defio: preserve user fb_ops Jani Nikula
2019-11-29 14:12 ` Noralf Trønnes
2019-11-29 15:22 ` Daniel Vetter
2019-11-29 10:29 ` [PATCH v2 02/14] drm/fb-helper: don't preserve fb_ops across deferred IO use Jani Nikula
2019-11-29 14:12 ` Noralf Trønnes
2019-11-29 10:29 ` [PATCH v2 03/14] video: smscufx: don't restore fb_mmap after deferred IO cleanup Jani Nikula
2019-11-29 10:29 ` [PATCH v2 04/14] video: udlfb: " Jani Nikula
2019-11-29 10:29 ` [PATCH v2 05/14] video: fbdev: vesafb: modify the static fb_ops directly Jani Nikula
2019-11-29 10:29 ` [PATCH v2 06/14] video: fbmem: use const pointer for fb_ops Jani Nikula
2019-11-29 15:25 ` [Intel-gfx] " Daniel Vetter
2019-11-29 10:29 ` [PATCH v2 07/14] video: omapfb: " Jani Nikula
2019-12-03 9:16 ` Jani Nikula
2019-11-29 10:29 ` [PATCH v2 08/14] video: fbdev: make fbops member of struct fb_info a const pointer Jani Nikula
2019-11-30 1:41 ` kbuild test robot
2019-11-29 10:29 ` [PATCH v2 09/14] drm: constify fb ops across all drivers Jani Nikula
2019-11-29 10:29 ` [PATCH v2 10/14] video: " Jani Nikula
2019-11-29 10:35 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` [PATCH v2 11/14] HID: picoLCD: constify fb ops Jani Nikula
2019-12-02 8:40 ` Bruno Prémont
2019-12-05 9:38 ` Jani Nikula
2019-12-08 0:07 ` Jiri Kosina
2019-11-29 10:29 ` [PATCH v2 12/14] media: constify fb ops across all drivers Jani Nikula
2019-11-29 10:35 ` [Intel-gfx] " Jani Nikula
2019-11-29 10:29 ` [PATCH v2 13/14] samples: vfio-mdev: constify fb ops Jani Nikula
2019-11-29 10:29 ` [PATCH v2 14/14] auxdisplay: " Jani Nikula
2019-11-29 15:24 ` Daniel Vetter
2019-11-29 20:16 ` Miguel Ojeda
2019-11-29 20:30 ` Daniel Vetter [this message]
2019-11-29 20:59 ` Miguel Ojeda
2019-12-02 8:08 ` robin
2019-12-02 7:37 ` robin
2019-11-29 15:40 ` [PATCH v2 00/14] video, drm, etc: constify fbops in struct fb_info Daniel Vetter
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=20191129203007.GV624164@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=robin@protonic.nl \
/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).