On Wednesday 15 July 2015 09:54:45 David Daney wrote:
> From: David Daney
>
> Signed-off-by: David Daney
Please describe here in what way is this incompatible with SBSA.
>From earlier discussions I had expected ThunderX to be SBSA compliant,
so I'm a bit surprised to see a PCI hack now.
> +#de
On 07/16/2015 01:31 AM, Paul Bolle wrote:
On wo, 2015-07-15 at 09:54 -0700, David Daney wrote:
--- a/drivers/pci/host/Kconfig
+++ b/drivers/pci/host/Kconfig
+config PCI_THUNDER_PEM
+ bool
Do you expect other symbols to select this symbol in the future?
No, ...
Because
at this mome
Hi David,
On Wed, Jul 15, 2015 at 05:54:45PM +0100, David Daney wrote:
> From: David Daney
>
-ENOCOMMITLOG
> Signed-off-by: David Daney
> ---
> drivers/pci/host/Kconfig| 12 +
> drivers/pci/host/Makefile | 2 +
> drivers/pci/host/pcie-thunder-pem.c | 462
> +
On wo, 2015-07-15 at 09:54 -0700, David Daney wrote:
> --- a/drivers/pci/host/Kconfig
> +++ b/drivers/pci/host/Kconfig
> +config PCI_THUNDER_PEM
> + bool
Do you expect other symbols to select this symbol in the future? Because
at this moment PCI_THUNDER_PEM is merely an alias for PCI_THUNDER.
On 15/07/15 17:54, David Daney wrote:
> From: David Daney
>
> Signed-off-by: David Daney
> ---
> drivers/pci/host/Kconfig| 12 +
> drivers/pci/host/Makefile | 2 +
> drivers/pci/host/pcie-thunder-pem.c | 462
>
> drivers/pci/host/pc
Hi,
As mentioned in my reply to the cover letter, a DT binding document is
necessary for this.
It looks like many of the properties of your root complex which should
be described (e.g. physical addresses, master IDs as visible to MSI
controllers) are blindly assumed by this driver, and I expect t
6 matches
Mail list logo
