From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3] i.MX6: mx6q_sabrelite: add SATA bindings
Date: Sat, 28 Apr 2012 08:36:40 -0700 [thread overview]
Message-ID: <4F9C0E88.5060404@boundarydevices.com> (raw)
In-Reply-To: <4F9C03F5.8030308@googlemail.com>
Hi Dirk,
On 04/28/2012 07:51 AM, Dirk Behme wrote:
> Hi Eric,
>
> On 26.04.2012 01:50, Eric Nelson wrote:
>> Signed-off-by: Eric Nelson<eric.nelson@boundarydevices.com>
>>
>> ---
>> V2 has been stripped of the board-independent changes and
>> uses clrsetbits_le32() instead of twiddling bits by hand.
>>
>> V3 returns immediately from setup_sata() if enable_sata_clock()
>> returns an error.
>>
>> board/freescale/mx6qsabrelite/mx6qsabrelite.c | 32 +++++++++++++++++++++++++
>> include/configs/mx6qsabrelite.h | 13 ++++++++++
>> 2 files changed, 45 insertions(+), 0 deletions(-)
>>
>> diff --git a/board/freescale/mx6qsabrelite/mx6qsabrelite.c
>> b/board/freescale/mx6qsabrelite/mx6qsabrelite.c
>> index 1d09a72..c9a108f 100644
>> --- a/board/freescale/mx6qsabrelite/mx6qsabrelite.c
>> +++ b/board/freescale/mx6qsabrelite/mx6qsabrelite.c
>> @@ -25,6 +25,8 @@
>> #include<asm/arch/imx-regs.h>
>> #include<asm/arch/mx6x_pins.h>
>> #include<asm/arch/iomux-v3.h>
>> +#include<asm/arch/ccm_regs.h>
>
> Do we need ccm_regs.h here?
>
Nope. Good catch.
I'll generate a V4 in a day or two to allow some other review.
Stefano, what's the status of the dwc_ahsata driver?
Without that, the bindings are clearly useless.
Regards,
Eric
next prev parent reply other threads:[~2012-04-28 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <http://lists.denx.de/pipermail/u-boot/2012-March/120150.html>
2012-04-25 23:50 ` [U-Boot] [PATCH V3] i.MX6: mx6q_sabrelite: add SATA bindings Eric Nelson
2012-04-28 14:51 ` Dirk Behme
2012-04-28 15:36 ` Eric Nelson [this message]
2012-04-29 14:48 ` Stefano Babic
2012-04-30 2:27 ` Marek Vasut
2012-04-30 13:33 ` Eric Nelson
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=4F9C0E88.5060404@boundarydevices.com \
--to=eric.nelson@boundarydevices.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