From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/2] ARM: mx5: dynamically allocate pwm devices
Date: Wed, 1 Dec 2010 08:24:16 +0100 [thread overview]
Message-ID: <20101201072416.GB32355@pengutronix.de> (raw)
In-Reply-To: <1291156869-4941-1-git-send-email-festevam@gmail.com>
On Tue, Nov 30, 2010 at 08:41:08PM -0200, Fabio Estevam wrote:
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> arch/arm/plat-mxc/devices/platform-mxc_pwm.c | 9 +++++++++
> 1 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/plat-mxc/devices/platform-mxc_pwm.c b/arch/arm/plat-mxc/devices/platform-mxc_pwm.c
> index 3d8ebdb..a5e1581 100644
> --- a/arch/arm/plat-mxc/devices/platform-mxc_pwm.c
> +++ b/arch/arm/plat-mxc/devices/platform-mxc_pwm.c
> @@ -40,6 +40,15 @@ const struct imx_mxc_pwm_data imx27_mxc_pwm_data __initconst =
> imx_mxc_pwm_data_entry_single(MX27, 0, , SZ_4K);
> #endif /* ifdef CONFIG_SOC_IMX27 */
>
> +#ifdef CONFIG_SOC_IMX51
> +const struct imx_mxc_pwm_data imx51_mxc_pwm_data[] __initconst = {
> +#define imx51_mxc_pwm_data_entry(_id, _hwid) \
> + imx_mxc_pwm_data_entry(MX51, _id, _hwid, SZ_16K)
> + imx51_mxc_pwm_data_entry(0, 1),
> + imx51_mxc_pwm_data_entry(1, 2),
> +};
> +#endif /* ifdef CONFIG_SOC_IMX51 */
> +
Does this compile? I guess you need to rename MX51_MXC_INT_PWM1 and
MX51_MXC_INT_PWM2.
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2010-12-01 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 22:41 [PATCH v5 1/2] ARM: mx5: dynamically allocate pwm devices Fabio Estevam
2010-11-30 22:41 ` [PATCH v5 2/2] ARM: mx5: dynamically allocate imx-keypad devices Fabio Estevam
2010-12-01 7:24 ` Uwe Kleine-König [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=20101201072416.GB32355@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).