From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: pxa: hx4700: Initialize DS1WM clock_rate
Date: Sat, 28 Apr 2012 18:36:04 +0100 [thread overview]
Message-ID: <20120428173604.GC27792@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1335610789.79238.YahooMailClassic@web29018.mail.ird.yahoo.com>
I don't know who's intending to take this, but I'd have thought Haojian
would have...
On Sat, Apr 28, 2012 at 11:59:49AM +0100, Paul Parsons wrote:
> The asic3 driver now sets the DS1WM clock_rate from the newly added
> asic3_platform_data clock_rate field.
>
> This patch initializes the asic3_platform_data clock_rate field on the
> hx4700 platform.
>
> Signed-off-by: Paul Parsons <lost.distance@yahoo.com>
> Cc: Philipp Zabel <philipp.zabel@gmail.com>
> ---
> arch/arm/mach-pxa/hx4700.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-pxa/hx4700.c b/arch/arm/mach-pxa/hx4700.c
> index 00a00a9..6bd692d 100644
> --- a/arch/arm/mach-pxa/hx4700.c
> +++ b/arch/arm/mach-pxa/hx4700.c
> @@ -295,6 +295,7 @@ static struct asic3_platform_data asic3_platform_data = {
> .gpio_config_num = ARRAY_SIZE(asic3_gpio_config),
> .irq_base = IRQ_BOARD_START,
> .gpio_base = HX4700_ASIC3_GPIO_BASE,
> + .clock_rate = 4000000,
> .leds = asic3_leds,
> };
>
> --
> 1.7.3.4
>
next prev parent reply other threads:[~2012-04-28 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 10:59 [PATCH RESEND] ARM: pxa: hx4700: Initialize DS1WM clock_rate Paul Parsons
2012-04-28 17:36 ` Russell King - ARM Linux [this message]
2012-05-02 2:03 ` Haojian Zhuang
-- strict thread matches above, loose matches on Subject: below --
2012-05-02 15:49 Paul Parsons
[not found] <E1SPbo0-0004MU-OV@merlin.infradead.org>
2012-05-03 1:48 ` Haojian Zhuang
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=20120428173604.GC27792@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).