All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Thierry Reding
	<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: PWM and backlight devices
Date: Tue, 06 Dec 2011 12:20:47 -0600	[thread overview]
Message-ID: <4EDE5CFF.1060709@gmail.com> (raw)
In-Reply-To: <20111206150749.GA13761-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>

On 12/06/2011 09:07 AM, Thierry Reding wrote:
> Hi,
> 
> I'm working on adding support for a device which is booted from a device tree
> only. Currently this gets me to a login prompt on a serial console and the
> device is basically functional. However, the device also has a display with a
> backlight that is controlled via a PWM (supplied by the SoC). If this was a
> regular board it would be simple to implement this via the pwm-backlight
> driver.
> 
> Unfortunately, the pwm-backlight driver doesn't have device tree support yet
> and I'm not sure how to best implement it. As far as I can see, I would first
> need to have some way of representing a PWM device in the DT that I could
> reference in the pwm-backlight device node and I would need to add actual DT
> support to pwm-backlight. Implementing support for the data passed in the
> platform data should be rather straightforward, but I don't see how the
> callback functions could be represented in the DT.
> 
> For some setups it would probably be enough to just specify the used PWM, but
> other boards fiddle with some GPIOs in the callbacks and I guess that could
> be represented by adding a "gpios" property with a list of pins that need to
> be toggled for example when the backlight power is enabled/disabled.
> 
> Has anyone done something similar yet? Am I even on the right track here?
> 

I haven't seen anything. Perhaps something similar to how the gpio-keys
binding is done would work here. This could have a phandle to the pwm
device similar to gpios.

Rob

      parent reply	other threads:[~2011-12-06 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 15:07 PWM and backlight devices Thierry Reding
     [not found] ` <20111206150749.GA13761-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2011-12-06 18:20   ` Rob Herring [this message]

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=4EDE5CFF.1060709@gmail.com \
    --to=robherring2-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.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.