On Thu, Jul 4, 2019 at 1:20 AM Joerg Roedel wrote:
>
> Hi Rob,
>
> On Tue, Jul 02, 2019 at 01:26:18PM -0700, Rob Clark wrote:
> > 1) In some cases the bootloader takes the iommu out of bypass and
> >enables the display. This is in particular a problem on the aarch64
> >laptops that exist
Hi Rob,
On Tue, Jul 02, 2019 at 01:26:18PM -0700, Rob Clark wrote:
> 1) In some cases the bootloader takes the iommu out of bypass and
>enables the display. This is in particular a problem on the aarch64
>laptops that exist these days, and modern snapdragon android devices.
>(Older
On Wed, Jul 3, 2019 at 5:42 AM Robin Murphy wrote:
>
> On 02/07/2019 21:26, Rob Clark wrote:
> > From: Rob Clark
> >
> > Avoid attaching any non-driver managed domain if the driver indicates
> > that it manages the iommu directly.
> >
> > This solves a couple problems that drm/msm + arm-smmu has
On 02/07/2019 21:26, Rob Clark wrote:
From: Rob Clark
Avoid attaching any non-driver managed domain if the driver indicates
that it manages the iommu directly.
This solves a couple problems that drm/msm + arm-smmu has with the iommu
framework:
1) In some cases the bootloader takes the iommu
From: Rob Clark
Avoid attaching any non-driver managed domain if the driver indicates
that it manages the iommu directly.
This solves a couple problems that drm/msm + arm-smmu has with the iommu
framework:
1) In some cases the bootloader takes the iommu out of bypass and
enables the
