public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/5] i.MX6: define struct pwm_regs and PWMCR_* defines
Date: Tue, 15 Jul 2014 10:52:52 +0200	[thread overview]
Message-ID: <53C4EBE4.80602@denx.de> (raw)
In-Reply-To: <53C4E272.8010409@denx.de>

Hello Stefano,

Am 15.07.2014 10:12, schrieb Stefano Babic:
> Hi Heiko,
>
> On 12/07/2014 06:10, Heiko Schocher wrote:
>> add defines for pwm modul found on imx6.
>>
>> Signed-off-by: Heiko Schocher<hs@denx.de>
>> Cc: Stefano Babic<sbabic@denx.de>
>>
>> ---
>> - changes for v2:
>>    - new
>>
>>   arch/arm/include/asm/arch-mx6/imx-regs.h | 16 ++++++++++++++++
>>   1 file changed, 16 insertions(+)
>>
>> diff --git a/arch/arm/include/asm/arch-mx6/imx-regs.h b/arch/arm/include/asm/arch-mx6/imx-regs.h
>> index 7193118..2135051 100644
>> --- a/arch/arm/include/asm/arch-mx6/imx-regs.h
>> +++ b/arch/arm/include/asm/arch-mx6/imx-regs.h
>> @@ -669,5 +669,21 @@ struct wdog_regs {
>>   	u16	wmcr;	/* Miscellaneous Control */
>>   };
>>
>> +#define PWMCR_PRESCALER(x)	(((x - 1)&  0xFFF)<<  4)
>> +#define PWMCR_DOZEEN		(1<<  24)
>> +#define PWMCR_WAITEN		(1<<  23)
>> +#define PWMCR_DBGEN		(1<<  22)
>> +#define PWMCR_CLKSRC_IPG_HIGH	(2<<  16)
>> +#define PWMCR_CLKSRC_IPG	(1<<  16)
>> +#define PWMCR_EN		(1<<  0)
>> +
>> +struct pwm_regs {
>> +	u32	cr;
>> +	u32	sr;
>> +	u32	ir;
>> +	u32	sar;
>> +	u32	pr;
>> +	u32	cnr;
>> +};
>>   #endif /* __ASSEMBLER__*/
>>   #endif /* __ASM_ARCH_MX6_IMX_REGS_H__ */
>>
>
> I see. What do you mind to add a little effort and move the setup of the
> PWM from the aristaneos board to a PWM driver ? I see there is not (yet)
> such a driver, but why not ?

Yes, I can do that ... Hmm, where do you think is a good place for this
driver?

> What we need are only three simple functions exactly as in Linux kernel:
> pwm_enable() pwm_disable(), pwm_config(duty, period)
>
> This becomes more general and can be reused by other i.MX boards.

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2014-07-15  8:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12  4:10 [U-Boot] [PATCH v2 0/5] arm, imx6: add aristainetos board support Heiko Schocher
2014-07-12  4:10 ` [U-Boot] [PATCH v2 1/5] spi, spi_mxc: do not hang in spi_xchg_single Heiko Schocher
2014-07-12 12:54   ` Jagan Teki
2014-07-14  7:26     ` Heiko Schocher
2014-07-14  8:01       ` Jagan Teki
2014-07-14  8:20         ` Heiko Schocher
2014-07-12  4:10 ` [U-Boot] [PATCH v2 2/5] imx6: add gpr2 usb_otg_id iomux select control define Heiko Schocher
2014-07-15  8:07   ` Stefano Babic
2014-07-12  4:10 ` [U-Boot] [PATCH v2 3/5] i.MX6: define struct pwm_regs and PWMCR_* defines Heiko Schocher
2014-07-15  8:12   ` Stefano Babic
2014-07-15  8:52     ` Heiko Schocher [this message]
2014-07-15  8:58       ` Stefano Babic
2014-07-15  9:27         ` Heiko Schocher
2014-07-15 10:40           ` Stefano Babic
2014-07-12  4:10 ` [U-Boot] [PATCH v2 4/5] i.MX6: add enable_spi_clk() Heiko Schocher
2014-07-14 17:13   ` Jagan Teki
2014-07-12  4:10 ` [U-Boot] [PATCH v2 5/5] arm, imx6: add aristainetos board Heiko Schocher
2014-07-15  8:31   ` Stefano Babic

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=53C4EBE4.80602@denx.de \
    --to=hs@denx.de \
    --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