From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] mmp2: add mfpr setting
Date: Tue, 26 Jan 2010 18:28:50 +0800 [thread overview]
Message-ID: <f17812d71001260228jadc2157n63c5283cbd63eb61@mail.gmail.com> (raw)
In-Reply-To: <771cded01001250303vbb38c7dp62e61b64abab89ea@mail.gmail.com>
On Mon, Jan 25, 2010 at 7:03 PM, Haojian Zhuang
<haojian.zhuang@gmail.com> wrote:
> From 3c6535a752748cf7e17683d7c37ccf66f245e714 Mon Sep 17 00:00:00 2001
> From: Haojian Zhuang <haojian.zhuang@marvell.com>
> Date: Mon, 25 Jan 2010 05:18:37 -0500
> Subject: [PATCH] mmp2: add mfpr setting
>
> Signed-off-by: Haojian Zhuang <haojian.zhuang@marvell.com>
> ---
> ?arch/arm/mach-mmp/include/mach/mfp-mmp2.h | ? ?4 ++++
> ?arch/arm/mach-mmp/mmp2.c ? ? ? ? ? ? ? ? ?| ? ?7 +++++++
> ?2 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-mmp/include/mach/mfp-mmp2.h
> b/arch/arm/mach-mmp/include/mach/mfp-mmp2.h
> index 9371510..9f9f814 100644
> --- a/arch/arm/mach-mmp/include/mach/mfp-mmp2.h
> +++ b/arch/arm/mach-mmp/include/mach/mfp-mmp2.h
> @@ -231,6 +231,10 @@
> ?/* Codec*/
> ?#define GPIO23_GPIO23 ? ? ? ? ?MFP_CFG(GPIO23, AF0)
>
> +#define GPIO101_GPIO101 ? ? ? ? ? ? ? ?MFP_CFG(GPIO101, AF0)
> +
> +/* PMIC */
> +#define PMIC_PMIC_INT ? ? ? ? ?MFP_CFG(PMIC_INT, AF0)
>
> ?#endif /* __ASM_MACH_MFP_MMP2_H */
>
> diff --git a/arch/arm/mach-mmp/mmp2.c b/arch/arm/mach-mmp/mmp2.c
> index a9ca93d..561194d 100644
> --- a/arch/arm/mach-mmp/mmp2.c
> +++ b/arch/arm/mach-mmp/mmp2.c
> @@ -28,6 +28,12 @@
>
> ?#define MFPR_VIRT_BASE (APB_VIRT_BASE + 0x1e000)
>
> +static struct mfp_addr_map mmp2_addr_map[] __initdata = {
> + ? ? ? MFP_ADDR(PMIC_INT, 0x2c4),
> +
Mmm... I'm wondering where're the MFPR addresses for other pins?
> + ? ? ? MFP_ADDR_END,
> +};
> +
> ?/* APB peripheral clocks */
> ?static APBC_CLK(uart1, MMP2_UART1, 1, 26000000);
> ?static APBC_CLK(uart2, MMP2_UART2, 1, 26000000);
> @@ -61,6 +67,7 @@ static int __init mmp2_init(void)
> ?{
> ? ? ? ?if (cpu_is_mmp2()) {
> ? ? ? ? ? ? ? ?mfp_init_base(MFPR_VIRT_BASE);
> + ? ? ? ? ? ? ? mfp_init_addr(mmp2_addr_map);
> ? ? ? ? ? ? ? ?clks_register(ARRAY_AND_SIZE(mmp2_clkregs));
> ? ? ? ?}
>
> --
> 1.5.6.5
>
next prev parent reply other threads:[~2010-01-26 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 11:03 [PATCH 2/4] mmp2: add mfpr setting Haojian Zhuang
2010-01-26 10:28 ` Eric Miao [this message]
2010-01-26 11:40 ` Haojian Zhuang
2010-01-27 12:40 ` Eric Miao
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=f17812d71001260228jadc2157n63c5283cbd63eb61@mail.gmail.com \
--to=eric.y.miao@gmail.com \
--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).