On Fri, Dec 28, 2018 at 06:59:00PM +0100, Christoph Hellwig wrote: > On Fri, Dec 28, 2018 at 05:30:57PM +0000, Liviu Dudau wrote: > > On Wed, Dec 19, 2018 at 05:55:02PM +0100, Christoph Hellwig wrote: > > > As all maintainers seem to be off to their holidays already I've > > > applied this now given that I don't want to leave arm64 in broken > > > state in linux-next any longer. > > > > Hi Christoph, > > > > Talking about linux-next being broken, I found out that with > > next-20181224 the nvme driver with an HMB NVMe SSD (Toshiba RC-100) > > also fails on a RK3399 board (NanoPC T4). It works with v4.20 just fine. > > > > The reason for linking it to your patchset is that I get this on > > next-20181224 (the DMA addresses looks the same for the allocated buffers): > > Your patch looks correct. Can you send the dma_alloc_coherent > to dma_alloc_attrs switch to linux-nvme list with a proper commit log > and signoff?
Sure, but that still doesn't make nvme work. Do you have any suggestions? Best regards, Liviu -- ________________________________________________________ ________| |_______ \ | With enough courage, you can do without a reputation | / \ | -- Rhett Butler | / / |________________________________________________________| \ /__________) (_________\ _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu