From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/4] nitrogen6x: Move setup_sata to common part
Date: Thu, 28 Nov 2013 09:07:58 +0100 [thread overview]
Message-ID: <5296F9DE.90409@denx.de> (raw)
In-Reply-To: <1384533774-3233-3-git-send-email-giuseppe.pagano@seco.com>
Hi Giuseppe,
On 15/11/2013 17:42, Giuseppe Pagano wrote:
> Move setup_sata function definition from platform file nitrogen6x.c
> to arch/arm/imx-common/sata.c to avoid code duplication.
>
> Signed-off-by: Giuseppe Pagano <giuseppe.pagano@seco.com>
> CC: Stefano Babic <sbabic@denx.de>
> CC: Fabio Estevam <fabio.estevam@freescale.com>
> CC: Eric Nelson <eric.nelson@boundarydevices.com>
> ---
>
> Changes in v2:
> - Split previous patch between nitrogen6x udoo code changes.
>
> arch/arm/imx-common/Makefile | 1 +
> arch/arm/imx-common/sata.c | 33 ++++++++++++++++++++++++++++++++
> arch/arm/include/asm/imx-common/sata.h | 17 ++++++++++++++++
> board/boundary/nitrogen6x/nitrogen6x.c | 27 +-------------------------
> 4 files changed, 52 insertions(+), 26 deletions(-)
> create mode 100644 arch/arm/imx-common/sata.c
> create mode 100644 arch/arm/include/asm/imx-common/sata.h
>
> diff --git a/arch/arm/imx-common/Makefile b/arch/arm/imx-common/Makefile
> index 727a052..6f85c42 100644
> --- a/arch/arm/imx-common/Makefile
> +++ b/arch/arm/imx-common/Makefile
> @@ -17,6 +17,7 @@ endif
> ifeq ($(SOC),$(filter $(SOC),mx5 mx6))
> COBJS-y += timer.o cpu.o speed.o
> COBJS-$(CONFIG_I2C_MXC) += i2c-mxv7.o
> +COBJS-$(CONFIG_CMD_SATA) += sata.o
By testing this breaks mx5 boards:
Boards with errors: 3 ( m53evk ima3-mx53 mx53loco )
The reason is that mx5 does not have and does not need a setup_sata, and
the code in sata.c (all registers definitions) are mx6 specific.
I suggest the file is compiled only for iMX6 (now it is for both mx5 and
mx6) as result of filter.
Can you send a V3 of the two sata patches ? You do not need to resend
the whole patchset.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2013-11-28 8:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 16:42 [U-Boot] [PATCH v2 0/4] udoo: Move and optimize platform register setting Giuseppe Pagano
2013-11-15 16:42 ` [U-Boot] [PATCH v2 1/4] udoo: Add ethernet support (FEC + Micrel KSZ9031) Giuseppe Pagano
2013-11-18 15:51 ` Stefano Babic
2013-11-18 17:05 ` Giuseppe Pagano
2013-11-20 7:55 ` Giuseppe Pagano
2013-11-19 4:34 ` Fabio Estevam
2013-11-25 15:06 ` Fabio Estevam
2013-11-28 8:26 ` Stefano Babic
2013-11-28 9:23 ` Giuseppe Pagano
2013-11-15 16:42 ` [U-Boot] [PATCH v2 2/4] nitrogen6x: Move setup_sata to common part Giuseppe Pagano
2013-11-28 8:07 ` Stefano Babic [this message]
2013-11-15 16:42 ` [U-Boot] [PATCH v2 3/4] udoo: Add SATA support on uDoo Board Giuseppe Pagano
2013-11-15 16:42 ` [U-Boot] [PATCH v2 4/4] udoo: Fix watchdog during kernel boot Giuseppe Pagano
2013-11-28 8:26 ` Stefano Babic
2013-11-28 8:23 ` [U-Boot] [PATCH v2 0/4] udoo: Move and optimize platform register setting Stefano Babic
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=5296F9DE.90409@denx.de \
--to=sbabic@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