All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Helge Deller <deller@gmx.de>,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Priit Laes" <plaes@plaes.org>,
	"Dillon Min" <dillon.minfei@gmail.com>,
	"Noralf Trønnes" <noralf@tronnes.org>,
	"David Lechner" <dlechner@baylibre.com>
Subject: State of affairs with Ilitek 9341 support
Date: Fri, 8 Dec 2023 18:00:36 +0200	[thread overview]
Message-ID: <ZXM9pG-53V4S8E2H@smile.fi.intel.com> (raw)

Included authors and latest (non-white-space) contributors to the drivers
in question along with relevant mailing list and respective (active in the
area) maintainers.

I already had risen the question in times when 4th (sic!) driver for the same
hardware was about to be pulled into upstream that we have to somehow reduce
the code base and unify device properties.

So, the main question here "What is the plan and where are we now?"

I admit that fbtft case is special as it supports, in particular, platform
device (parallel interface) and also well established in the embedded world.
What about the rest?

N.B. Besides the fact that panel drivers are too OF-centric, which is bad
practice for the new kernel code in general and has to be stopped. I.o.w.
seeing of_property_*() or alike in the driver after ca. 2020 should be
immediate NAK unless it's very well justified why it may not be used on
non-OF systems.

-- 
With Best Regards,
Andy Shevchenko



WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Helge Deller <deller@gmx.de>,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>
Cc: "David Lechner" <dlechner@baylibre.com>,
	"Priit Laes" <plaes@plaes.org>,
	"Dillon Min" <dillon.minfei@gmail.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Noralf Trønnes" <noralf@tronnes.org>
Subject: State of affairs with Ilitek 9341 support
Date: Fri, 8 Dec 2023 18:00:36 +0200	[thread overview]
Message-ID: <ZXM9pG-53V4S8E2H@smile.fi.intel.com> (raw)

Included authors and latest (non-white-space) contributors to the drivers
in question along with relevant mailing list and respective (active in the
area) maintainers.

I already had risen the question in times when 4th (sic!) driver for the same
hardware was about to be pulled into upstream that we have to somehow reduce
the code base and unify device properties.

So, the main question here "What is the plan and where are we now?"

I admit that fbtft case is special as it supports, in particular, platform
device (parallel interface) and also well established in the embedded world.
What about the rest?

N.B. Besides the fact that panel drivers are too OF-centric, which is bad
practice for the new kernel code in general and has to be stopped. I.o.w.
seeing of_property_*() or alike in the driver after ca. 2020 should be
immediate NAK unless it's very well justified why it may not be used on
non-OF systems.

-- 
With Best Regards,
Andy Shevchenko



             reply	other threads:[~2023-12-08 16:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 16:00 Andy Shevchenko [this message]
2023-12-08 16:00 ` State of affairs with Ilitek 9341 support Andy Shevchenko
2023-12-08 20:18 ` Noralf Trønnes
2023-12-08 20:18   ` Noralf Trønnes
2023-12-11 13:19   ` Andy Shevchenko
2023-12-11 13:19     ` Andy Shevchenko
2023-12-11 13:40     ` Maxime Ripard
2023-12-11 13:40       ` Maxime Ripard
2023-12-23  3:00     ` Dillon Min
2023-12-23  3:00       ` Dillon Min
2024-08-13 10:59       ` Andy Shevchenko

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=ZXM9pG-53V4S8E2H@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=deller@gmx.de \
    --cc=dillon.minfei@gmail.com \
    --cc=dlechner@baylibre.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=noralf@tronnes.org \
    --cc=plaes@plaes.org \
    --cc=thomas.petazzoni@bootlin.com \
    --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.