On 10/04/18 14:33, Peter Ujfalusi wrote: > From: Tomi Valkeinen <tomi.valkei...@ti.com> > > Define unique compatible string for the DMM in DRA7xx family. > > The new compatible can be used to apply DRA7xx specific workarounds for > ERRATAs, like i878 (MPU Lockup with concurrent DMM and EMIF accesses) > > Signed-off-by: Tomi Valkeinen <tomi.valkei...@ti.com> > Signed-off-by: Peter Ujfalusi <peter.ujfal...@ti.com> > Reviewed-by: Rob Herring <r...@kernel.org> > Reviewed-by: Laurent Pinchart <laurent.pinch...@ideasonboard.com> > --- > Documentation/devicetree/bindings/arm/omap/dmm.txt | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/arm/omap/dmm.txt > b/Documentation/devicetree/bindings/arm/omap/dmm.txt > index 8bd6d0a238a8..bbbe7cdba30c 100644 > --- a/Documentation/devicetree/bindings/arm/omap/dmm.txt > +++ b/Documentation/devicetree/bindings/arm/omap/dmm.txt > @@ -8,7 +8,8 @@ translation for initiators which need contiguous dma bus > addresses. > > Required properties: > - compatible: Should contain "ti,omap4-dmm" for OMAP4 family > - Should contain "ti,omap5-dmm" for OMAP5 and DRA7x family > + Should contain "ti,omap5-dmm" for OMAP5 family > + Should contain "ti,dra7-dmm" for DRA7xx family > - reg: Contains DMM register address range (base address and > length) > - interrupts: Should contain an interrupt-specifier for DMM_IRQ. > - ti,hwmods: Name of the hwmod associated to DMM, which is typically "dmm" >
Thinking about this now, wouldn't it be better to add a DT property to enable the work-around? Or we could use soc_device_match() to figure out that this is a DRA7 SoC. Tomi -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
