From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Aurélien <aurelien.intel@ap2c.com>,
"Hans de Goede" <hdegoede@redhat.com>, Lyude <lyude@redhat.com>,
dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] Developing a new backlight driver for specific OLED screen
Date: Fri, 9 Sep 2022 05:50:40 -0400 [thread overview]
Message-ID: <YxsMcH37rRkt0cfj@intel.com> (raw)
In-Reply-To: <183219aab00.2890.be34037ad6564a4fe81285fd91a8f407@ap2c.com>
On Fri, Sep 09, 2022 at 11:35:28AM +0200, Aurélien wrote:
> Hi,
> I hope this mailing-mist is the right place for this question.
+ dri-devel mailing list that looks more appropriated.
+ Hans and Lyude who were recently working to standardize some of the
backlight stuff.
> I would like to develop a new driver in order to manage backlight for a
> specific OLED display (Samsung one). For that propose I need to use the
> dpcd aux read and write functions.
> Since this driver is independent film the i915 driver I would like to
> develop an indémependant driver.
> So my question is: how can I use the i915 API (dpcd aux communications)
> outside from the driver and register the backlight sys entries like the
> i915 does (in order to have all the softwares which plays with the
> backlight working without modifying them) ?
I don't believe you want to use the i915 API, but move the common functions
to the drm subsystem itself and then reuse as a drm device.
> Many thanks for your answers
> --
> Aurélien
next prev parent reply other threads:[~2022-09-09 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 9:35 [Intel-gfx] Developing a new backlight driver for specific OLED screen Aurélien
2022-09-09 9:50 ` Rodrigo Vivi [this message]
2022-09-09 15:26 ` Jani Nikula
2022-09-09 15:49 ` Aurélien
2022-09-09 18:20 ` Lyude Paul
2022-09-12 8:44 ` Jani Nikula
2022-10-28 15:53 ` Aurélien
2022-10-31 8:40 ` Jani Nikula
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=YxsMcH37rRkt0cfj@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=aurelien.intel@ap2c.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lyude@redhat.com \
/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.