Hi Peter, On Friday, 23 March 2018 10:31:53 EEST Peter Ujfalusi wrote: > On 2018-03-22 15:42, Peter Ujfalusi wrote: > > From: Tomi Valkeinen <tomi.valkeinen@xxxxxx> > > > > 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.valkeinen@xxxxxx> > > I have failed to add: > Signed-off-by: Peter Ujfalusi <peter.ujfalusi@xxxxxx> That's not mandatory. The SoB line only serves to notify that you adhere to the developer's certificate of origin as documented in Documentation/process/ submitting-patches.rst. If you haven't modified this patch, and if you intend to get it picked from the mailing list (as opposed to getting it pulled from your tree), you don't need to add your SoB. > > --- > > > > 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" -- Regards, Laurent Pinchart -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
