From: Alex Courbot <acourbot@nvidia.com> To: Thierry Reding <thierry.reding@avionic-design.de> Cc: Stephen Warren <swarren@nvidia.com>, Devicetree@theia.denx.de, Discuss <devicetree-discuss@lists.ozlabs.org>, U-Boot Mailing List <u-boot@lists.denx.de>, Jerry Van Baren <vanbaren@cideas.com>, Tom Warren <twarren@nvidia.com> Subject: Re: [PATCH v2 07/19] tegra: fdt: Add LCD definitions for Tegra Date: Thu, 12 Jul 2012 18:22:58 +0900 [thread overview] Message-ID: <4FFE9772.8010200@nvidia.com> (raw) In-Reply-To: <20120712084051.GA27022@avionic-0098.adnet.avionic-design.de> On Thu 12 Jul 2012 05:40:51 PM JST, Thierry Reding wrote: > Linux has a generic PWM backlight driver. This is currently solved by > using this in the DT: > > backlight { > compatible = "pwm-backlight"; > pwms = <&pwm 0 5000000>; > > brightness-levels = <0 4 8 16 32 64 128 255>; > default-brightness-level = <6>; > }; > > Alex Courbot (Cc'd) has been working on adding a generic way to add GPIO > and regulator support to that. I don't know exactly what the > lvds-shutdown-gpios and panel-vdd-gpios properties do. If they control > hardware connected behind the display controller I suppose they could go > into the rgb node. Thanks for bringing that back to light - the patches did not receive any feedback so far. If Simon wants to have a look, the one in the series that touches the device tree is here: https://lkml.org/lkml/2012/7/9/30 The idea is to extend pwm-backlight to support the GPIOs and regulators that may be related to the backlight, and order them into proper power sequences that were so far done by callbacks in board files. So your nvidia,pwm , nvidia,backlight-enable-gpios and nvidia,backlight-vdd-gpios properties would be moved into the backlight node and their appropriate power sequences (including any delay required by the panel specification) would be written. Actually, the power sequences code is independent from the backlight and could be used in other areas as well. Looking at your panel node, which also uses gpios and has a timings table, it might make sense to use them there as well. > The panel alternative that you propose sounds interesting as well. Maybe > the panel should itself contain either a phandle or a subnode for the > backlight and collect the properties that you listed above. The panel and backlight should definitely be connected in some way. But since they are controlled independantly, I'm not sure about the implications of having them represented hierarchically in the DT. Alex. ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------
WARNING: multiple messages have this Message-ID (diff)
From: Alex Courbot <acourbot@nvidia.com> To: u-boot@lists.denx.de Subject: [U-Boot] [PATCH v2 07/19] tegra: fdt: Add LCD definitions for Tegra Date: Thu, 12 Jul 2012 18:22:58 +0900 [thread overview] Message-ID: <4FFE9772.8010200@nvidia.com> (raw) In-Reply-To: <20120712084051.GA27022@avionic-0098.adnet.avionic-design.de> On Thu 12 Jul 2012 05:40:51 PM JST, Thierry Reding wrote: > Linux has a generic PWM backlight driver. This is currently solved by > using this in the DT: > > backlight { > compatible = "pwm-backlight"; > pwms = <&pwm 0 5000000>; > > brightness-levels = <0 4 8 16 32 64 128 255>; > default-brightness-level = <6>; > }; > > Alex Courbot (Cc'd) has been working on adding a generic way to add GPIO > and regulator support to that. I don't know exactly what the > lvds-shutdown-gpios and panel-vdd-gpios properties do. If they control > hardware connected behind the display controller I suppose they could go > into the rgb node. Thanks for bringing that back to light - the patches did not receive any feedback so far. If Simon wants to have a look, the one in the series that touches the device tree is here: https://lkml.org/lkml/2012/7/9/30 The idea is to extend pwm-backlight to support the GPIOs and regulators that may be related to the backlight, and order them into proper power sequences that were so far done by callbacks in board files. So your nvidia,pwm , nvidia,backlight-enable-gpios and nvidia,backlight-vdd-gpios properties would be moved into the backlight node and their appropriate power sequences (including any delay required by the panel specification) would be written. Actually, the power sequences code is independent from the backlight and could be used in other areas as well. Looking at your panel node, which also uses gpios and has a timings table, it might make sense to use them there as well. > The panel alternative that you propose sounds interesting as well. Maybe > the panel should itself contain either a phandle or a subnode for the > backlight and collect the properties that you listed above. The panel and backlight should definitely be connected in some way. But since they are controlled independantly, I'm not sure about the implications of having them represented hierarchically in the DT. Alex. ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------
next prev parent reply other threads:[~2012-07-12 9:22 UTC|newest] Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-13 16:19 [U-Boot] [PATCH v2 0/19] tegra: Add display driver and LCD support for Seaboard Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 01/19] Add gpio_request() to asm-generic header Simon Glass 2012-09-21 19:30 ` Anatolij Gustschin 2012-09-27 20:58 ` Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 05/19] tegra: Use const for pinmux_config_pingroup/table() Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 06/19] tegra: Add display support to funcmux Simon Glass 2012-06-14 23:24 ` Stephen Warren 2012-07-11 3:48 ` Simon Glass 2012-06-13 16:19 ` [PATCH v2 07/19] tegra: fdt: Add LCD definitions for Tegra Simon Glass 2012-06-13 16:19 ` [U-Boot] " Simon Glass 2012-06-14 23:32 ` Stephen Warren 2012-06-14 23:32 ` [U-Boot] " Stephen Warren 2012-07-11 4:44 ` Simon Glass 2012-07-11 4:44 ` [U-Boot] " Simon Glass 2012-07-11 5:48 ` Thierry Reding 2012-07-11 5:48 ` [U-Boot] " Thierry Reding 2012-07-12 8:21 ` Simon Glass 2012-07-12 8:21 ` [U-Boot] " Simon Glass 2012-07-12 8:40 ` Thierry Reding 2012-07-12 8:40 ` [U-Boot] " Thierry Reding 2012-07-12 9:22 ` Alex Courbot [this message] 2012-07-12 9:22 ` Alex Courbot 2012-06-13 16:19 ` [U-Boot] [PATCH v2 08/19] tegra: Add support for PWFM Simon Glass 2012-06-14 23:35 ` Stephen Warren 2012-07-11 4:45 ` Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 09/19] tegra: Add SOC support for display/lcd Simon Glass 2012-06-14 23:39 ` Stephen Warren [not found] ` <CAPnjgZ2bqPx+dHD9m+NuFrAbBeP1PQxHokLMwvD1-3OnC6ZHtg@mail.gmail.com> 2012-07-11 5:12 ` Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 10/19] tegra: Add LCD driver Simon Glass 2012-06-14 23:45 ` Stephen Warren 2012-07-11 4:56 ` Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 11/19] tegra: Add LCD support to Nvidia boards Simon Glass 2012-06-14 23:47 ` Stephen Warren 2012-07-11 4:58 ` Simon Glass 2012-07-23 20:25 ` Stephen Warren 2012-09-27 19:15 ` Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 12/19] arm: Add control over cachability of memory regions Simon Glass 2012-06-14 23:49 ` Stephen Warren 2012-07-11 5:01 ` Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 13/19] lcd: Add CONFIG_LCD_ALIGNMENT to select frame buffer alignment Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 14/19] lcd: Add support for flushing LCD fb from dcache after update Simon Glass 2012-06-14 23:51 ` Stephen Warren 2012-07-11 5:06 ` Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 15/19] tegra: Align LCD frame buffer to section boundary Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 16/19] tegra: Support control of cache settings for LCD Simon Glass [not found] ` <1339604395-6621-1-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> 2012-06-13 16:19 ` [PATCH v2 02/19] fdt: Add debugging to fdtdec_get_int/addr() Simon Glass 2012-06-13 16:19 ` [U-Boot] " Simon Glass 2012-09-21 19:39 ` Anatolij Gustschin 2012-09-21 19:56 ` Anatolij Gustschin 2012-06-13 16:19 ` [PATCH v2 03/19] fdt: Add function to look up a phandle's register address Simon Glass 2012-06-13 16:19 ` [U-Boot] " Simon Glass 2012-06-14 23:17 ` Stephen Warren 2012-06-14 23:17 ` [U-Boot] " Stephen Warren 2012-07-11 5:10 ` Simon Glass 2012-07-11 5:10 ` [U-Boot] " Simon Glass 2012-06-13 16:19 ` [PATCH v2 04/19] fdt: Add header guard to fdtdec.h Simon Glass 2012-06-13 16:19 ` [U-Boot] " Simon Glass 2012-06-13 16:19 ` [PATCH v2 17/19] tegra: fdt: Add LCD definitions for Seaboard Simon Glass 2012-06-13 16:19 ` [U-Boot] " Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 18/19] lcd: Add CONSOLE_SCROLL_LINES option to speed console Simon Glass 2012-06-13 16:19 ` [U-Boot] [PATCH v2 19/19] tegra: Enable display/lcd support on Seaboard Simon Glass 2012-06-13 22:57 ` [U-Boot] [PATCH v2 0/19] tegra: Add display driver and LCD support for Seaboard Stephen Warren 2012-06-13 23:03 ` Stephen Warren 2012-06-13 23:09 ` Stephen Warren 2012-06-25 21:03 ` Tom Warren 2012-06-27 5:11 ` Simon Glass 2012-07-11 10:04 ` Simon Glass
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=4FFE9772.8010200@nvidia.com \ --to=acourbot@nvidia.com \ --cc=Devicetree@theia.denx.de \ --cc=devicetree-discuss@lists.ozlabs.org \ --cc=swarren@nvidia.com \ --cc=thierry.reding@avionic-design.de \ --cc=twarren@nvidia.com \ --cc=u-boot@lists.denx.de \ --cc=vanbaren@cideas.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: linkBe 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.