public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 01/11] Blackfin: bf60x: new processor header files
Date: Tue, 19 Feb 2013 11:15:01 +0100	[thread overview]
Message-ID: <20130219101501.D1F63200530@gemini.denx.de> (raw)
In-Reply-To: <1361257266-3722-2-git-send-email-sonic.adi@gmail.com>

Dear Sonic Zhang,

In message <1361257266-3722-2-git-send-email-sonic.adi@gmail.com> you wrote:
> 
> Add header files for blackfin new processor bf60x.
...
>  arch/blackfin/include/asm/mach-bf609/BF609_def.h  | 3758 +++++++++++++++++++++

This is a bit excessive, isn't it?  Do we really all thse many
thousands lines of defines?


> diff --git a/arch/blackfin/include/asm/mach-bf609/BF609_def.h b/arch/blackfin/include/asm/mach-bf609/BF609_def.h
> new file mode 100644
> index 0000000..39b740f
> --- /dev/null
> +++ b/arch/blackfin/include/asm/mach-bf609/BF609_def.h
> @@ -0,0 +1,3758 @@
> +/* DO NOT EDIT THIS FILE
> + * Automatically generated by generate-def-headers.xsl
> + * DO NOT EDIT THIS FILE
> + */
> +
> +#ifndef __BFIN_DEF_ADSP_BF609_proc__
> +#define __BFIN_DEF_ADSP_BF609_proc__
> +
> +#include "../mach-common/ADSP-EDN-core_def.h"
> +
> +#define CNT_CFG                     0xFFC00400         /* CNT0 Configuration Register */
> +#define CNT_IMSK                    0xFFC00404         /* CNT0 Interrupt Mask Register */
> +#define CNT_STAT                    0xFFC00408         /* CNT0 Status Register */
> +#define CNT_CMD                     0xFFC0040C         /* CNT0 Command Register */
> +#define CNT_DEBNCE                  0xFFC00410         /* CNT0 Debounce Register */
> +#define CNT_CNTR                    0xFFC00414         /* CNT0 Counter Register */
> +#define CNT_MAX                     0xFFC00418         /* CNT0 Maximum Count Register */
> +#define CNT_MIN                     0xFFC0041C         /* CNT0 Minimum Count Register */
> +
> +#define RSI_CLK_CONTROL             0xFFC00604         /* RSI0 Clock Control Register */
> +#define RSI_ARGUMENT                0xFFC00608         /* RSI0 Argument Register */
> +#define RSI_COMMAND                 0xFFC0060C         /* RSI0 Command Register */
> +#define RSI_RESP_CMD                0xFFC00610         /* RSI0 Response Command Register */
> +#define RSI_RESPONSE0               0xFFC00614         /* RSI0 Response 0 Register */
> +#define RSI_RESPONSE1               0xFFC00618         /* RSI0 Response 1 Register */
> +#define RSI_RESPONSE2               0xFFC0061C         /* RSI0 Response 2 Register */
> +#define RSI_RESPONSE3               0xFFC00620         /* RSI0 Response 3 Register */
> +#define RSI_DATA_TIMER              0xFFC00624         /* RSI0 Data Timer Register */
> +#define RSI_DATA_LGTH               0xFFC00628         /* RSI0 Data Length Register */
> +#define RSI_DATA_CONTROL            0xFFC0062C         /* RSI0 Data Control Register */
> +#define RSI_DATA_CNT                0xFFC00630         /* RSI0 Data Count Register */
> +#define RSI_STATUS                  0xFFC00634         /* RSI0 Status Register */
> +#define RSI_STATUSCL                0xFFC00638         /* RSI0 Status Clear Register */
> +#define RSI_IMSK0                   0xFFC0063C         /* RSI0 Interrupt 0 Mask Register */
> +#define RSI_IMSK1                   0xFFC00640         /* RSI0 Interrupt 1 Mask Register */
> +#define RSI_FIFO_CNT                0xFFC00648         /* RSI0 FIFO Counter Register */
...

I think I mentioned before that device registers have to be described
using C structs in U-Boot, and proper I/O accessors must be used to
access these.

In any case, please trim to the really needed definitions.

> --- /dev/null
> +++ b/arch/blackfin/include/asm/mach-bf609/anomaly.h
> @@ -0,0 +1,103 @@
> +/*
> + * DO NOT EDIT THIS FILE
> + * This file is under version control at
> + *   svn://sources.blackfin.uclinux.org/toolchain/trunk/proc-defs/header-frags/
> + * and can be replaced with that version at any time
> + * DO NOT EDIT THIS FILE

This makes no sense to me.

> + * Copyright 2004-2012 Analog Devices Inc.
> + * Licensed under the ADI BSD license.
> + *   https://docs.blackfin.uclinux.org/doku.php?id=adi_bsd
> + */

I'm not sure if this has been discussed before - is this really GPL
compatible?



Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Harrison's Postulate:
	For every action, there is an equal and opposite criticism.

  reply	other threads:[~2013-02-19 10:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19  7:00 [U-Boot] [PATCH v2 00/11] *** SUBJECT HERE *** Sonic Zhang
2013-02-19  7:00 ` [U-Boot] [PATCH v2 01/11] Blackfin: bf60x: new processor header files Sonic Zhang
2013-02-19 10:15   ` Wolfgang Denk [this message]
2013-02-20  3:20     ` Sonic Zhang
2013-02-19  7:00 ` [U-Boot] [PATCH v2 02/11] Blackfin: bf60x: Port blackfin core architecture code to boot on bf60x Sonic Zhang
2013-02-19  7:00 ` [U-Boot] [PATCH v2 03/11] Blackfin: bf60x: add serial support Sonic Zhang
2013-02-19  7:00 ` [U-Boot] [PATCH v2 04/11] Blackfin: bf60x: add dma support Sonic Zhang
2013-02-19  7:01 ` [U-Boot] [PATCH v2 05/11] Blackfin: bf60x: support big cplb page Sonic Zhang
2013-02-19  7:01 ` [U-Boot] [PATCH v2 06/11] Blackfin: bf60x: add gpio support Sonic Zhang
2013-02-19  7:01 ` [U-Boot] [PATCH v2 07/11] blackfin: bf609: add board and headers files to support bf609 Sonic Zhang
2013-02-19  7:01 ` [U-Boot] [PATCH v2 08/11] Blackfin: bf60x: add rsi/sdh support Sonic Zhang
2013-02-19  7:01 ` [U-Boot] [PATCH v2 09/11] Blackfin: spi: add bf6xx spi driver Sonic Zhang
2013-02-19  7:01 ` [U-Boot] [PATCH v2 10/11] Blackfin: bf60x: add hw watchdog support Sonic Zhang
2013-02-19  7:01 ` [U-Boot] [PATCH v2 11/11] Blackfin: bf60x: add resume from hibernate Sonic Zhang
2013-02-19 10:14 ` [U-Boot] [PATCH v2 00/11] *** SUBJECT HERE *** Wolfgang Denk
2013-02-20  8:36   ` Sonic Zhang
2013-02-21  1:50     ` Tom Rini
2013-02-21 10:46       ` Sonic Zhang

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=20130219101501.D1F63200530@gemini.denx.de \
    --to=wd@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