[lkml]   [2019]   [Nov]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] dma-mapping: treat dev->bus_dma_mask as a DMA limit
On 19/11/2019 5:00 pm, Christoph Hellwig wrote:
> On Tue, Nov 19, 2019 at 01:57:43PM +0100, Nicolas Saenz Julienne wrote:
>> Hi Rob & Christoph,
>> do you mind if I append v2 of this into my upcoming v3 RPi4 PCIe support
>> series, I didn't do it initially as I thought this was going to be a
>> contentious patch. But as it turned out better than expected, I think it
>> should go into the PCIe series. In the end it's the first explicit user of the
>> bus DMA limit.
>> Here's v2 in case you don't know what I'm talking about:
> In principle I wouldn't mind, but I think this is going to conflict
> quite badly with other changes in the dma-mapping tree (including
> yours). So I think we'll need a shared tree or I'll need to pull
> in the whole series through the dma-mapping tree if there are not
> other conflicts and the other maintainers are fine with it.

TBH I can't see it being a massive problem even if the DMA patch, driver
and DTS patch went entirely separately via the respective DMA, PCI, and
arm-soc trees in the same cycle. Bisecting over a merge window is a big
enough pain in the bum as it is, and if the worst case is that someone
trying to do that on a Pi4 has a wonky PCI controller appear for a
couple of commits, they may as well just disable that driver for their
bisection, because it wasn't there at the start so can't possibly be the
thing they're looking for regressions in ;)


 \ /
  Last update: 2019-11-19 18:18    [W:0.075 / U:3.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site