From: Sam Ravnborg <sam@ravnborg.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Boris Brezillon <boris.brezillon@bootlin.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: backlight - chicken and egg challenge
Date: Sun, 9 Sep 2018 00:38:24 +0200 [thread overview]
Message-ID: <20180908223824.GA7401@ravnborg.org> (raw)
In-Reply-To: <CAKMK7uFt1DiqNb5eO3c2n5Lh3z5206Ykn42FNd1vMMvNpbFV=A@mail.gmail.com>
> >
> > So the open question is how to fix this dependency challenge?
> >
> > 1) Drop the generic backlight driver and implement all pwm/backlight
> > handling in the driver.
> > 2) Re-introduce the MFD driver.
> > 3) ?
> >
> > Any good ideas?
>
> component.c should be able to cope. The driver that matches for the
> physical/platform device register the pwm thing, plus a component (for
> the drm driver, you can start with initializing the drm_device
> already, except for the panel). The panel registers the other
> component. the component master then does the final step of
> registering the overall drm_device.
>
> Should all work, only bit you might need is a bit of
> drm_panel/component.c integration. Iirc there's been discussions about
> that, but no idea where they are stuck.
Sound reasonable, I will try to look into this.
If anyone have pointers to the drm_panel/component.c integration
discussions I expect this would be a good help.
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-08 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 20:17 backlight - chicken and egg challenge Sam Ravnborg
2018-09-08 21:23 ` Daniel Vetter
2018-09-08 22:38 ` Sam Ravnborg [this message]
2018-09-10 7:27 ` Boris Brezillon
2018-09-11 12:48 ` Liviu Dudau
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=20180908223824.GA7401@ravnborg.org \
--to=sam@ravnborg.org \
--cc=boris.brezillon@bootlin.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
/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.