From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 05/20] armv8/ls2085a: call ft_pcie_setup() to change dts status
Date: Wed, 27 May 2015 08:27:27 -0700 [thread overview]
Message-ID: <5565E25F.3040908@freescale.com> (raw)
In-Reply-To: <DM2PR0301MB06709B928DDCAC9F52B86E0AA9CB0@DM2PR0301MB0670.namprd03.prod.outlook.com>
On 05/26/2015 09:30 PM, Kushwaha Prabhakar-B32579 wrote:
>>>
>>> Shouldn't this function be called from SoC function? It is not a
>>> board- dependent setup, but rather depending on RCW which is an SoC
>> feature.
>>>
>
> There are 2 function and their relationship is like this
> ft_pci_setup calling ft_pcie_ls_setup.
>
> ft_pcie_ls_setup is doing thing related to SoC.
> So I believe ft_pci_setup can be called from board file. Not sure
>
I was thinking to move the call to fdt.c for the SoC, for example in the
function of ft_cpu_setup().
York
next prev parent reply other threads:[~2015-05-27 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 7:08 [U-Boot] [PATCH 01/20] armv8/ls2085ardb: Add eth & phy f/w loading support Prabhakar Kushwaha
2015-05-18 7:08 ` [U-Boot] [PATCH 02/20] armv8/ls2085ardb: add hwconfig setting for eSDHC Prabhakar Kushwaha
2015-05-18 7:08 ` [U-Boot] [PATCH 03/20] armv8/ls2085a: Enable Date command for QDS and RDB Prabhakar Kushwaha
2015-05-18 7:08 ` [U-Boot] [PATCH 04/20] armv8/ls2085aqds: Add support of 0x49 in ethernet Prabhakar Kushwaha
2015-05-26 15:51 ` York Sun
2015-05-18 7:08 ` [U-Boot] [PATCH 05/20] armv8/ls2085a: call ft_pcie_setup() to change dts status Prabhakar Kushwaha
2015-05-26 15:54 ` York Sun
2015-05-27 3:40 ` Lian M.H.
2015-05-27 4:30 ` Kushwaha Prabhakar
2015-05-27 15:27 ` York Sun [this message]
2015-05-18 7:08 ` [U-Boot] [PATCH 06/20] armv8/ls2085qds: Update SFP TX bit as "0" to enable XFI Prabhakar Kushwaha
2015-05-18 7:08 ` [U-Boot] [PATCH 07/20] armv8/ls2085rdb: Update PCA9547PW slave address Prabhakar Kushwaha
2015-05-26 15:55 ` 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=5565E25F.3040908@freescale.com \
--to=yorksun@freescale.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