| Message ID | 20180309184417.23368-3-eric@anholt.net |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
| Series | None | expand |
Hi Eric, > Eric Anholt <eric@anholt.net> hat am 9. März 2018 um 19:44 geschrieben: > > > The VCHIQ communication channel can be provided by BCM283x and Capri > SoCs, to communicate with the VPU-side OS services. > > Signed-off-by: Eric Anholt <eric@anholt.net> > --- > > v2: VCHI->VCHIQ, dropped firmware property, added cache-line-size > v3: Dropped cache-line-size, s/vchi@/mailbox@/ > > .../devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt > > diff --git a/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt > new file mode 100644 > index 000000000000..8dd7b3a7de65 > --- /dev/null > +++ b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt > @@ -0,0 +1,16 @@ > +Broadcom VCHIQ firmware services > + > +Required properties: > + > +- compatible: Should be "brcm,bcm2835-vchiq" > +- reg: Physical base address and length of the doorbell register pair > +- interrupts: The interrupt number > + See bindings/interrupt-controller/brcm,bcm2835-armctrl-ic.txt > + > +Example: > + > +mailbox@7e00b840 { just a question: do you think this is future-proof to claim the doorbell for VCHIQ? Stefan > + compatible = "brcm,bcm2835-vchiq"; > + reg = <0x7e00b840 0xf>; > + interrupts = <0 2>; > +}; > -- > 2.16.2 > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Stefan Wahren <stefan.wahren@i2se.com> writes: > Hi Eric, > >> Eric Anholt <eric@anholt.net> hat am 9. März 2018 um 19:44 geschrieben: >> >> >> The VCHIQ communication channel can be provided by BCM283x and Capri >> SoCs, to communicate with the VPU-side OS services. >> >> Signed-off-by: Eric Anholt <eric@anholt.net> >> --- >> >> v2: VCHI->VCHIQ, dropped firmware property, added cache-line-size >> v3: Dropped cache-line-size, s/vchi@/mailbox@/ >> >> .../devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt | 16 ++++++++++++++++ >> 1 file changed, 16 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt >> >> diff --git a/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt >> new file mode 100644 >> index 000000000000..8dd7b3a7de65 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt >> @@ -0,0 +1,16 @@ >> +Broadcom VCHIQ firmware services >> + >> +Required properties: >> + >> +- compatible: Should be "brcm,bcm2835-vchiq" >> +- reg: Physical base address and length of the doorbell register pair >> +- interrupts: The interrupt number >> + See bindings/interrupt-controller/brcm,bcm2835-armctrl-ic.txt >> + >> +Example: >> + >> +mailbox@7e00b840 { > > just a question: do you think this is future-proof to claim the doorbell for VCHIQ? There are 4 and this is the only one used so far, so it seems terribly unlikely to get reused. If the firmware did for some reason decide to reuse it for something else, they'd surely go override the DT like they have in the past.
On Fri, Mar 09, 2018 at 10:44:14AM -0800, Eric Anholt wrote: > The VCHIQ communication channel can be provided by BCM283x and Capri > SoCs, to communicate with the VPU-side OS services. > > Signed-off-by: Eric Anholt <eric@anholt.net> > --- > > v2: VCHI->VCHIQ, dropped firmware property, added cache-line-size > v3: Dropped cache-line-size, s/vchi@/mailbox@/ > > .../devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt Reviewed-by: Rob Herring <robh@kernel.org> -- To unsubscribe from this list: send the line "unsubscribe devicetree" 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/soc/bcm/brcm,bcm2835-vchiq.txt b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt new file mode 100644 index 000000000000..8dd7b3a7de65 --- /dev/null +++ b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt @@ -0,0 +1,16 @@ +Broadcom VCHIQ firmware services + +Required properties: + +- compatible: Should be "brcm,bcm2835-vchiq" +- reg: Physical base address and length of the doorbell register pair +- interrupts: The interrupt number + See bindings/interrupt-controller/brcm,bcm2835-armctrl-ic.txt + +Example: + +mailbox@7e00b840 { + compatible = "brcm,bcm2835-vchiq"; + reg = <0x7e00b840 0xf>; + interrupts = <0 2>; +};
The VCHIQ communication channel can be provided by BCM283x and Capri SoCs, to communicate with the VPU-side OS services. Signed-off-by: Eric Anholt <eric@anholt.net> --- v2: VCHI->VCHIQ, dropped firmware property, added cache-line-size v3: Dropped cache-line-size, s/vchi@/mailbox@/ .../devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt