On Mon, Feb 20, 2017 at 12:28 PM, Sylwester Nawrocki <s.nawrocki@xxxxxxxxxxx> wrote: > On 02/14/2017 06:03 PM, Krzysztof Kozlowski wrote: >> On Tue, Feb 14, 2017 at 08:52:08AM +0100, Marek Szyprowski wrote: >>> During my research I found that some of the requirements for the memory >>> buffers for MFC v6+ devices were blindly copied from the previous (v5) >>> version and simply turned out to be excessive. The relaxed requirements >>> are applied by the recent patches to the MFC driver and the driver is >>> now fully functional even without the reserved memory blocks for all >>> v6+ variants. This patch removes those reserved memory nodes from all >> boards having MFC v6+ hardware block. >> >> Signed-off-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> >> --- >> >> Looks okay (for v4.12). Full bisectability depends on changes in MFC >> driver, right? I will need a stable branch/tag with driver changes >> (although recently Arnd did not want driver changes mixed with DTS...). > > I'd suggest postponing that dts cleanup patch to v4.13, everything > should continue to work properly with just the driver patches merged > and that way there will be no need to pull all 14 driver patches > into the arm-soc tree. Yes. I didn't post an update here but to make it clear - the DTS change in this case have to wait. It cannot go to a branch with the driver changes (regardless if these as pulled from outside or included as is). Best regards, Krzysztof
