public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hannes Schmelzer <hannes@schmelzer.or.at>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] board/BuR/common: support timer5 for pwm-backlight
Date: Fri, 12 Jun 2015 07:25:47 +0200	[thread overview]
Message-ID: <557A6D5B.7010308@schmelzer.or.at> (raw)
In-Reply-To: <CAPnjgZ0G5CR5LwUtzPV84WF9LB-r6UMRP49Z4GUQuhNR7wCPxA@mail.gmail.com>

Hi Simon,

board_type doesn't apply here.

The board can be used in

Device-Type A
Device-Type B
Device-Type C

all of them may have different backlights.
So it comes, that device-type A has different variants where one has 
backlight using PMIC, the other one has backlight using PWM.

For this we have an entry within the device-tree (brightdrv) on linux 
devices, and on vxworks-devices (where we don't have a device-tree) we 
have same as variable in environment.

The board_type variable is used to separate "Device-Type A, Device-Type 
B, ..."

At this time only one of my boards (brxre2, not committed yet) has this 
variable in use.

best regards,
Hannes

On 2015-06-11 22:07, Simon Glass wrote:
> Hi,
>
> On 11 June 2015 at 04:25, Hannes Schmelzer <oe5hpm@oevsv.at> wrote:
>> in future we support yet another b&r am335x based board, where Timer 5 is
>> wired to backlight-driver.
>>
>> So we introduce a new driver-type '2' to setup timer5 instead timer6.
>>
>> Signed-off-by: Hannes Schmelzer <oe5hpm@oevsv.at>
>>
> Reviewed-by: Simon Glass <sjg@chromium.org>
>
> You might consider using an enum for the board type.
>
>> ---
>>
>>   board/BuR/common/common.c | 14 +++++++++++---
>>   1 file changed, 11 insertions(+), 3 deletions(-)
>>
>> diff --git a/board/BuR/common/common.c b/board/BuR/common/common.c
>> index 7830d1a..441465c 100644
>> --- a/board/BuR/common/common.c
>> +++ b/board/BuR/common/common.c
>> @@ -64,8 +64,7 @@ void lcdbacklight(int on)
>>          unsigned int pwmfrq = getenv_ulong("ds1_pwmfreq", 10, ~0UL);
>>   #endif
>>          unsigned int tmp;
>> -
>> -       struct gptimer *const timerhw = (struct gptimer *)DM_TIMER6_BASE;
>> +       struct gptimer *timerhw;
>>
>>          if (on)
>>                  bright = bright != ~0UL ? bright : 50;
>> @@ -73,6 +72,14 @@ void lcdbacklight(int on)
>>                  bright = 0;
>>
>>          switch (driver) {
>> +       case 2:
>> +               timerhw = (struct gptimer *)DM_TIMER5_BASE;
>> +               break;
>> +       default:
>> +               timerhw = (struct gptimer *)DM_TIMER6_BASE;
>> +       }
>> +
>> +       switch (driver) {
>>          case 0: /* PMIC LED-Driver */
>>                  /* brightness level */
>>                  tps65217_reg_write(TPS65217_PROT_LEVEL_NONE,
>> @@ -83,7 +90,8 @@ void lcdbacklight(int on)
>>                                     bright != 0 ? 0x0A : 0x02,
>>                                     0xFF);
>>                  break;
>> -       case 1: /* PWM using timer6 */
>> +       case 1:
>> +       case 2: /* PWM using timer */
>>                  if (pwmfrq != ~0UL) {
>>                          timerhw->tiocp_cfg = TCFG_RESET;
>>                          udelay(10);
>> --
>> 2.1.4
>>
> Regards,
> Simon
>
>

  reply	other threads:[~2015-06-12  5:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 10:25 [U-Boot] [PATCH] board/BuR/common: support timer5 for pwm-backlight Hannes Schmelzer
2015-06-11 20:07 ` Simon Glass
2015-06-12  5:25   ` Hannes Schmelzer [this message]
2015-06-18 22:46 ` [U-Boot] " Tom Rini

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=557A6D5B.7010308@schmelzer.or.at \
    --to=hannes@schmelzer.or.at \
    --cc=u-boot@lists.denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox