| Message ID | 201406210036.59693.sergei.shtylyov@cogentembedded.com (mailing list archive) |
|---|---|
| State | Changes Requested |
| Headers | show |
On Saturday 21 June 2014 00:36:58 Sergei Shtylyov wrote: > + pci0: pci@ee090000 { > + compatible = "renesas,pci-r8a7790"; > + clocks = <&mstp7_clks R8A7790_CLK_EHCI>; > + reg = <0x0 0xee090000 0x0 0xc00>, > + <0x0 0xee080000 0x0 0x1100>; > + interrupts = <0 108 IRQ_TYPE_LEVEL_HIGH>; > + status = "disabled"; > + > + bus-range = <0 0>; > + #address-cells = >; > + #size-cells = <2>; > + #interrupt-cells = <1>; > + interrupt-map-mask = <0xff00 0 0 0x7>; > + interrupt-map = <0x0000 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH > + 0x0800 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH > + 0x1000 0 0 2 &gic 0 108 IRQ_TYPE_LEVEL_HIGH>; > + }; Hmm, this device node is not actually compliant to the PCI binding, it needs a "ranges" property that can be used to look up the memory and I/O space windows. It also needs a device_type property. I realize that the driver doesn't currently use them, but you should adhere to the binding anyway, so we can fix the driver at some point. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello. On 06/21/2014 12:51 AM, Arnd Bergmann wrote: >> + pci0: pci@ee090000 { >> + compatible = "renesas,pci-r8a7790"; >> + clocks = <&mstp7_clks R8A7790_CLK_EHCI>; >> + reg = <0x0 0xee090000 0x0 0xc00>, >> + <0x0 0xee080000 0x0 0x1100>; >> + interrupts = <0 108 IRQ_TYPE_LEVEL_HIGH>; >> + status = "disabled"; >> + >> + bus-range = <0 0>; >> + #address-cells = >; >> + #size-cells = <2>; >> + #interrupt-cells = <1>; >> + interrupt-map-mask = <0xff00 0 0 0x7>; >> + interrupt-map = <0x0000 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH >> + 0x0800 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH >> + 0x1000 0 0 2 &gic 0 108 IRQ_TYPE_LEVEL_HIGH>; >> + }; > Hmm, this device node is not actually compliant to the PCI binding, > it needs a "ranges" property that can be used to look up the memory > and I/O space windows. The PCI driver doesn't support I/O space. > It also needs a device_type property. Hm, are you sure about that? I thought only PCI devices should have it... > I realize that the driver doesn't currently use them, but you should > adhere to the binding anyway, so we can fix the driver at some point. Sigh, agreed about the need to fix the driver. Too bad you've spoken up only now though. And you've ACKed the DT bindings without those properties documented or even present in an example... :-( > Arnd WBR, Sergei -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Saturday 21 June 2014 01:00:21 Sergei Shtylyov wrote: > > On 06/21/2014 12:51 AM, Arnd Bergmann wrote: > > >> + pci0: pci@ee090000 { > >> + compatible = "renesas,pci-r8a7790"; > >> + clocks = <&mstp7_clks R8A7790_CLK_EHCI>; > >> + reg = <0x0 0xee090000 0x0 0xc00>, > >> + <0x0 0xee080000 0x0 0x1100>; > >> + interrupts = <0 108 IRQ_TYPE_LEVEL_HIGH>; > >> + status = "disabled"; > >> + > >> + bus-range = <0 0>; > >> + #address-cells = >; > >> + #size-cells = <2>; > >> + #interrupt-cells = <1>; > >> + interrupt-map-mask = <0xff00 0 0 0x7>; > >> + interrupt-map = <0x0000 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH > >> + 0x0800 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH > >> + 0x1000 0 0 2 &gic 0 108 IRQ_TYPE_LEVEL_HIGH>; > >> + }; > > > Hmm, this device node is not actually compliant to the PCI binding, > > it needs a "ranges" property that can be used to look up the memory > > and I/O space windows. > > The PCI driver doesn't support I/O space. Well, whichever windows are registered by the driver should come from the ranges property. > > It also needs a device_type property. > > Hm, are you sure about that? I thought only PCI devices should have it... Yes, pretty sure it's needed in both the host controller and the devices. > > I realize that the driver doesn't currently use them, but you should > > adhere to the binding anyway, so we can fix the driver at some point. > > Sigh, agreed about the need to fix the driver. Too bad you've spoken up > only now though. And you've ACKed the DT bindings without those properties > documented or even present in an example... Yes, I realized that too late as well, sorry about it. For some reason I only looked at the interrupt-map being done right and forgot to check the ranges. We definitely need to move the code handling the ranges into a common location to avoid this mistake in the future. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello. On 06/21/2014 01:00 AM, Sergei Shtylyov wrote: >>> + pci0: pci@ee090000 { >>> + compatible = "renesas,pci-r8a7790"; >>> + clocks = <&mstp7_clks R8A7790_CLK_EHCI>; >>> + reg = <0x0 0xee090000 0x0 0xc00>, >>> + <0x0 0xee080000 0x0 0x1100>; >>> + interrupts = <0 108 IRQ_TYPE_LEVEL_HIGH>; >>> + status = "disabled"; >>> + >>> + bus-range = <0 0>; >>> + #address-cells = >; >>> + #size-cells = <2>; >>> + #interrupt-cells = <1>; >>> + interrupt-map-mask = <0xff00 0 0 0x7>; >>> + interrupt-map = <0x0000 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH >>> + 0x0800 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH >>> + 0x1000 0 0 2 &gic 0 108 IRQ_TYPE_LEVEL_HIGH>; >>> + }; >> Hmm, this device node is not actually compliant to the PCI binding, >> it needs a "ranges" property that can be used to look up the memory >> and I/O space windows. > The PCI driver doesn't support I/O space. Meaning that the hardware doesn't support it... >> It also needs a device_type property. > Hm, are you sure about that? I thought only PCI devices should have it... Seeing it now in 'bus.pci.pdf'. However, it's strange that the PCI devices also seem to need that... >> Arnd WBR, Sergei -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 06/21/2014 01:10 AM, Arnd Bergmann wrote: >>>> + pci0: pci@ee090000 { >>>> + compatible = "renesas,pci-r8a7790"; >>>> + clocks = <&mstp7_clks R8A7790_CLK_EHCI>; >>>> + reg = <0x0 0xee090000 0x0 0xc00>, >>>> + <0x0 0xee080000 0x0 0x1100>; >>>> + interrupts = <0 108 IRQ_TYPE_LEVEL_HIGH>; >>>> + status = "disabled"; >>>> + >>>> + bus-range = <0 0>; >>>> + #address-cells = >; >>>> + #size-cells = <2>; >>>> + #interrupt-cells = <1>; >>>> + interrupt-map-mask = <0xff00 0 0 0x7>; >>>> + interrupt-map = <0x0000 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH >>>> + 0x0800 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH >>>> + 0x1000 0 0 2 &gic 0 108 IRQ_TYPE_LEVEL_HIGH>; >>>> + }; >>> Hmm, this device node is not actually compliant to the PCI binding, >>> it needs a "ranges" property that can be used to look up the memory >>> and I/O space windows. >> The PCI driver doesn't support I/O space. > Well, whichever windows are registered by the driver should come > from the ranges property. I know. Too bad the driver's original author managed to misunderstand that... >>> It also needs a device_type property. >> Hm, are you sure about that? I thought only PCI devices should have it... > Yes, pretty sure it's needed in both the host controller and the > devices. I don't understand the case of the PCI devices, honestly. Shouldn't the "device_type" prop reflect the device's functionality rather than the bus where it's located? >>> I realize that the driver doesn't currently use them, but you should >>> adhere to the binding anyway, so we can fix the driver at some point. >> Sigh, agreed about the need to fix the driver. Too bad you've spoken up >> only now though. And you've ACKed the DT bindings without those properties >> documented or even present in an example... > Yes, I realized that too late as well, sorry about it. For some reason > I only looked at the interrupt-map being done right and forgot to > check the ranges. > We definitely need to move the code handling the ranges into a common > location to avoid this mistake in the future. It is already in the common location, AFAIK; what's lacking there is the code that parses "dma-ranges" as well but that should be pretty easy to add... > Arnd WBR, Sergei -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Saturday 21 June 2014 01:25:26 Sergei Shtylyov wrote: > On 06/21/2014 01:10 AM, Arnd Bergmann wrote: > >>> It also needs a device_type property. > > >> Hm, are you sure about that? I thought only PCI devices should have it... > > > Yes, pretty sure it's needed in both the host controller and the > > devices. > > I don't understand the case of the PCI devices, honestly. Shouldn't the > "device_type" prop reflect the device's functionality rather than the bus > where it's located? It probably made more sense on real Open Firmware than it does on FDT, but we're trying to follow the bindings anyway. I believe the "device_type=pci" originally indicated a device that has a readable config space (through the OF client interface), which is true for both the host and the devices. > >>> I realize that the driver doesn't currently use them, but you should > >>> adhere to the binding anyway, so we can fix the driver at some point. > > >> Sigh, agreed about the need to fix the driver. Too bad you've spoken up > >> only now though. And you've ACKed the DT bindings without those properties > >> documented or even present in an example... > > > Yes, I realized that too late as well, sorry about it. For some reason > > I only looked at the interrupt-map being done right and forgot to > > check the ranges. > > > We definitely need to move the code handling the ranges into a common > > location to avoid this mistake in the future. > > It is already in the common location, AFAIK; what's lacking there is the > code that parses "dma-ranges" as well but that should be pretty easy to add... We have some common helpers for "ranges" parsing already, but we should improve them so a driver has to do much less in the future. For "dma-ranges", we still to write need most of the code. For platform devices, we can now calculate the offset for the simple (no IOMMU) case, but we still need to calculate the dma mask correctly (that part should be simple, maybe you can help there as you have an immediate need), and we need to handle the IOMMU and swiotlb cases better. For PCI devices, we need to do all the same things we do for platform devices, and we can probably share most of the code. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
> >> Hm, are you sure about that? I thought only PCI devices should have it... > > >Yes, pretty sure it's needed in both the host controller and the > >devices. > > I don't understand the case of the PCI devices, honestly. > Shouldn't the "device_type" prop reflect the device's functionality > rather than the bus where it's located? It is confusingly named, but it is required on the host bridge OF node. The spec says ' .. corresponding to a device that implements a PCI bus', which includes the host bridge. The key element is that it must be present on the node that introduces the PCI 3 dword address encoding scheme, and then on all nodes below it that use the 3 dword scheme. Otherwise Linux common OF PCI code does not work properly. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Index: renesas/arch/arm/boot/dts/r8a7790.dtsi =================================================================== --- renesas.orig/arch/arm/boot/dts/r8a7790.dtsi +++ renesas/arch/arm/boot/dts/r8a7790.dtsi @@ -930,6 +930,60 @@ status = "disabled"; }; + pci0: pci@ee090000 { + compatible = "renesas,pci-r8a7790"; + clocks = <&mstp7_clks R8A7790_CLK_EHCI>; + reg = <0x0 0xee090000 0x0 0xc00>, + <0x0 0xee080000 0x0 0x1100>; + interrupts = <0 108 IRQ_TYPE_LEVEL_HIGH>; + status = "disabled"; + + bus-range = <0 0>; + #address-cells = <3>; + #size-cells = <2>; + #interrupt-cells = <1>; + interrupt-map-mask = <0xff00 0 0 0x7>; + interrupt-map = <0x0000 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH + 0x0800 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH + 0x1000 0 0 2 &gic 0 108 IRQ_TYPE_LEVEL_HIGH>; + }; + + pci1: pci@ee0b0000 { + compatible = "renesas,pci-r8a7790"; + clocks = <&mstp7_clks R8A7790_CLK_EHCI>; + reg = <0x0 0xee0b0000 0x0 0xc00>, + <0x0 0xee0a0000 0x0 0x1100>; + interrupts = <0 112 IRQ_TYPE_LEVEL_HIGH>; + status = "disabled"; + + bus-range = <1 1>; + #address-cells = <3>; + #size-cells = <2>; + #interrupt-cells = <1>; + interrupt-map-mask = <0xff00 0 0 0x7>; + interrupt-map = <0x0000 0 0 1 &gic 0 112 IRQ_TYPE_LEVEL_HIGH + 0x0800 0 0 1 &gic 0 112 IRQ_TYPE_LEVEL_HIGH + 0x1000 0 0 2 &gic 0 112 IRQ_TYPE_LEVEL_HIGH>; + }; + + pci2: pci@ee0d0000 { + compatible = "renesas,pci-r8a7790"; + clocks = <&mstp7_clks R8A7790_CLK_EHCI>; + reg = <0x0 0xee0d0000 0x0 0xc00>, + <0x0 0xee0c0000 0x0 0x1100>; + interrupts = <0 113 IRQ_TYPE_LEVEL_HIGH>; + status = "disabled"; + + bus-range = <2 2>; + #address-cells = <3>; + #size-cells = <2>; + #interrupt-cells = <1>; + interrupt-map-mask = <0xff00 0 0 0x7>; + interrupt-map = <0x0000 0 0 1 &gic 0 113 IRQ_TYPE_LEVEL_HIGH + 0x0800 0 0 1 &gic 0 113 IRQ_TYPE_LEVEL_HIGH + 0x1000 0 0 2 &gic 0 113 IRQ_TYPE_LEVEL_HIGH>; + }; + pciec: pcie@fe000000 { compatible = "renesas,pcie-r8a7790"; reg = <0 0xfe000000 0 0x80000>;