On 07/22/2014 11:37 AM, Rob Herring wrote:
On Fri, Jul 18, 2014 at 2:50 PM, Arnd Bergmann wrote:
On Friday 18 July 2014 14:31:39 Rob Herring wrote:
+
+ Example:
+ pcie_msi_intc: msi-interrupt-controller {
+ interrupt-controller;
+
On 07/22/2014 11:41 AM, Rob Herring wrote:
On Mon, Jul 21, 2014 at 11:39 AM, Murali Karicheri wrote:
On 07/20/2014 09:44 PM, Jingoo Han wrote:
On Saturday, July 19, 2014 5:29 AM, Murali Karicheri wrote:
On 07/18/2014 03:31 PM, Rob Herring wrote:
On Fri, Jul 18, 2014 at 10:14 AM, Murali
On Mon, Jul 21, 2014 at 11:39 AM, Murali Karicheri wrote:
> On 07/20/2014 09:44 PM, Jingoo Han wrote:
>>
>> On Saturday, July 19, 2014 5:29 AM, Murali Karicheri wrote:
>>>
>>> On 07/18/2014 03:31 PM, Rob Herring wrote:
On Fri, Jul 18, 2014 at 10:14 AM, Murali Karicheri
wrote:
>>>
On Fri, Jul 18, 2014 at 2:50 PM, Arnd Bergmann wrote:
> On Friday 18 July 2014 14:31:39 Rob Herring wrote:
>> > +
>> > + Example:
>> > + pcie_msi_intc: msi-interrupt-controller {
>> > + interrupt-controller;
>> > + #interrupt-cells = <1>;
>> > +
On Fri, Jul 18, 2014 at 2:50 PM, Arnd Bergmann a...@arndb.de wrote:
On Friday 18 July 2014 14:31:39 Rob Herring wrote:
+
+ Example:
+ pcie_msi_intc: msi-interrupt-controller {
+ interrupt-controller;
+ #interrupt-cells = 1;
+
On Mon, Jul 21, 2014 at 11:39 AM, Murali Karicheri m-kariche...@ti.com wrote:
On 07/20/2014 09:44 PM, Jingoo Han wrote:
On Saturday, July 19, 2014 5:29 AM, Murali Karicheri wrote:
On 07/18/2014 03:31 PM, Rob Herring wrote:
On Fri, Jul 18, 2014 at 10:14 AM, Murali
On 07/22/2014 11:41 AM, Rob Herring wrote:
On Mon, Jul 21, 2014 at 11:39 AM, Murali Karicherim-kariche...@ti.com wrote:
On 07/20/2014 09:44 PM, Jingoo Han wrote:
On Saturday, July 19, 2014 5:29 AM, Murali Karicheri wrote:
On 07/18/2014 03:31 PM, Rob Herring wrote:
On Fri, Jul 18, 2014 at
On 07/22/2014 11:37 AM, Rob Herring wrote:
On Fri, Jul 18, 2014 at 2:50 PM, Arnd Bergmanna...@arndb.de wrote:
On Friday 18 July 2014 14:31:39 Rob Herring wrote:
+
+ Example:
+ pcie_msi_intc: msi-interrupt-controller {
+ interrupt-controller;
+
On 07/20/2014 09:44 PM, Jingoo Han wrote:
On Saturday, July 19, 2014 5:29 AM, Murali Karicheri wrote:
On 07/18/2014 03:31 PM, Rob Herring wrote:
On Fri, Jul 18, 2014 at 10:14 AM, Murali Karicheri wrote:
--- Cut ---
+
+Optional properties:-
+ phys: phandle to Generic Keystone SerDes
On 07/20/2014 09:44 PM, Jingoo Han wrote:
On Saturday, July 19, 2014 5:29 AM, Murali Karicheri wrote:
On 07/18/2014 03:31 PM, Rob Herring wrote:
On Fri, Jul 18, 2014 at 10:14 AM, Murali Karicherim-kariche...@ti.com wrote:
--- Cut ---
+
+Optional properties:-
+ phys: phandle to
On Saturday, July 19, 2014 5:29 AM, Murali Karicheri wrote:
> On 07/18/2014 03:31 PM, Rob Herring wrote:
> > On Fri, Jul 18, 2014 at 10:14 AM, Murali Karicheri
> > wrote:
> --- Cut ---
> >> +
> >> +Optional properties:-
> >> + phys: phandle to Generic Keystone SerDes phy for PCI
> >> +
On Saturday, July 19, 2014 5:29 AM, Murali Karicheri wrote:
On 07/18/2014 03:31 PM, Rob Herring wrote:
On Fri, Jul 18, 2014 at 10:14 AM, Murali Karicherim-kariche...@ti.com
wrote:
--- Cut ---
+
+Optional properties:-
+ phys: phandle to Generic Keystone SerDes phy for PCI
+
Rob,
On 07/18/2014 03:31 PM, Rob Herring wrote:
On Fri, Jul 18, 2014 at 10:14 AM, Murali Karicheri wrote:
--- Cut ---
+
+Optional properties:-
+ phys: phandle to Generic Keystone SerDes phy for PCI
+ phy-names: name of the Generic Keystine SerDes phy for PCI
+ - If boot
On 07/18/2014 03:50 PM, Arnd Bergmann wrote:
On Friday 18 July 2014 14:31:39 Rob Herring wrote:
+
+ Example:
+ pcie_msi_intc: msi-interrupt-controller {
+ interrupt-controller;
+ #interrupt-cells =<1>;
+ interrupt-parent
On Friday 18 July 2014 14:31:39 Rob Herring wrote:
> > +
> > + Example:
> > + pcie_msi_intc: msi-interrupt-controller {
> > + interrupt-controller;
> > + #interrupt-cells = <1>;
> > + interrupt-parent = <>;
> > +
On Fri, Jul 18, 2014 at 10:14 AM, Murali Karicheri wrote:
> keystone PCIe controller is based on v3.65 version of the
> designware h/w. Main differences are
> 1. No ATU support
> 2. Legacy and MSI irq functions are implemented in
>application register space
>
keystone PCIe controller is based on v3.65 version of the
designware h/w. Main differences are
1. No ATU support
2. Legacy and MSI irq functions are implemented in
application register space
3. MSI interrupts are multiplexed over 8 IRQ lines to the Host
On Fri, Jul 18, 2014 at 10:14 AM, Murali Karicheri m-kariche...@ti.com wrote:
keystone PCIe controller is based on v3.65 version of the
designware h/w. Main differences are
1. No ATU support
2. Legacy and MSI irq functions are implemented in
application register
On Friday 18 July 2014 14:31:39 Rob Herring wrote:
+
+ Example:
+ pcie_msi_intc: msi-interrupt-controller {
+ interrupt-controller;
+ #interrupt-cells = 1;
+ interrupt-parent = gic;
+
On 07/18/2014 03:50 PM, Arnd Bergmann wrote:
On Friday 18 July 2014 14:31:39 Rob Herring wrote:
+
+ Example:
+ pcie_msi_intc: msi-interrupt-controller {
+ interrupt-controller;
+ #interrupt-cells =1;
+ interrupt-parent
Rob,
On 07/18/2014 03:31 PM, Rob Herring wrote:
On Fri, Jul 18, 2014 at 10:14 AM, Murali Karicherim-kariche...@ti.com wrote:
--- Cut ---
+
+Optional properties:-
+ phys: phandle to Generic Keystone SerDes phy for PCI
+ phy-names: name of the Generic Keystine SerDes phy for PCI
+
keystone PCIe controller is based on v3.65 version of the
designware h/w. Main differences are
1. No ATU support
2. Legacy and MSI irq functions are implemented in
application register space
3. MSI interrupts are multiplexed over 8 IRQ lines to the Host
22 matches
Mail list logo