From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] 85xx/p2020ds: Use is_serdes_configured() to determine of PCIe enabled
Date: Fri, 28 May 2010 09:33:44 -0500 [thread overview]
Message-ID: <4BFFD448.9070101@freescale.com> (raw)
In-Reply-To: <4584B13C-7D36-4249-BCC6-FACF36778B61@kernel.crashing.org>
Kumar Gala wrote:
> * tweak SET_STD_PCIE_INFO to track LAW_TRGT_IF_PCIE_n
> * add something like the following to fsl_pci_init_port():
>
> struct law_entry law;
>
> law = find_law(pci_info->mem_phys);
> if (law.index == -1) {
> law.index = set_next_law(pci_info->mem_phys,
> law_size_bits(pci_info->mem_size),
> pci_info->law_trgt_id);
> }
>
> /* duplicate for IO */
Ok, I'll add it to my list for the PCI revamp.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2010-05-28 14:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 9:17 [U-Boot] [PATCH] 85xx: Add is_serdes_configured() support for P2020 SERDES Kumar Gala
2010-05-21 9:17 ` [U-Boot] [PATCH] 85xx/p2020ds: Use is_serdes_configured() to determine of PCIe enabled Kumar Gala
2010-05-26 20:46 ` Timur Tabi
2010-05-26 21:37 ` Timur Tabi
2010-05-27 7:08 ` Wolfgang Denk
2010-05-27 8:42 ` Kumar Gala
2010-05-27 11:20 ` Wolfgang Denk
2010-05-27 12:45 ` Kumar Gala
2010-05-27 13:20 ` Wolfgang Denk
2010-05-27 15:47 ` Kumar Gala
2010-05-27 19:38 ` Scott Wood
2010-05-27 21:27 ` Kumar Gala
2010-05-27 21:28 ` Timur Tabi
2010-05-27 21:38 ` Timur Tabi
2010-05-28 12:53 ` Kumar Gala
2010-05-28 14:33 ` Timur Tabi [this message]
2010-05-21 11:43 ` [U-Boot] [PATCH] 85xx: Add is_serdes_configured() support for P2020SERDES Li Yang
[not found] ` <6D3E1D972AA8904199D0D412F4A64CBD024CF99A@zch01exm26.fsl.freescale.net>
2010-05-21 12:51 ` Kumar Gala
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=4BFFD448.9070101@freescale.com \
--to=timur@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.