public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] sunxi: Support SID e-fuses on A83T and H3
Date: Wed, 16 Mar 2016 14:10:23 +0100	[thread overview]
Message-ID: <56E95B3F.6030201@redhat.com> (raw)
In-Reply-To: <1453883684-2447-1-git-send-email-wens@csie.org>

Hi,

On 27-01-16 09:34, Chen-Yu Tsai wrote:
> On the A83T and H3, the SID block is at a different address.
> Furthurmore, the e-fuses are at an offset of 0x200 within the
> hardware's address space.
>
> Signed-off-by: Chen-Yu Tsai <wens@csie.org>

Thanks, applied to my tree and this will go out with the
next pull-req.

Regards,

Hans


> ---
>   arch/arm/include/asm/arch-sunxi/cpu_sun4i.h | 7 +++++++
>   1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm/include/asm/arch-sunxi/cpu_sun4i.h b/arch/arm/include/asm/arch-sunxi/cpu_sun4i.h
> index 0cdefdc..f797649 100644
> --- a/arch/arm/include/asm/arch-sunxi/cpu_sun4i.h
> +++ b/arch/arm/include/asm/arch-sunxi/cpu_sun4i.h
> @@ -74,7 +74,14 @@
>   #define SUNXI_AD_DA_BASE		0x01c22c00
>   #define SUNXI_KEYPAD_BASE		0x01c23000
>   #define SUNXI_TZPC_BASE			0x01c23400
> +
> +#if defined(CONFIG_MACH_SUN8I_A83T) || defined(CONFIG_MACH_SUN8I_H3)
> +/* SID address space starts at 0x01c1400, but e-fuse is at offset 0x200 */
> +#define SUNXI_SID_BASE			0x01c14200
> +#else
>   #define SUNXI_SID_BASE			0x01c23800
> +#endif
> +
>   #define SUNXI_SJTAG_BASE		0x01c23c00
>
>   #define SUNXI_TP_BASE			0x01c25000
>

      parent reply	other threads:[~2016-03-16 13:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  8:34 [U-Boot] [PATCH] sunxi: Support SID e-fuses on A83T and H3 Chen-Yu Tsai
2016-01-27  8:34 ` [U-Boot] [PATCH] sunxi: Add support for Cubietruck Plus Chen-Yu Tsai
2016-03-19 22:43   ` Dennis Gilmore
2016-03-19 23:34     ` Dennis Gilmore
2016-03-20 13:47     ` [U-Boot] [linux-sunxi] " Hans de Goede
2016-03-16 13:10 ` Hans de Goede [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=56E95B3F.6030201@redhat.com \
    --to=hdegoede@redhat.com \
    --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