| Message ID | 1430174242-29465-5-git-send-email-abrestic@chromium.org |
|---|---|
| State | Superseded, archived |
| Headers | show |
On Mon, 27 Apr 2015, Andrew Bresticker wrote: > Add a binding document for the XUSB host complex on NVIDIA Tegra124 > and later SoCs. The XUSB host complex includes a mailbox for > communication with the XUSB micro-controller and an xHCI host-controller. > > Signed-off-by: Andrew Bresticker <abrestic@chromium.org> > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Pawel Moll <pawel.moll@arm.com> > Cc: Mark Rutland <mark.rutland@arm.com> > Cc: Ian Campbell <ijc+devicetree@hellion.org.uk> > Cc: Kumar Gala <galak@codeaurora.org> > Cc: Samuel Ortiz <sameo@linux.intel.com> > Cc: Lee Jones <lee.jones@linaro.org> > --- > New for v7. > --- > .../bindings/mfd/nvidia,tegra124-xusb.txt | 46 ++++++++++++++++++++++ > 1 file changed, 46 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt > > diff --git a/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt > new file mode 100644 > index 0000000..6a46680 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt > @@ -0,0 +1,46 @@ > +NVIDIA Tegra XUSB host copmlex > +============================== > + > +The XUSB host complex on Tegra124 and later SoCs contains an xHCI host > +controller and a mailbox for communication with the XUSB micro-controller. > + > +Required properties: > +-------------------- > + - compatible: For Tegra124, must contain "nvidia,tegra124-xusb". > + Otherwise, must contain '"nvidia,<chip>-xusb", "nvidia,tegra124-xusb"' > + where <chip> is tegra132. Okay. Why? > + - reg: Must contain register base and length for each register set listed > + in reg-names. You've mentioned 2 of the cells, what about the remaining 2? > + - reg-names: Must include the following entries: > + - xhci > + - fpci > + - ipfs > + - interrupts: Must contain an interrupt for each entry in interrupt-names. > + - interrupt-names: Must include the following entries: > + - host > + - smi > + - pme > + > +Example: > +-------- > + usb@0,70090000 { > + compatible = "nvidia,tegra124-xusb"; > + reg = <0x0 0x70090000 0x0 0x8000>, > + <0x0 0x70098000 0x0 0x1000>, > + <0x0 0x70099000 0x0 0x1000>; > + reg-names = "xhci", "fpci", "ipfs"; > + interrupts = <GIC_SPI 39 IRQ_TYPE_LEVEL_HIGH>, > + <GIC_SPI 40 IRQ_TYPE_LEVEL_HGIH>, > + <GIC_SPI 43 IRQ_TYPE_LEVEL_HIGH>; > + interrupt-names = "host", "smi", "pme"; Are these resources used by both children? If not, place them into the children and ioremap() them from the associated child drivers. Using an MFD driver to pull all of this out an disseminate it is a bit bonkers. > + usb-host { > + compatible = "nvidia,tegra124-xhci"; > + ... > + }; > + > + mailbox { > + compatible = "nvidia,tegra124-xusb-mbox"; > + ... > + }; > + };
Lee, On Wed, Apr 29, 2015 at 2:25 AM, Lee Jones <lee.jones@linaro.org> wrote: > On Mon, 27 Apr 2015, Andrew Bresticker wrote: > >> Add a binding document for the XUSB host complex on NVIDIA Tegra124 >> and later SoCs. The XUSB host complex includes a mailbox for >> communication with the XUSB micro-controller and an xHCI host-controller. >> >> Signed-off-by: Andrew Bresticker <abrestic@chromium.org> >> Cc: Rob Herring <robh+dt@kernel.org> >> Cc: Pawel Moll <pawel.moll@arm.com> >> Cc: Mark Rutland <mark.rutland@arm.com> >> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk> >> Cc: Kumar Gala <galak@codeaurora.org> >> Cc: Samuel Ortiz <sameo@linux.intel.com> >> Cc: Lee Jones <lee.jones@linaro.org> >> --- >> New for v7. >> --- >> .../bindings/mfd/nvidia,tegra124-xusb.txt | 46 ++++++++++++++++++++++ >> 1 file changed, 46 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt >> >> diff --git a/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt >> new file mode 100644 >> index 0000000..6a46680 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt >> @@ -0,0 +1,46 @@ >> +NVIDIA Tegra XUSB host copmlex >> +============================== >> + >> +The XUSB host complex on Tegra124 and later SoCs contains an xHCI host >> +controller and a mailbox for communication with the XUSB micro-controller. >> + >> +Required properties: >> +-------------------- >> + - compatible: For Tegra124, must contain "nvidia,tegra124-xusb". >> + Otherwise, must contain '"nvidia,<chip>-xusb", "nvidia,tegra124-xusb"' >> + where <chip> is tegra132. > > Okay. Why? Why what? This is the convention used for Tegra bindings and is also documented in Documentation/devicetree/bindings/submitting-patches.txt. See nvidia,tegra114-spi.txt and nvidia,tegra20-i2c.txt for other examples of this. >> + - reg: Must contain register base and length for each register set listed >> + in reg-names. > > You've mentioned 2 of the cells, what about the remaining 2? The example given was for Tegra124, where there are two address cells and two size cells. >> + - reg-names: Must include the following entries: >> + - xhci >> + - fpci >> + - ipfs >> + - interrupts: Must contain an interrupt for each entry in interrupt-names. >> + - interrupt-names: Must include the following entries: >> + - host >> + - smi >> + - pme >> + >> +Example: >> +-------- >> + usb@0,70090000 { >> + compatible = "nvidia,tegra124-xusb"; >> + reg = <0x0 0x70090000 0x0 0x8000>, >> + <0x0 0x70098000 0x0 0x1000>, >> + <0x0 0x70099000 0x0 0x1000>; >> + reg-names = "xhci", "fpci", "ipfs"; >> + interrupts = <GIC_SPI 39 IRQ_TYPE_LEVEL_HIGH>, >> + <GIC_SPI 40 IRQ_TYPE_LEVEL_HGIH>, >> + <GIC_SPI 43 IRQ_TYPE_LEVEL_HIGH>; >> + interrupt-names = "host", "smi", "pme"; > > Are these resources used by both children? Only the FPCI register set is shared. > If not, place them into the children and ioremap() them from the > associated child drivers. Ok. -Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 29 Apr 2015, Andrew Bresticker wrote: > Lee, > > On Wed, Apr 29, 2015 at 2:25 AM, Lee Jones <lee.jones@linaro.org> wrote: > > On Mon, 27 Apr 2015, Andrew Bresticker wrote: > > > >> Add a binding document for the XUSB host complex on NVIDIA Tegra124 > >> and later SoCs. The XUSB host complex includes a mailbox for > >> communication with the XUSB micro-controller and an xHCI host-controller. > >> > >> Signed-off-by: Andrew Bresticker <abrestic@chromium.org> > >> Cc: Rob Herring <robh+dt@kernel.org> > >> Cc: Pawel Moll <pawel.moll@arm.com> > >> Cc: Mark Rutland <mark.rutland@arm.com> > >> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk> > >> Cc: Kumar Gala <galak@codeaurora.org> > >> Cc: Samuel Ortiz <sameo@linux.intel.com> > >> Cc: Lee Jones <lee.jones@linaro.org> > >> --- > >> New for v7. > >> --- > >> .../bindings/mfd/nvidia,tegra124-xusb.txt | 46 ++++++++++++++++++++++ > >> 1 file changed, 46 insertions(+) > >> create mode 100644 Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt > >> > >> diff --git a/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt > >> new file mode 100644 > >> index 0000000..6a46680 > >> --- /dev/null > >> +++ b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt > >> @@ -0,0 +1,46 @@ > >> +NVIDIA Tegra XUSB host copmlex > >> +============================== > >> + > >> +The XUSB host complex on Tegra124 and later SoCs contains an xHCI host > >> +controller and a mailbox for communication with the XUSB micro-controller. > >> + > >> +Required properties: > >> +-------------------- > >> + - compatible: For Tegra124, must contain "nvidia,tegra124-xusb". > >> + Otherwise, must contain '"nvidia,<chip>-xusb", "nvidia,tegra124-xusb"' > >> + where <chip> is tegra132. > > > > Okay. Why? > > Why what? This is the convention used for Tegra bindings and is also > documented in Documentation/devicetree/bindings/submitting-patches.txt. > See nvidia,tegra114-spi.txt and nvidia,tegra20-i2c.txt for other > examples of this. It seems strange to me that you'd mention two specific chips in one compatible string. What's the purpose of that? > >> + - reg: Must contain register base and length for each register set listed > >> + in reg-names. > > > > You've mentioned 2 of the cells, what about the remaining 2? > > The example given was for Tegra124, where there are two address cells > and two size cells. I don't get that. How does that work? > >> + - reg-names: Must include the following entries: > >> + - xhci > >> + - fpci > >> + - ipfs > >> + - interrupts: Must contain an interrupt for each entry in interrupt-names. > >> + - interrupt-names: Must include the following entries: > >> + - host > >> + - smi > >> + - pme > >> + > >> +Example: > >> +-------- > >> + usb@0,70090000 { > >> + compatible = "nvidia,tegra124-xusb"; > >> + reg = <0x0 0x70090000 0x0 0x8000>, > >> + <0x0 0x70098000 0x0 0x1000>, > >> + <0x0 0x70099000 0x0 0x1000>; > >> + reg-names = "xhci", "fpci", "ipfs"; > >> + interrupts = <GIC_SPI 39 IRQ_TYPE_LEVEL_HIGH>, > >> + <GIC_SPI 40 IRQ_TYPE_LEVEL_HGIH>, > >> + <GIC_SPI 43 IRQ_TYPE_LEVEL_HIGH>; > >> + interrupt-names = "host", "smi", "pme"; > > > > Are these resources used by both children? > > Only the FPCI register set is shared. > > > If not, place them into the children and ioremap() them from the > > associated child drivers. > > Ok. Great.
On Wed, Apr 29, 2015 at 11:34 AM, Lee Jones <lee.jones@linaro.org> wrote: > On Wed, 29 Apr 2015, Andrew Bresticker wrote: > >> Lee, >> >> On Wed, Apr 29, 2015 at 2:25 AM, Lee Jones <lee.jones@linaro.org> wrote: >> > On Mon, 27 Apr 2015, Andrew Bresticker wrote: >> > >> >> Add a binding document for the XUSB host complex on NVIDIA Tegra124 >> >> and later SoCs. The XUSB host complex includes a mailbox for >> >> communication with the XUSB micro-controller and an xHCI host-controller. >> >> >> >> Signed-off-by: Andrew Bresticker <abrestic@chromium.org> >> >> Cc: Rob Herring <robh+dt@kernel.org> >> >> Cc: Pawel Moll <pawel.moll@arm.com> >> >> Cc: Mark Rutland <mark.rutland@arm.com> >> >> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk> >> >> Cc: Kumar Gala <galak@codeaurora.org> >> >> Cc: Samuel Ortiz <sameo@linux.intel.com> >> >> Cc: Lee Jones <lee.jones@linaro.org> >> >> --- >> >> New for v7. >> >> --- >> >> .../bindings/mfd/nvidia,tegra124-xusb.txt | 46 ++++++++++++++++++++++ >> >> 1 file changed, 46 insertions(+) >> >> create mode 100644 Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt >> >> >> >> diff --git a/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt >> >> new file mode 100644 >> >> index 0000000..6a46680 >> >> --- /dev/null >> >> +++ b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt >> >> @@ -0,0 +1,46 @@ >> >> +NVIDIA Tegra XUSB host copmlex >> >> +============================== >> >> + >> >> +The XUSB host complex on Tegra124 and later SoCs contains an xHCI host >> >> +controller and a mailbox for communication with the XUSB micro-controller. >> >> + >> >> +Required properties: >> >> +-------------------- >> >> + - compatible: For Tegra124, must contain "nvidia,tegra124-xusb". >> >> + Otherwise, must contain '"nvidia,<chip>-xusb", "nvidia,tegra124-xusb"' >> >> + where <chip> is tegra132. >> > >> > Okay. Why? >> >> Why what? This is the convention used for Tegra bindings and is also >> documented in Documentation/devicetree/bindings/submitting-patches.txt. >> See nvidia,tegra114-spi.txt and nvidia,tegra20-i2c.txt for other >> examples of this. > > It seems strange to me that you'd mention two specific chips in one > compatible string. What's the purpose of that? The Tegra maintainers can correct me if I'm wrong here, but the point is, I think, to future-proof the binding. There are currently no differences between Tegra124 and Tegra132 that need to be accounted for in the driver, so the driver need only match against "nvidia,tegra124-xusb". If a Tegra132-specific quirk comes about later all Tegra132 device-trees will also include the "nvidia,tegra132-*" compatible string, so we can simply update the driver without breaking DT backwards-compatibility. >> >> + - reg: Must contain register base and length for each register set listed >> >> + in reg-names. >> > >> > You've mentioned 2 of the cells, what about the remaining 2? >> >> The example given was for Tegra124, where there are two address cells >> and two size cells. > > I don't get that. How does that work? Tegra124 has a physical address space of > 4GB because of LPAE, thus a single cell each for address and size is not sufficient. The arm64 Tegra SoCs will obviously also use two address and size cells. Take a look at arch/arm/boot/dts/tegra124.dtsi. -Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 29 Apr 2015, Andrew Bresticker wrote: > On Wed, Apr 29, 2015 at 11:34 AM, Lee Jones <lee.jones@linaro.org> wrote: > > On Wed, 29 Apr 2015, Andrew Bresticker wrote: > > > >> Lee, > >> > >> On Wed, Apr 29, 2015 at 2:25 AM, Lee Jones <lee.jones@linaro.org> wrote: > >> > On Mon, 27 Apr 2015, Andrew Bresticker wrote: > >> > > >> >> Add a binding document for the XUSB host complex on NVIDIA Tegra124 > >> >> and later SoCs. The XUSB host complex includes a mailbox for > >> >> communication with the XUSB micro-controller and an xHCI host-controller. > >> >> > >> >> Signed-off-by: Andrew Bresticker <abrestic@chromium.org> > >> >> Cc: Rob Herring <robh+dt@kernel.org> > >> >> Cc: Pawel Moll <pawel.moll@arm.com> > >> >> Cc: Mark Rutland <mark.rutland@arm.com> > >> >> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk> > >> >> Cc: Kumar Gala <galak@codeaurora.org> > >> >> Cc: Samuel Ortiz <sameo@linux.intel.com> > >> >> Cc: Lee Jones <lee.jones@linaro.org> > >> >> --- > >> >> New for v7. > >> >> --- > >> >> .../bindings/mfd/nvidia,tegra124-xusb.txt | 46 ++++++++++++++++++++++ > >> >> 1 file changed, 46 insertions(+) > >> >> create mode 100644 Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt > >> >> > >> >> diff --git a/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt > >> >> new file mode 100644 > >> >> index 0000000..6a46680 > >> >> --- /dev/null > >> >> +++ b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt > >> >> @@ -0,0 +1,46 @@ > >> >> +NVIDIA Tegra XUSB host copmlex > >> >> +============================== > >> >> + > >> >> +The XUSB host complex on Tegra124 and later SoCs contains an xHCI host > >> >> +controller and a mailbox for communication with the XUSB micro-controller. > >> >> + > >> >> +Required properties: > >> >> +-------------------- > >> >> + - compatible: For Tegra124, must contain "nvidia,tegra124-xusb". > >> >> + Otherwise, must contain '"nvidia,<chip>-xusb", "nvidia,tegra124-xusb"' > >> >> + where <chip> is tegra132. > >> > > >> > Okay. Why? > >> > >> Why what? This is the convention used for Tegra bindings and is also > >> documented in Documentation/devicetree/bindings/submitting-patches.txt. > >> See nvidia,tegra114-spi.txt and nvidia,tegra20-i2c.txt for other > >> examples of this. > > > > It seems strange to me that you'd mention two specific chips in one > > compatible string. What's the purpose of that? > > The Tegra maintainers can correct me if I'm wrong here, but the point > is, I think, to future-proof the binding. There are currently no > differences between Tegra124 and Tegra132 that need to be accounted > for in the driver, so the driver need only match against > "nvidia,tegra124-xusb". If a Tegra132-specific quirk comes about > later all Tegra132 device-trees will also include the > "nvidia,tegra132-*" compatible string, so we can simply update the > driver without breaking DT backwards-compatibility. I still don't understand why you need to use them both at the same time. Why don't you use nvidia,tegra124-* for Tegra124 and nvidia,tegra132-* for Tegra132? > >> >> + - reg: Must contain register base and length for each register set listed > >> >> + in reg-names. > >> > > >> > You've mentioned 2 of the cells, what about the remaining 2? > >> > >> The example given was for Tegra124, where there are two address cells > >> and two size cells. > > > > I don't get that. How does that work? > > Tegra124 has a physical address space of > 4GB because of LPAE, thus a > single cell each for address and size is not sufficient. The arm64 > Tegra SoCs will obviously also use two address and size cells. Take a > look at arch/arm/boot/dts/tegra124.dtsi. Okay, so these get shifted and &'ed into posstible 64bit addresses? I guess I just thought ARM64 addresses would look like: 0xXXXXXXXXXXXXXXXX 0xXXXX
On Thu, Apr 30, 2015 at 3:06 AM, Lee Jones <lee.jones@linaro.org> wrote: > On Wed, 29 Apr 2015, Andrew Bresticker wrote: > >> On Wed, Apr 29, 2015 at 11:34 AM, Lee Jones <lee.jones@linaro.org> wrote: >> > On Wed, 29 Apr 2015, Andrew Bresticker wrote: >> > >> >> Lee, >> >> >> >> On Wed, Apr 29, 2015 at 2:25 AM, Lee Jones <lee.jones@linaro.org> wrote: >> >> > On Mon, 27 Apr 2015, Andrew Bresticker wrote: >> >> > >> >> >> Add a binding document for the XUSB host complex on NVIDIA Tegra124 >> >> >> and later SoCs. The XUSB host complex includes a mailbox for >> >> >> communication with the XUSB micro-controller and an xHCI host-controller. >> >> >> >> >> >> Signed-off-by: Andrew Bresticker <abrestic@chromium.org> >> >> >> Cc: Rob Herring <robh+dt@kernel.org> >> >> >> Cc: Pawel Moll <pawel.moll@arm.com> >> >> >> Cc: Mark Rutland <mark.rutland@arm.com> >> >> >> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk> >> >> >> Cc: Kumar Gala <galak@codeaurora.org> >> >> >> Cc: Samuel Ortiz <sameo@linux.intel.com> >> >> >> Cc: Lee Jones <lee.jones@linaro.org> >> >> >> --- >> >> >> New for v7. >> >> >> --- >> >> >> .../bindings/mfd/nvidia,tegra124-xusb.txt | 46 ++++++++++++++++++++++ >> >> >> 1 file changed, 46 insertions(+) >> >> >> create mode 100644 Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt >> >> >> >> >> >> diff --git a/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt >> >> >> new file mode 100644 >> >> >> index 0000000..6a46680 >> >> >> --- /dev/null >> >> >> +++ b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt >> >> >> @@ -0,0 +1,46 @@ >> >> >> +NVIDIA Tegra XUSB host copmlex >> >> >> +============================== >> >> >> + >> >> >> +The XUSB host complex on Tegra124 and later SoCs contains an xHCI host >> >> >> +controller and a mailbox for communication with the XUSB micro-controller. >> >> >> + >> >> >> +Required properties: >> >> >> +-------------------- >> >> >> + - compatible: For Tegra124, must contain "nvidia,tegra124-xusb". >> >> >> + Otherwise, must contain '"nvidia,<chip>-xusb", "nvidia,tegra124-xusb"' >> >> >> + where <chip> is tegra132. >> >> > >> >> > Okay. Why? >> >> >> >> Why what? This is the convention used for Tegra bindings and is also >> >> documented in Documentation/devicetree/bindings/submitting-patches.txt. >> >> See nvidia,tegra114-spi.txt and nvidia,tegra20-i2c.txt for other >> >> examples of this. >> > >> > It seems strange to me that you'd mention two specific chips in one >> > compatible string. What's the purpose of that? >> >> The Tegra maintainers can correct me if I'm wrong here, but the point >> is, I think, to future-proof the binding. There are currently no >> differences between Tegra124 and Tegra132 that need to be accounted >> for in the driver, so the driver need only match against >> "nvidia,tegra124-xusb". If a Tegra132-specific quirk comes about >> later all Tegra132 device-trees will also include the >> "nvidia,tegra132-*" compatible string, so we can simply update the >> driver without breaking DT backwards-compatibility. > > I still don't understand why you need to use them both at the same > time. Why don't you use nvidia,tegra124-* for Tegra124 and > nvidia,tegra132-* for Tegra132? The XUSB block on Tegra132 is identical to the one on Tegra124, so the Tegra132 XUSB is 'compatible' with the Tegra124 XUSB. Again, I'm just following the convention the other Tegra bindings are using... >> >> >> + - reg: Must contain register base and length for each register set listed >> >> >> + in reg-names. >> >> > >> >> > You've mentioned 2 of the cells, what about the remaining 2? >> >> >> >> The example given was for Tegra124, where there are two address cells >> >> and two size cells. >> > >> > I don't get that. How does that work? >> >> Tegra124 has a physical address space of > 4GB because of LPAE, thus a >> single cell each for address and size is not sufficient. The arm64 >> Tegra SoCs will obviously also use two address and size cells. Take a >> look at arch/arm/boot/dts/tegra124.dtsi. > > Okay, so these get shifted and &'ed into posstible 64bit addresses? Yup. -Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt new file mode 100644 index 0000000..6a46680 --- /dev/null +++ b/Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt @@ -0,0 +1,46 @@ +NVIDIA Tegra XUSB host copmlex +============================== + +The XUSB host complex on Tegra124 and later SoCs contains an xHCI host +controller and a mailbox for communication with the XUSB micro-controller. + +Required properties: +-------------------- + - compatible: For Tegra124, must contain "nvidia,tegra124-xusb". + Otherwise, must contain '"nvidia,<chip>-xusb", "nvidia,tegra124-xusb"' + where <chip> is tegra132. + - reg: Must contain register base and length for each register set listed + in reg-names. + - reg-names: Must include the following entries: + - xhci + - fpci + - ipfs + - interrupts: Must contain an interrupt for each entry in interrupt-names. + - interrupt-names: Must include the following entries: + - host + - smi + - pme + +Example: +-------- + usb@0,70090000 { + compatible = "nvidia,tegra124-xusb"; + reg = <0x0 0x70090000 0x0 0x8000>, + <0x0 0x70098000 0x0 0x1000>, + <0x0 0x70099000 0x0 0x1000>; + reg-names = "xhci", "fpci", "ipfs"; + interrupts = <GIC_SPI 39 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 40 IRQ_TYPE_LEVEL_HGIH>, + <GIC_SPI 43 IRQ_TYPE_LEVEL_HIGH>; + interrupt-names = "host", "smi", "pme"; + + usb-host { + compatible = "nvidia,tegra124-xhci"; + ... + }; + + mailbox { + compatible = "nvidia,tegra124-xusb-mbox"; + ... + }; + };
Add a binding document for the XUSB host complex on NVIDIA Tegra124 and later SoCs. The XUSB host complex includes a mailbox for communication with the XUSB micro-controller and an xHCI host-controller. Signed-off-by: Andrew Bresticker <abrestic@chromium.org> Cc: Rob Herring <robh+dt@kernel.org> Cc: Pawel Moll <pawel.moll@arm.com> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Ian Campbell <ijc+devicetree@hellion.org.uk> Cc: Kumar Gala <galak@codeaurora.org> Cc: Samuel Ortiz <sameo@linux.intel.com> Cc: Lee Jones <lee.jones@linaro.org> --- New for v7. --- .../bindings/mfd/nvidia,tegra124-xusb.txt | 46 ++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 Documentation/devicetree/bindings/mfd/nvidia,tegra124-xusb.txt