ter
such as dmas for console UART
Only then can the mechanism work in the generic case.
Yours,
Linus Walleij
___
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
n Arm.
I don't know about arm64 though.
Yours,
Linus Walleij
___
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
er probe. We need a strong devlink for the first category
and maybe a weak devlink for the latter category.
I don't know if this is a generic hardware property for all operating
systems so it could be a DT property such as dma-weak-dependency?
Or maybe compromize and add a linux,dma-weak-dependenc
n powered it up. I'm
on parental leave for another week but after that I could actually
try to get that machine up, but it'd be a bit late for this merge window
indeed.
BR
Linus Walleij
___
iommu mailing list
iommu@lists.linux-foundation.
arm/mach-footbridge/include/mach/dma-direct.h |8
> b/arch/arm/mach-footbridge/include/mach/memory.h |4
I think Marc Z has a Netwinder that he can test this on. Marc?
I have one too, just not much in my office because of parental leave.
Yours,
Linus Walleij
___
The new PCI driver does not need any of this stuff, so just
drop it.
Cc: iommu@lists.linux-foundation.org
Reviewed-by: Christoph Hellwig
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Pick up Christoph's Reviewed-by and add proper CC for iommu
- Resending with the rest
---
arch/
e if DMA_CMA is not available/functioning, for example, if no CMA
> area for DMA_CMA use has been setup via "cma=X". In the worst case, the
> driver cannot do it's job properly in some configurations.
Looks good to me. At least a lot better than what we have.
Reviewed-by:
On Tue, Feb 2, 2021 at 9:55 PM Rob Herring wrote:
> Running 'dt-validate -m' will flag any compatible strings missing a schema.
> Fix all the errors found in DT binding examples. Most of these are just
> typos.
>
> Cc: Stephen Boyd
> Cc: Maxime Ripard
> Cc: Chen-Yu Tsai
On Mon, Nov 16, 2020 at 5:36 PM Will Deacon wrote:
> Linus -- please can you drop this one (patch 3/3) for now, given that it's
> causing problems?
Reverted now, sorry for missing to do this earlier.
Yours,
Linus Walleij
___
iommu mailing list
Bjorn Andersson
> Cc: Joerg Roedel
> Cc: Thomas Gleixner
> Cc: Jason Cooper
> Cc: Marc Zyngier
> Cc: Linus Walleij
> Cc: Vinod Koul
> Cc: Kalle Valo
> Cc: Maulik Shah
> Cc: Lina Iyer
> Cc: Saravana Kannan
> Cc: Todd Kjos
> Cc: Greg Kroah-Hartman
>
Kconfigs selecting PINCTRL_MSM to
> also depend on QCOM_SCM || QCOM_SCM=n so that we match the
> module setting of QCOM_SCM.
>
> Cc: Catalin Marinas
> Cc: Will Deacon
> Cc: Andy Gross
> Cc: Bjorn Andersson
> Cc: Joerg Roedel
> Cc: Thomas Gleixner
> Cc: Jason Cooper
>
e.
>
> We also add PINCTRL_MSM to the arm64 defconfig to avoid
> surprises as otherwise PINCTRL_MSM/IPQ* options previously
> enabled, will be off.
>
> Cc: Catalin Marinas
> Cc: Will Deacon
> Cc: Andy Gross
> Cc: Bjorn Andersson
> Cc: Joerg Roedel
> Cc: Thomas Gleixn
rn can you have a look at this series?
BTW John I'm afraid I just merged a new QCOM subdriver so we might
need to respin this to cover all.
It's an important patch so I'll help out in rebasing it if the only problem is
that my tree is moving under your feet.
Yours,
Linus Walleij
___
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
time.
>
> New in v3:
> * Drop conditional usage of IRQCHIP_DECLARE as suggested by
>Stephen Boyd and Marc Zyngier
This patch set looks entirely reasonable to me.
Reviewed-by: Linus Walleij
Yours,
Linus Walleij
___
iommu mailing l
> Cc: Joerg Roedel
> Cc: Thomas Gleixner
> Cc: Jason Cooper
> Cc: Marc Zyngier
> Cc: Linus Walleij
> Cc: Lina Iyer
> Cc: Saravana Kannan
> Cc: Todd Kjos
> Cc: Greg Kroah-Hartman
> Cc: linux-arm-...@vger.kernel.org
> Cc: iommu@lists.linux-foundation.org
>
On Wed, Jan 16, 2019 at 11:25 AM Arnd Bergmann wrote:
> On Mon, Jan 14, 2019 at 11:27 AM Ulf Hansson wrote:
> >
> > +Linus Walleij (recently made a cleanup of the mmc bounce buffering code).
Nah it's not THAT bounce buffer.
> Linus probably knows more here, but I have a
A mask.
Possibly drivers should augment their coherent DMA mask
in accordance with "dma-ranges" from the device tree
if more finegranular masking is needed.
Reported-by: Russell King
Fixes: 4d8bde883bfb ("OF: Don't set default coherent DMA mask")
Cc: Russell King
Cc: Chris
he device can access all
of the system memory by setting the coherent DMA mask
to 0x when creating a device from the device
tree, which is crude, but seems to be what kernel v4.18
assumed.
Cc: Russell King
Cc: Christoph Hellwig
Cc: Robin Murphy
Signed-off-by: Linus Walleij
---
Russell, Chr
/of/*.
I will send you a copy of the thread.
Yours,
Linus Walleij
___
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
On Wed, Aug 29, 2018 at 8:24 AM Christoph Hellwig wrote:
> Fix warnings and regressions from requiring a dma mask.
Applied all three patches and took a few ARM systems for a test ride:
Tested-by: Linus Walleij
Yours,
Linus Walleij
___
iommu mail
the amba devices now.
Do you think we can proceed with this patch or do you want me to
revert the split back?
FWIW the platform devices have the same problem, but I know
I know, two wrongs does not make one right :/
Yours,
Linus Walleij
___
iommu
sks")
Cc: Robin Murphy
Cc: Rob Herring
Cc: Christoph Hellwig
Cc: Eric Anholt
Cc: Noralf Trønnes
Signed-off-by: Linus Walleij
---
I don't know which tree Robins patch came in from, but I assume
Christoph's, so can you carry this patch as well?
---
drivers/of/platform.c | 3 +++
1 file chang
set eliminating mach/* from shmobile.
(Usually we will just move all the headers down into the
mach-shmobile folder.)
Yours,
Linus Walleij
___
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
23 matches
Mail list logo
