From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] pxa255: Add UDC registers definitions
Date: Thu, 9 Aug 2012 22:34:47 +0200 [thread overview]
Message-ID: <201208092234.47683.marex@denx.de> (raw)
In-Reply-To: <1343410121-7039-1-git-send-email-luk0104@gmail.com>
Dear ?ukasz Da?ek,
> This patch starts series of patches adding support for USB support on
> PXA255 chips.
>
> Signed-off-by: ?ukasz Da?ek <luk0104@gmail.com>
> ---
> arch/arm/include/asm/arch-pxa/pxa-regs.h | 247
> ++++++++++++++++++++++++++++++ 1 files changed, 247 insertions(+), 0
> deletions(-)
>
> diff --git a/arch/arm/include/asm/arch-pxa/pxa-regs.h
> b/arch/arm/include/asm/arch-pxa/pxa-regs.h index b81b42c..114e9a2 100644
> --- a/arch/arm/include/asm/arch-pxa/pxa-regs.h
> +++ b/arch/arm/include/asm/arch-pxa/pxa-regs.h
> @@ -2498,6 +2498,253 @@ typedef void (*ExcpHndlr) (void) ;
>
> #endif /* CONFIG_CPU_PXA27X */
>
> +#if defined(CONFIG_CPU_PXA25X)
> +
> +#ifdef CONFIG_PXA25X_UDC_LINUX
> +# define UDCCR *((volatile u32 *)0x40600000)
NAK, drop this #define altogether, use writel() readl() IO accessors, see below.
> +#else
> +# define UDCCR 0x40600000
Ok ... so this is a register address, right? Can you rework this to use the
struct-based access?
aka:
struct pxa2xx_udc_regs {
uint32_t udccr;
uint32_t uicr0;
....
};
And then when used, do:
struct pxa2xx_udc_regs *udc_regs;
writel(value, &udc_regs->udccr);
etc.
[...]
btw. you'll usually get better results (and faster review) by CCing me directly,
I found your patches accidentally now.
btw2. it'd be cool if someone reworked the PXA stuff to use struct based access
altogerther ... see arch/arm/include/mach-mx28/regs*.h for some hints too.
Best regards,
next prev parent reply other threads:[~2012-08-09 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 17:28 [U-Boot] [PATCH 1/5] pxa255: Add UDC registers definitions Łukasz Dałek
2012-08-09 20:34 ` Marek Vasut [this message]
2012-08-11 10:54 ` nerwusek
2012-08-11 12:45 ` Marek Vasut
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=201208092234.47683.marex@denx.de \
--to=marex@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