Messages in this thread | ![/](/images/icornerl.gif) | | Date | Wed, 30 Mar 2016 14:11:15 -0700 | From | Tony Lindgren <> | Subject | Re: [PATCH] ARM: OMAP2: Fix up interconnect barrier initialization for DRA7 |
| |
* Laurent Pinchart <laurent.pinchart@ideasonboard.com> [160311 08:46]: > Hi Nishanth, > > Thank you for the patch. > > On Friday 11 March 2016 10:12:28 Nishanth Menon wrote: > > The following commits: > > commit 3fa609755c11 ("ARM: omap2: restore OMAP4 barrier behaviour") > > commit f746929ffdc8 ("Revert "ARM: OMAP4: remove dead kconfig option > > OMAP4_ERRATA_I688"") and > > commit ea827ad5ffbb ("ARM: DRA7: Provide proper IO map table") > > came in around the same time, unfortunately this seem to have missed > > initializing the barrier for DRA7 platforms - omap5_map_io was reused > > for dra7 till it was split out by the last patch. barrier_init > > needs to be hence carried forward as it is valid for DRA7 family of > > processors as they are for OMAP5. > > > > Fixes: ea827ad5ffbb7 ("ARM: DRA7: Provide proper IO map table") > > Reported-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> > > Reported-by: Tomi Valkeinen <tomi.valkeinen@ti.com> > > Cc: Russell King <rmk+kernel@arm.linux.org.uk> > > Signed-off-by: Nishanth Menon <nm@ti.com> > > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Applying into omap-for-v4.6/fixes with Cc stable thanks.
Tony
| ![\](/images/icornerr.gif) |