All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	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, 09 Sep 2022 18:26:36 +0300	[thread overview]
Message-ID: <878rms7emr.fsf@intel.com> (raw)
In-Reply-To: <YxsMcH37rRkt0cfj@intel.com>

On Fri, 09 Sep 2022, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> 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.

Aurélien, are you aware of drivers/gpu/drm/display/drm_dp_helper.c and
all the functions around struct dp_aux_backlight and struct
drm_edp_backlight_info?

Also see drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c.

Does the display use some proprietary, non-VESA DPCD registers? There's
already some of that in i915 for Intel proprietary interfaces.


BR,
Jani.



>
>>    Many thanks for your answers
>>    --
>>    Aurélien

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-09-09 15:26 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
2022-09-09 15:26   ` Jani Nikula [this message]
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=878rms7emr.fsf@intel.com \
    --to=jani.nikula@linux.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 \
    --cc=rodrigo.vivi@intel.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.