[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <55A8FCBE.3090703@ti.com>
Date: Fri, 17 Jul 2015 09:01:50 -0400
From: Murali Karicheri <m-karicheri2@...com>
To: "santosh.shilimkar@...cle.com" <santosh.shilimkar@...cle.com>,
<robh+dt@...nel.org>, <pawel.moll@....com>, <mark.rutland@....com>,
<ijc+devicetree@...lion.org.uk>, <galak@...eaurora.org>,
<linux@....linux.org.uk>, <devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <ssantosh@...nel.org>
Subject: Re: [PATCH v1 1/2] ARM: keystone: dts: fix dt bindings for PCIe
On 07/16/2015 06:43 PM, santosh.shilimkar@...cle.com wrote:
> On 7/16/15 2:51 PM, Murali Karicheri wrote:
>> Currently PCIe DT bindings are broken. PCIe driver can't function
>> without having a SerDes driver that provide the phy configuration.
>> On K2E EVM, this causes problem since the EVM has Marvell SATA
>> controller present and with default values in the SerDes register,
>> it seems to pass the PCIe link check, but causes issues since
>> the configuration is not correct. The manifestation is that when
>> EVM is booted with NFS rootfs, the boot hangs. We shouldn't enable
>> PCIe on this EVM since to work, SerDes driver has to be present as
>> well. So by default, the PCIe DT binding should be disabled in SoC
>> specific DTS. It can be enabled in the board specific DTS when the
>> SerDes device driver is also present.
>>
>> So fix the status of PCIe DT bindings in the SoC specific DTS to
>> "disabled". To enable PCIe, the status should be set to "ok" in
>> the EVM DTS file when SerDes driver support becomes available in
>> the upstream tree.
>>
>> Signed-off-by: Murali Karicheri <m-karicheri2@...com>
>> ---
>> - updated commit description to make it clear that it is fix
>> to be applied to v4.2-rc.
>
> Just sent pull request with both of these patches from the series.
>
> Regards,
> Santosh
>
>
Thanks Santosh.
regards,
--
Murali Karicheri
Linux Kernel, Keystone
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists