On Mon, Oct 27, 2014 at 4:32 AM, Heiko Stübner wrote:
> Hi Daniel,
>
> Am Freitag, 24. Oktober 2014, 15:33:47 schrieb Daniel Kurtz:
>
> [...]
>
>> +static int rk_iommu_attach_device(struct iommu_domain *domain,
>> + struct device *dev)
>> +{
>> + struct rk_iommu
On Mon, Oct 27, 2014 at 4:32 AM, Heiko Stübner he...@sntech.de wrote:
Hi Daniel,
Am Freitag, 24. Oktober 2014, 15:33:47 schrieb Daniel Kurtz:
[...]
+static int rk_iommu_attach_device(struct iommu_domain *domain,
+ struct device *dev)
+{
+ struct rk_iommu
Hi Daniel,
Am Freitag, 24. Oktober 2014, 15:33:47 schrieb Daniel Kurtz:
[...]
> +static int rk_iommu_attach_device(struct iommu_domain *domain,
> + struct device *dev)
> +{
> + struct rk_iommu *iommu = dev_get_drvdata(dev->archdata.iommu);
Here I get a
Hi Daniel,
Am Freitag, 24. Oktober 2014, 15:33:47 schrieb Daniel Kurtz:
[...]
+static int rk_iommu_attach_device(struct iommu_domain *domain,
+ struct device *dev)
+{
+ struct rk_iommu *iommu = dev_get_drvdata(dev-archdata.iommu);
Here I get a null-ptr
The rk3288 has several iommus. Each iommu belongs to a single master
device. There is one device (ISP) that has two slave iommus, but that
case is not yet supported by this driver.
At subsys init, the iommu driver registers itself as the iommu driver for
the platform bus. The master devices
The rk3288 has several iommus. Each iommu belongs to a single master
device. There is one device (ISP) that has two slave iommus, but that
case is not yet supported by this driver.
At subsys init, the iommu driver registers itself as the iommu driver for
the platform bus. The master devices
On Tue, Oct 14, 2014 at 04:02:40PM +0800, Daniel Kurtz wrote:
> +static void rk_iommu_detach_device(struct iommu_domain *domain,
> +struct device *dev)
> +{
> + struct rk_iommu *iommu = dev_get_drvdata(dev->archdata.iommu);
> + struct rk_iommu_domain
On Tue, Oct 14, 2014 at 04:02:40PM +0800, Daniel Kurtz wrote:
+static void rk_iommu_detach_device(struct iommu_domain *domain,
+struct device *dev)
+{
+ struct rk_iommu *iommu = dev_get_drvdata(dev-archdata.iommu);
+ struct rk_iommu_domain *rk_domain =
On Fri, Oct 17, 2014 at 10:22:13AM +0800, Daniel Kurtz wrote:
> Gentle ping.
>
> Any more feedback on the rockchip iommu driver?
I'll look at it in more detail when the merge window is over.
Joerg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Fri, Oct 17, 2014 at 10:22:13AM +0800, Daniel Kurtz wrote:
Gentle ping.
Any more feedback on the rockchip iommu driver?
I'll look at it in more detail when the merge window is over.
Joerg
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
On Tue, Oct 14, 2014 at 4:02 PM, Daniel Kurtz wrote:
> The rk3288 has several iommus. Each iommu belongs to a single master
> device. There is one device (ISP) that has two slave iommus, but that
> case is not yet supported by this driver.
>
> At subsys init, the iommu driver registers itself
On Tue, Oct 14, 2014 at 4:02 PM, Daniel Kurtz djku...@chromium.org wrote:
The rk3288 has several iommus. Each iommu belongs to a single master
device. There is one device (ISP) that has two slave iommus, but that
case is not yet supported by this driver.
At subsys init, the iommu driver
The rk3288 has several iommus. Each iommu belongs to a single master
device. There is one device (ISP) that has two slave iommus, but that
case is not yet supported by this driver.
At subsys init, the iommu driver registers itself as the iommu driver for
the platform bus. The master devices
The rk3288 has several iommus. Each iommu belongs to a single master
device. There is one device (ISP) that has two slave iommus, but that
case is not yet supported by this driver.
At subsys init, the iommu driver registers itself as the iommu driver for
the platform bus. The master devices
14 matches
Mail list logo
