public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sinan Akman <sinan@writeme.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5] arm: Add sata support on Layerscape ARMv8 board
Date: Mon, 7 Dec 2015 01:03:47 -0500	[thread overview]
Message-ID: <56652143.9040607@writeme.com> (raw)
In-Reply-To: <DM2PR03MB57415E2F16EDE5D08F9B7F2FA090@DM2PR03MB574.namprd03.prod.outlook.com>


   Hi Yuantian

On 06/12/15 10:09 PM, Yuantian Tang wrote:
> Hi York,
>
> Please see explanation inline.
> [...]
> I was trying to use one function for all, but I found separating them is better.
> Take ls1043a and ls2080a as an example, ls2080a has two controllers, while ls1043a has one.
> Ls2080a has two registers that need to be updated while ls1043a has four.
> A lot of #ifdef are needed if we unify them, not mention that in the future, changing one of the platforms' register will affect the other.

    You might want to take into consideration that in the near future we 
will be moving
this to dm. In that respect having all that in one file already will 
probably make things
much easier. If you consider this, perhaps you will have a different view.

> Maybe I am not thinking it through.  If you can give me more detail that viable, I can give a try.
>
>> [...]
>> ports, so we have to choice one. In this case I choice the first one which is
>> SATA1.
>>
>> This should be put into comment, or README if you have one.
> This phenomenon is not LS platform specific, that's uboot's issue which needs another patch to fix.
> I think uboot know that and choice to not fix it because for uboot supporting two sata port is not that significant.

   Again, with dm and reading all the hardware properties from device 
tree will
also change this. If both device nodes are enabled we will have to 
support both
as long as there is no hardware limitation. So I think there is no 
reason why
having both SATA and PCIe would not be significant. It is just that the 
current
implementation has this limitation and there is already some timeline 
for removing
these limitations.

   Regards
   Sinan Akman

  reply	other threads:[~2015-12-07  6:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02  3:27 [U-Boot] [PATCH v5] arm: Add sata support on Layerscape ARMv8 board Yuantian.Tang at freescale.com
2015-12-02  4:12 ` Sinan Akman
2015-12-03 16:27 ` York Sun
2015-12-04  2:47   ` Yuantian Tang
2015-12-04 17:24     ` York Sun
2015-12-07  3:09       ` Yuantian Tang
2015-12-07  6:03         ` Sinan Akman [this message]
2015-12-07  7:04           ` Yuantian Tang
2015-12-07  7:28             ` Sinan Akman
2015-12-07 16:27         ` York Sun
2015-12-08  3:04           ` Yuantian Tang
2015-12-08  4:29             ` York Sun

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=56652143.9040607@writeme.com \
    --to=sinan@writeme.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