<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/drivers/gpu/drm/tegra/fb.c, branch linux-4.4.y</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=linux-4.4.y</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=linux-4.4.y'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2015-10-30T15:54:41+00:00</updated>
<entry>
<title>drm/tegra: fb: Remove gratuituous blank line</title>
<updated>2015-10-30T15:54:41+00:00</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2015-08-11T13:38:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=c8a8067f7d66bf77a0627e0b237b0b4486862a73'/>
<id>urn:sha1:c8a8067f7d66bf77a0627e0b237b0b4486862a73</id>
<content type='text'>
This was introduced by mistake in commit 0f7d9052fb70 ("drm/tegra: Use
new drm_fb_helper functions"). Remove it.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: Use new drm_fb_helper functions</title>
<updated>2015-08-06T12:12:57+00:00</updated>
<author>
<name>Archit Taneja</name>
<email>architt@codeaurora.org</email>
</author>
<published>2015-07-22T09:28:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=0f7d9052fb705e629c3f998051e835c97eb44749'/>
<id>urn:sha1:0f7d9052fb705e629c3f998051e835c97eb44749</id>
<content type='text'>
Use the newly created wrapper drm_fb_helper functions instead of calling
core fbdev functions directly. They also simplify the fb_info creation.

v2:
- Fix up error handling path in tegra_fbdev_probe

Cc: Thierry Reding &lt;thierry.reding@gmail.com&gt;
Cc: "Terje Bergström" &lt;tbergstrom@nvidia.com&gt;
Cc: Stephen Warren &lt;swarren@wwwdotorg.org&gt;

Signed-off-by: Archit Taneja &lt;architt@codeaurora.org&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
</content>
</entry>
<entry>
<title>drm/tegra: Move tegra_drm_mode_funcs to the core</title>
<updated>2015-01-27T09:14:44+00:00</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2014-11-26T12:03:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=f99142149095b3172c255fc792e8ebb84f38f182'/>
<id>urn:sha1:f99142149095b3172c255fc792e8ebb84f38f182</id>
<content type='text'>
This structure will be extended using non-framebuffer related callbacks
in subsequent patches, so it should move to a more central location.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: fb: Add error codes to error messages</title>
<updated>2014-11-13T15:18:34+00:00</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2014-11-06T13:36:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=cb10c81fdf8c77df4fffc8cb740ddf33427869df'/>
<id>urn:sha1:cb10c81fdf8c77df4fffc8cb740ddf33427869df</id>
<content type='text'>
This helps in determining what errors happened at specifics points in
the initialization sequence.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: fb: Properly release GEM objects on failure</title>
<updated>2014-11-13T15:18:33+00:00</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2014-11-06T13:33:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=b88f005ea38f29b50e55fc7eb25d92ea78a2eeab'/>
<id>urn:sha1:b88f005ea38f29b50e55fc7eb25d92ea78a2eeab</id>
<content type='text'>
When fbdev initialization fails, make sure to unreference the GEM
objects properly. Note that we can't do this in the general error
unwinding path because ownership of the GEM object references is
transferred to the framebuffer upon creation.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: fb: Do not destroy framebuffer</title>
<updated>2014-11-13T15:18:32+00:00</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2014-10-21T11:56:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=3feaf3e5ae89347a2ab3b9e994f1f3d85c09185f'/>
<id>urn:sha1:3feaf3e5ae89347a2ab3b9e994f1f3d85c09185f</id>
<content type='text'>
Drop a reference instead of directly calling the framebuffer .destroy()
callback at fbdev free time. This is necessary to make sure the object
isn't destroyed if anyone else still has a reference.

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: Add IOMMU support</title>
<updated>2014-11-13T15:14:48+00:00</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2014-06-26T19:41:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=df06b759f2cf4690fa9991edb1504ba39932b2bb'/>
<id>urn:sha1:df06b759f2cf4690fa9991edb1504ba39932b2bb</id>
<content type='text'>
When an IOMMU device is available on the platform bus, allocate an IOMMU
domain and attach the display controllers to it. The display controllers
can then scan out non-contiguous buffers by mapping them through the
IOMMU.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: Fix error handling cleanup</title>
<updated>2014-11-13T15:14:48+00:00</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2014-11-06T13:12:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=1d1e6fe9b5cd9e51c0b064b60f673a973cac38ba'/>
<id>urn:sha1:1d1e6fe9b5cd9e51c0b064b60f673a973cac38ba</id>
<content type='text'>
The DRM driver's -&gt;load() implementation didn't do a good job (no job at
all really) cleaning up on failure. Fix that by undoing any prior setup
when an error occurs. This requires a bit of rework to make it possible
to clean up fbdev midway.

This was tested by injecting errors at various points during the
initialization sequence and verifying that error cleanup didn't crash
and no memory leaked (using kmemleak).

Reported-by: Stéphane Marchesin &lt;marcheu@chromium.org&gt;
Reported-by: Sean Paul &lt;seanpaul@chromium.org&gt;
Reviewed-by: Sean Paul &lt;seanpaul@chromium.org&gt;
Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: Properly align stride for framebuffers</title>
<updated>2014-08-04T08:07:38+00:00</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2014-07-11T06:29:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=d1f3e1e0b38d49cbb996dcf0fde5b5205d12a23d'/>
<id>urn:sha1:d1f3e1e0b38d49cbb996dcf0fde5b5205d12a23d</id>
<content type='text'>
Tegra20 and Tegra30 both required the buffer line stride to be aligned
on 8 byte boundaries. Tegra114 and Tegra124 increased the alignment to
64 bytes. Introduce a parameter to specify the alignment requirements
for each display controller and round up the pitch of newly allocated
framebuffers appropriately.

Originally-by: Stéphane Marchesin &lt;marcheu@chromium.org&gt;
Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/tegra: Implement more tiling modes</title>
<updated>2014-08-04T08:07:34+00:00</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2014-06-03T12:48:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=c134f019abcfaa1cb6e07f6154e92a4f8ce8ddd8'/>
<id>urn:sha1:c134f019abcfaa1cb6e07f6154e92a4f8ce8ddd8</id>
<content type='text'>
Tegra124 supports a block-linear mode in addition to the regular pitch
linear and tiled modes. Add support for these by moving the internal
representation into a structure rather than a simple flag.

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