<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/tegra/vic.c, branch linux-5.8.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.8.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.8.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2020-01-10T15:37:38Z</updated>
<entry>
<title>gpu: host1x: Rename "parent" to "host"</title>
<updated>2020-01-10T15:37:38Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-12-02T09:51:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=608f43ad27ab26700677cc4d9ead3b2d9d338a21'/>
<id>urn:sha1:608f43ad27ab26700677cc4d9ead3b2d9d338a21</id>
<content type='text'>
Rename the host1x clients' parent to "host" because that more closely
describes what it is. The parent can be confused with the parent device
in terms of the device hierarchy. Subsequent patches will add a new
member that refers to the parent in that hierarchy.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: Silence expected errors on IOMMU attach</title>
<updated>2019-12-04T12:37:44Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-12-03T16:19:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a8817489dc3e3b1910842958a3b9d9e4832e99b0'/>
<id>urn:sha1:a8817489dc3e3b1910842958a3b9d9e4832e99b0</id>
<content type='text'>
Subdevices may not be hooked up to an IOMMU via device tree. Detect such
situations and avoid confusing users by not emitting an error message.

Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: vic: Export module device table</title>
<updated>2019-12-04T12:37:27Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-12-03T16:19:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=82d73874d422b43359698f73c418a02322c886d5'/>
<id>urn:sha1:82d73874d422b43359698f73c418a02322c886d5</id>
<content type='text'>
Export the module device table to ensure the VIC compatible strings are
listed in the module's aliases table. This in turn causes the driver to
be automatically loaded on boot if VIC is the only enabled subdevice of
the logical host1x DRM device.

Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: falcon: Clarify address usage</title>
<updated>2019-10-29T14:04:36Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-10-28T12:37:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d972d6247628054f4a9f05c084a1f52de9df209d'/>
<id>urn:sha1:d972d6247628054f4a9f05c084a1f52de9df209d</id>
<content type='text'>
Rename paddr -&gt; iova and vaddr -&gt; virt to make it clearer how these
addresses are used. This is important for a subsequent patch that makes
a distinction between the physical address (physical address of the
system memory from the CPU's point of view) and the IOVA (physical
address of the system memory from the device's point of view).

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: Remove memory allocation from Falcon library</title>
<updated>2019-10-29T14:04:36Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-10-28T12:37:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=20e7dce255e96a4d58168cf48e20210146dacf23'/>
<id>urn:sha1:20e7dce255e96a4d58168cf48e20210146dacf23</id>
<content type='text'>
Having to provide allocator hooks to the Falcon library is somewhat
cumbersome and it doesn't give the users of the library a lot of
flexibility to deal with allocations. Instead, remove the notion of
Falcon "operations" and let drivers deal with the memory allocations
themselves.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: Simplify IOMMU group selection</title>
<updated>2019-10-29T14:04:34Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-10-28T12:37:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7edd7961e58d531d19758134919de13dac47bcbe'/>
<id>urn:sha1:7edd7961e58d531d19758134919de13dac47bcbe</id>
<content type='text'>
All the devices that make up the DRM device are now part of the same
IOMMU group. This simplifies the handling of the IOMMU attachment and
also avoids exhausting the number of IOMMUs available on early Tegra
SoC generations.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: Move IOMMU group into host1x client</title>
<updated>2019-10-28T10:18:37Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-02-08T13:35:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=aacdf19849734d1be5e407932228ae101ba5b92f'/>
<id>urn:sha1:aacdf19849734d1be5e407932228ae101ba5b92f</id>
<content type='text'>
Handling of the IOMMU group attachment is common to all clients, so move
the group into the client to simplify code.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: vic: Use common IOMMU attach/detach code</title>
<updated>2019-10-28T10:18:36Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-02-08T13:15:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7baa943e0bb22454887edd1fffb2d00a4b842fe5'/>
<id>urn:sha1:7baa943e0bb22454887edd1fffb2d00a4b842fe5</id>
<content type='text'>
Reuse common code to attach to or detach from an IOMMU domain.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: vic: Inherit DMA mask from host1x</title>
<updated>2019-10-28T10:18:35Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-02-08T12:10:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d5ad0e3dfe74f465a218bde84efb25c72b3e51c4'/>
<id>urn:sha1:d5ad0e3dfe74f465a218bde84efb25c72b3e51c4</id>
<content type='text'>
VIC, just like all other host1x clients, has the same addressing range
as its parent host1x device. Inherit the DMA mask to reflect that.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: vic: Skip stream ID programming without IOMMU</title>
<updated>2019-10-28T10:18:35Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-02-08T12:09:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dd631e8ac90f08c37636fe9e6d12fc7bdf7f429a'/>
<id>urn:sha1:dd631e8ac90f08c37636fe9e6d12fc7bdf7f429a</id>
<content type='text'>
If VIC is not behind an IOMMU, don't touch any of the registers related
to stream ID programming.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
</feed>
