Hi,
There were certainly some interesting changes discussed at the allocator
workshop during XDC this year, and I'd like to just summarise my
thoughts on it and make sure everybody is on the same page.
For those who don't know who I am or my stake in this, I'm the
maintainer of the DRM and graph
> +free_edid:
> + kfree(imxpd->edid);
> + return ret;
I have taken another look at this change idea.
Can the function call “devm_kfree(dev, imxpd)” become relevant
also at this place?
Would you like to combine it with the update suggestion
“Fix error handling for a kmemdup() call in imx_p
Hi,
In upgrading from 5.1.1 to 5.3.6, I'm seeing the following in my dmesg
when resuming from sleep, which is accompanied by a slight hang too.
Is anybody else seeing this?
Thanks,
Jason
[ 46.618138] nouveau :01:00.0: timeout
[ 46.618183] WARNING: CPU: 4 PID: 993 at
drivers/gpu/drm/nouve
Hello,
syzbot found the following crash on:
HEAD commit:8ada228a Add linux-next specific files for 20191011
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14c30b1b60
kernel config: https://syzkaller.appspot.com/x/.config?x=7cf4eed5fe42c31a
dashboard
On Sat, Oct 12, 2019 at 4:07 AM Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Sat, 12 Oct 2019 10:30:21 +0200
>
> The return value from a call of the function “kmemdup” was not checked
> in this function implementation. Thus add the corresponding error handling.
>
> Fixes: 19022aaae677df
https://bugs.freedesktop.org/show_bug.cgi?id=111989
Bug ID: 111989
Summary: Diagnosing issues with Radeon VII
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity
On Tue, 08 Oct 2019, Rasmus Villemoes wrote:
> lightness*1000 is nowhere near overflowing 32 bits, so we can just use
> an ordinary 32/32 division, which is much cheaper than the 64/32 done
> via do_div().
>
> Reviewed-by: Daniel Thompson
> Signed-off-by: Rasmus Villemoes
> ---
> drivers/video
On Tue, 08 Oct 2019, Rasmus Villemoes wrote:
> The "break-even" point for the two formulas is L==8, which is also
> what the code actually implements. [Incidentally, at that point one
> has Y=0.008856, not 0.08856].
>
> Moreover, all the sources I can find say the linear factor is 903.3
> rather
On Tue, 08 Oct 2019, Rasmus Villemoes wrote:
> For a fixed small exponent of 3, it is more efficient to simply use
> two explicit multiplications rather than calling the int_pow() library
> function: Aside from the function call overhead, its implementation
> using repeated squaring means it ends
On Tue, 08 Oct 2019, Rasmus Villemoes wrote:
> Using a power-of-2 instead of power-of-10 base makes the computations
> much cheaper. 2^16 is safe; retval never becomes more than 2^48 +
> 2^32/2. On a 32 bit platform, the very expensive 64/32 division at the
> end of cie1931() instead becomes essen
https://bugs.freedesktop.org/show_bug.cgi?id=111989
L.S.S. changed:
What|Removed |Added
Priority|not set |medium
--
You are receiving this mail because
Thierry,
Another reminder :-)
If you want me to do this, then just let me know!
Regards,
Hans
On 10/4/19 10:48 AM, Hans Verkuil wrote:
> Hi Thierry,
>
> Just a reminder: this patch hasn't been merged yet for v5.5.
>
> Thanks!
>
> Hans
>
> On 8/28/19 1:54 PM, Thierry Reding wr
On Fri, 04 Oct 2019, Jean-Jacques Hiblot wrote:
> Hi Lee,
>
> On 04/10/2019 16:39, Lee Jones wrote:
> > On Wed, 18 Sep 2019, Jean-Jacques Hiblot wrote:
> >
> > > From: Tomi Valkeinen
> > >
> > > This patch adds a led-backlight driver (led_bl), which is similar to
> > > pwm_bl except the driver
Hi Rob,
On Fri, Oct 11, 2019 at 09:50:42AM -0500, Rob Herring wrote:
> :u?wc??m5?^?㞾?}4-??z{b???r?+?׀u???ا#????ek
> ?W?J^?(???h}??-??z{b???r?Z+?jW.?\?oۊwb?
> ?v+)l?b? &??,?&??ξW???!jx w?ǫ?*'??+y?^??^?M:???r鞞֭???u??q?ky?ۊwb?
> ?v+)l?b? &??,?&?????
On Mon, 07 Oct 2019, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> While working on my other series related to gpio-backlight[1] I noticed
> that we could simplify the driver if we made the only user of platform
> data use GPIO lookups and device properties. This series tries to do
pon., 14 paź 2019 o 10:12 Lee Jones napisał(a):
>
> On Mon, 07 Oct 2019, Bartosz Golaszewski wrote:
>
> > From: Bartosz Golaszewski
> >
> > While working on my other series related to gpio-backlight[1] I noticed
> > that we could simplify the driver if we made the only user of platform
> > data u
option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url:
https://github.com/0day-ci/linux/commits/Xin-Ji/dt-bindings-drm-bridge-anx7625-MIPI-to-DP-transmitter-binding/20191014-043019
reproduce:
# apt-get install sparse
# sparse versi
Fixes: 152a82b6747f ("drm/bridge: anx7625: Add anx7625 MIPI DSI/DPI to DP
bridge driver")
Signed-off-by: kbuild test robot
---
anx7625.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/bridge/analogix/anx7625.c
b/drivers/gpu/drm/bridge/analogix/anx7625.c
On Thu, Oct 03, 2019 at 01:27:18PM +0300, Ville Syrjälä wrote:
> On Wed, Oct 02, 2019 at 03:55:10PM -0400, Rob Clark wrote:
> > On Wed, Oct 2, 2019 at 9:45 AM Ville Syrjälä
> > wrote:
> > >
> > > On Tue, Oct 01, 2019 at 02:20:55PM -0700, Jeykumar Sankaran wrote:
> > > > On 2019-09-30 03:39, Ville
On Tue, Sep 24, 2019 at 08:12:38PM +0200, Nicolas Saenz Julienne wrote:
> qoriq-mc's dpmacs DMA configuration is inherited from their parent node,
> which acts a bus in this regard. So far it maked all devices as
> dma-coherent but no dma-ranges recommendation is made.
>
> The truth is that the un
On Tue, Sep 24, 2019 at 08:12:39PM +0200, Nicolas Saenz Julienne wrote:
> The bus behind the board's PCIe core has DMA addressing limitations. Add
> an empty 'dma-ranges' property on all PCIe bus descriptions to inform
> the OF core that a translation is due further down the line.
>
> Signed-off-b
https://bugzilla.kernel.org/show_bug.cgi?id=205185
Bug ID: 205185
Summary: amdgpu compile failure
Product: Drivers
Version: 2.5
Kernel Version: 5.3.5 - 5.3.6
Hardware: All
OS: Linux
Tree: Mainline
On Fri, Oct 11, 2019 at 05:45:45PM +0800, sandy.huang wrote:
> Hi, james, ville syrjala, david,
>
> 在 2019/10/11 下午4:32, james qian wang (Arm Technology China) 写道:
> > On Fri, Oct 11, 2019 at 03:32:17PM +0800, sandy.huang wrote:
> > > 在 2019/10/11 下午3:22, james qian wang (Arm Technology China) 写道:
On Fri, Oct 11, 2019 at 04:51:13PM -0400, Lyude Paul wrote:
> a little late but: i915 does have this hack (or rather-possible_crtcs with MST
> in i915 has been broken for a while and got fixed, but had to get reverted
> because of this issue), it's where this originally came from.
Hm since this is
On Fri, Oct 11, 2019 at 11:36:33AM +0200, Johan Hovold wrote:
> On Thu, Oct 10, 2019 at 03:50:43PM +0200, Daniel Vetter wrote:
> > On Thu, Oct 10, 2019 at 03:13:29PM +0200, Johan Hovold wrote:
> > > Two old USB drivers had a bug in them which could lead to memory leaks
> > > if an interrupted proce
On Thu, Oct 10, 2019 at 04:48:08PM -0400, Sean Paul wrote:
> From: Sean Paul
>
> *Record scratch* You read that subject correctly, I bet you're wondering
> how we got here. At least hear me out before you flame :-)
>
> For a long while now, we (ChromeOS) have been struggling getting any
> value
Hi,
> - doing this over dma-buf means we can only use this for the ww_mutx
> dance, not for anything else. Which means we need another layer on top
> for shared execbuf utils (which Gerd has started looking into, but I
> felt like not quite the right approach yet in his first draft series)
On Fri, Oct 11, 2019 at 05:43:09AM +, james qian wang (Arm Technology
China) wrote:
> Add a new helper function drm_color_ctm_s31_32_to_qm_n() for driver to
> convert S31.32 sign-magnitude to Qm.n 2's complement that supported by
> hardware.
>
> Signed-off-by: james qian wang (Arm Technology
> -Original Message-
> From: Ville Syrjälä
> Sent: Friday, October 4, 2019 10:24 PM
> To: Lin, Wayne
> Cc: dri-devel@lists.freedesktop.org; amd-...@lists.freedesktop.org; Li, Sun
> peng (Leo) ; Kazlauskas, Nicholas
>
> Subject: Re: [PATCH] drm/drm_edid: correct VIC and HDMI_VIC under H
On Fri, Oct 11, 2019 at 07:55:36PM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 11.10.19 um 19:09 schrieb Daniel Stone:
> > Hi Rohan,
> >
> > On Fri, 11 Oct 2019 at 15:30, Rohan Garg wrote:
> > > DRM_IOCTL_DUMB_SET_LABEL lets you label GEM objects, making it
> > > easier to debug issues in usersp
On Sun, 13 Oct 2019, Changbin Du wrote:
> The 'functions' directive is not only for functions, but also works for
> structs/unions. So the name is misleading. This patch renames it to
> 'specific', so now we have export/internal/specific directives to limit
> the functions/types to be included in
On Fri, Oct 11, 2019 at 04:30:09PM +0200, Rohan Garg wrote:
> DRM_IOCTL_DUMB_SET_LABEL lets you label GEM objects, making it
> easier to debug issues in userspace applications.
>
> Changes in v2:
> - Hoist the IOCTL up into the drm_driver framework
>
> Changes in v3:
> - Introduce a drm_gem_s
Hi Andrew,
On Wed, Oct 09, 2019 at 02:27:15PM -0400, Andrew F. Davis wrote:
> The CMA driver that registers these nodes will have to be expanded to
> export them using this framework as needed. We do something similar to
> export SRAM nodes:
>
> https://lkml.org/lkml/2019/3/21/575
>
> Unlike the
On Fri, Oct 11, 2019 at 07:25:02PM +0200, Daniel Vetter wrote:
> On Fri, Oct 11, 2019 at 12:56 PM Brian Starkey wrote:
> >
> > Hi,
> >
> > On Fri, Oct 11, 2019 at 11:14:43AM +0200, Neil Armstrong wrote:
> > > Hi Brian,
> > >
> > > On 11/10/2019 10:41, Brian Starkey wrote:
>
> > > > Are you sure t
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #162 from line...@xcpp.org ---
Created attachment 145730
--> https://bugs.freedesktop.org/attachment.cgi?id=145730&action=edit
Freeze/Black screen/Crash on 5.3.6
Apologies, I have been on vacation and thus away from my main System.
On Sun, Oct 13, 2019 at 11:09:09PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:8ada228a Add linux-next specific files for 20191011
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1423a87f60
> kernel config
Convert the STM32 display binding to DT schema format using json-schema.
Split the original bindings in two yaml files:
- one for display controller (ltdc)
- one for DSI controller
Signed-off-by: Benjamin Gaignard
---
changes in v3:
- use (GPL-2.0-only OR BSD-2-Clause) license
changes in v2:
- u
On Sun, Oct 13, 2019 at 07:49:08PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:8ada228a Add linux-next specific files for 20191011
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=14c30b1b60
> kernel config
On Mon, Oct 14, 2019 at 09:11:17AM +, Brian Starkey wrote:
> On Fri, Oct 11, 2019 at 07:25:02PM +0200, Daniel Vetter wrote:
> > On Fri, Oct 11, 2019 at 12:56 PM Brian Starkey
> > wrote:
> > >
> > > Hi,
> > >
> > > On Fri, Oct 11, 2019 at 11:14:43AM +0200, Neil Armstrong wrote:
> > > > Hi Bria
On Monday, October 14, 2019 12:17 PM, Daniel Vetter wrote:
> Oleg, will you be looking at this? With the reproducer and full drm
> debugging enabled it shouldn't be too hard to figure out what's going on
> heere ...
Oleg is no longer working at Intel. I don't think he monitors dri-devel
anymore.
> -Original Message-
> From: Ville Syrjala
> Sent: Friday, October 4, 2019 10:19 PM
> To: dri-devel@lists.freedesktop.org
> Cc: intel-...@lists.freedesktop.org; Lin, Wayne
> Subject: [PATCH 4/4] drm/edid: Prep for HDMI VIC aspect ratio (WIP)
>
> From: Ville Syrjälä
>
> I think this s
https://bugzilla.kernel.org/show_bug.cgi?id=205169
--- Comment #10 from Pierre-Eric Pelloux-Prayer
(pierre-eric.pelloux-pra...@amd.com) ---
"git bisect" identifies this commit as the problematic one: 617089d5837a
("drm/amd/display: revert wait in pipelock").
Reverting this commit on top of amd-s
Op 14-10-2019 om 11:16 schreef Daniel Vetter:
> On Sun, Oct 13, 2019 at 11:09:09PM -0700, syzbot wrote:
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:8ada228a Add linux-next specific files for 20191011
>> git tree: linux-next
>> console output: https://syzkaller.a
On Fri, Oct 11, 2019 at 08:26:53AM +, Mihail Atanassov wrote:
> Hi James,
>
> On Friday, 11 October 2019 06:45:27 BST james qian wang (Arm Technology
> China) wrote:
> > Add a new helper function drm_color_ctm_s31_32_to_qm_n() for driver to
> > convert S31.32 sign-magnitude to Qm.n 2's comple
https://bugs.freedesktop.org/show_bug.cgi?id=111986
--- Comment #7 from Pierre-Eric Pelloux-Prayer
---
Thanks for your bug report.
It would be really helpful to have the content of dmesg when your system hangs.
You can get it from another computer using ssh or you could extract it from
/var/log
Hi Lowry,
For future reference, it's quite useful for the reader if you put the
patch version in the subject line (e.g. [PATCH v3] ...) :).
On Saturday, 12 October 2019 07:50:46 BST Lowry Li (Arm Technology China) wrote:
> Set color_depth according to connector->bpc.
>
> Changes since v1:
> -
On Mon, Oct 14, 2019 at 10:56:05AM +0200, Daniel Vetter wrote:
> On Fri, Oct 11, 2019 at 05:43:09AM +, james qian wang (Arm Technology
> China) wrote:
> > Add a new helper function drm_color_ctm_s31_32_to_qm_n() for driver to
> > convert S31.32 sign-magnitude to Qm.n 2's complement that suppor
On Mon, 2019-10-14 at 16:28 +0800, Shawn Guo wrote:
> On Tue, Sep 24, 2019 at 08:12:38PM +0200, Nicolas Saenz Julienne wrote:
> > qoriq-mc's dpmacs DMA configuration is inherited from their parent node,
> > which acts a bus in this regard. So far it maked all devices as
> > dma-coherent but no dma-
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #93 from Pierre-Eric Pelloux-Prayer
---
Created attachment 145734
--> https://bugs.freedesktop.org/attachment.cgi?id=145734&action=edit
sdma read delay
Hi all,
Here's a new patch that should help with sdma issues.
This is not a
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #94 from Marko Popovic ---
(In reply to Pierre-Eric Pelloux-Prayer from comment #93)
> Created attachment 145734 [details] [review]
> sdma read delay
>
> Hi all,
>
> Here's a new patch that should help with sdma issues.
>
> This i
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #163 from Tom B ---
Gargoyle, linedot, can you confirm whether this crash is with both patches
applied?
I'm still on 5.3.1 patched and haven't had a single crash.
--
You are receiving this mail because:
You are the assignee for th
On Monday, 14 October 2019 10:43:39 BST james qian wang (Arm Technology China)
wrote:
> On Fri, Oct 11, 2019 at 08:26:53AM +, Mihail Atanassov wrote:
> > Hi James,
> >
> > On Friday, 11 October 2019 06:45:27 BST james qian wang (Arm Technology
> > China) wrote:
> > > Add a new helper functio
On Mon, Oct 14, 2019 at 11:39 AM syzbot
wrote:
>
> Op 14-10-2019 om 11:16 schreef Daniel Vetter:
> > On Sun, Oct 13, 2019 at 11:09:09PM -0700, syzbot wrote:
> >> Hello,
> >>
> >> syzbot found the following crash on:
> >>
> >> HEAD commit:8ada228a Add linux-next specific files for 20191011
> >>
On Sun, Oct 13, 2019 at 10:32:18PM +0530, Jagan Teki wrote:
> On Mon, Oct 7, 2019 at 3:01 PM Maxime Ripard wrote:
> >
> > On Sat, Oct 05, 2019 at 07:49:08PM +0530, Jagan Teki wrote:
> > > The MIPI DSI controller in Allwinner A64 is similar to A33.
> > >
> > > But unlike A33, A64 doesn't have DSI_S
On Mon, Oct 14, 2019 at 12:00:25PM +0200, Nicolas Saenz Julienne wrote:
> On Mon, 2019-10-14 at 16:28 +0800, Shawn Guo wrote:
> > On Tue, Sep 24, 2019 at 08:12:38PM +0200, Nicolas Saenz Julienne wrote:
> > > qoriq-mc's dpmacs DMA configuration is inherited from their parent node,
> > > which acts a
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #164 from line...@xcpp.org ---
(In reply to Tom B from comment #163)
> Gargoyle, linedot, can you confirm whether this crash is with both patches
> applied?
>
> I'm still on 5.3.1 patched and haven't had a single crash.
For 5.3.1 I'
On Mon, Oct 7, 2019 at 4:27 PM Maxime Ripard wrote:
>
> On Sat, Oct 05, 2019 at 07:49:12PM +0530, Jagan Teki wrote:
> > Add MIPI DSI pipeline for Allwinner A64.
> >
> > - dsi node, with A64 compatible since it doesn't support
> > DSI_SCLK gating unlike A33
> > - dphy node, with A64 compatible wi
On Wed, Aug 14, 2019 at 12:45:05PM +0200, Dariusz Marcinkiewicz wrote:
> Use the new cec_notifier_conn_(un)register() functions to
> (un)register the notifier for the HDMI connector, and fill in
> the cec_connector_info.
>
> Changes since v4:
> - only create a CEC notifier for HDMI connector
https://bugs.freedesktop.org/show_bug.cgi?id=110139
Martin Peres changed:
What|Removed |Added
Component|General |DRM/other
--
You are receiving this mai
This adds support for the ARM Framebuffer Compression decoders found
in the Amlogic GXM and G12A SoCs.
The Amlogic GXM and G12A AFBC decoder are totally different, the GXM only
handling only the AFBC v1.0 modes and the G12A decoder handling the
AFBC v1.2 modes.
The G12A AFBC decoder is an externa
This adds all the OSD configuration plumbing to support the AFBC decoders
path to display of the OSD1 plane.
The Amlogic GXM and G12A AFBC decoders are integrated very differently.
The Amlogic GXM has a direct output path to the OSD1 VIU pixel input,
because the GXM AFBC decoder seem to be a cust
This adds the driver for the ARM Framebuffer Compression decoders found
in the Amlogic GXM and G12A SoCs.
The Amlogic GXM and G12A AFBC decoder are totally different, the GXM only
handling only the AFBC v1.0 modes and the G12A decoder handling the
AFBC v1.2 modes.
The G12A AFBC decoder is an exte
When using an AFBC encoded frame, the AFBC Decoder must be resetted,
configured and enabled at each vsync IRQ.
To leave time for that, use the maximum lines hold time to give time
for AFBC setup and avoid visual glitches.
Signed-off-by: Neil Armstrong
---
drivers/gpu/drm/meson/meson_viu.c | 2 +
Also store the framebuffer width in the private common struct
to be used by the AFBC decoder module driver when committing the AFBC
plane.
Signed-off-by: Neil Armstrong
---
drivers/gpu/drm/meson/meson_drv.h | 1 +
drivers/gpu/drm/meson/meson_plane.c | 1 +
2 files changed, 2 insertions(+)
dif
Add the registers used to program the ARM Framebuffer Compression decoders
used in the Amlogic GXM and G12A SoCs families.
This also adds the routing and pipeline configuration bits and registers
needed to enable AFBC support.
Signed-off-by: Neil Armstrong
---
drivers/gpu/drm/meson/meson_regist
The Amlogic G12A AFBC Decoder pixel input need to be routed diferently
than the Amlogic GXM AFBC decoder, this adds support for routing the
VIU OSD1 pixel source to the AFBC "Mali Unpack" module.
This "Mali Unpack" module is also configured with a static RGBA mapping
for now until we support more
Finally, setup the VIU registers and start the AFBC decoder at each
vsync IRQ to support displaying AFBC encoded buffers on Amlogic GXM
and G12A SoCs.
Since the DRM core will stop the vsync IRQ after a few interrupts,
we need to keep the IRQ enabled while using the AFBC decoder.
Signed-off-by: Ne
Hi Robert,
Sorry it took me so long to have a closer look at this patchset.
I will definitely merge part of it, but this particular patch actually
breaks i.MX 7. I have vertical stripes on my display with this patch
applied (using Weston with DRM backend). Not sure why this exactly
happens, from
https://bugs.freedesktop.org/show_bug.cgi?id=110139
bastiborch...@gmx.net changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=100389
--- Comment #2 from Martin Peres ---
Seems unrelated to the kernel and would have a better place in a compositor or
in mesa.
If you disagree, please file a bug in https://gitlab.freedesktop.org/drm/misc.
--
You are receiving this mail because
From: Thierry Reding
None of the host1x clients have any limitations on the DMA segment size,
so don't pretend that they do.
Signed-off-by: Thierry Reding
---
drivers/gpu/host1x/bus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/host1x/bus.c b/drivers/gpu/hos
From: Thierry Reding
Signed-off-by: Thierry Reding
---
drivers/gpu/host1x/intr.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/host1x/intr.c b/drivers/gpu/host1x/intr.c
index 26f3c741d085..9245add23b5d 100644
--- a/drivers/gpu/host1x/intr.c
+++ b/drivers/gpu/host1x/intr.c
@@ -1
From: Thierry Reding
If VIC is not behind an IOMMU, don't touch any of the registers related
to stream ID programming.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/vic.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/tegra/vic.c b/drivers
From: Thierry Reding
A struct device doesn't carry much information that a channel might be
interested in, but the client very much does. Request channels for the
clients rather than their parent devices and store a pointer to them
in order to have that information available when needed.
Signed-
From: Thierry Reding
Some cleanups and minor improvements, nothing exciting here. However,
these prepare the way for some larger rework that will convert explicit
IOMMU API usage to the DMA API, which optionally can be backed by an
IOMMU.
Thierry
Thierry Reding (14):
gpu: host1x: Do not limit
From: Thierry Reding
The driver-specific messages should use the DRM_UT_DRIVER category so
that they can be properly filtered.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/drm.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/tegra/drm.c b
From: Thierry Reding
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
---
drivers/gpu/drm/tegra/vic.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/gpu/dr
From: Thierry Reding
The display controllers and VIC don't have any limitations on the
DMA segment size. Inherit the DMA parameters from the parent device,
which also doesn't have any such limitations.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dc.c | 9 +
drivers/gpu/drm
From: Thierry Reding
It's technically not required to explicitly initialize the fields that
will be zero by default, but it's easier to read these structures if
they are all initialized uniformly.
Signed-off-by: Thierry Reding
---
drivers/gpu/host1x/dev.c | 12
1 file changed, 12
From: Thierry Reding
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
---
drivers/gpu/drm/tegra/dc.c | 9 -
drivers/gpu/drm/tegra/dc.h | 2 --
drivers/gpu/drm/tegra/drm.c | 22 +
From: Thierry Reding
Reuse common code to attach to or detach from an IOMMU domain.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/vic.c | 27 ---
1 file changed, 8 insertions(+), 19 deletions(-)
diff --git a/drivers/gpu/drm/tegra/vic.c b/drivers/gpu/drm/tegra
From: Thierry Reding
The address can refer to either physical memory or IO virtual memory.
If referring to IO virtual memory, there will always be an associated
physical memory address. Rename this variable to "iova" to clarify in
all cases that this is the IO virtual memory, which in the absence
From: Thierry Reding
Instead of manually creating the SG table for a discontiguous buffer,
use the existing sg_alloc_table_from_pages(). Note that this is not safe
to be used with the ARM DMA/IOMMU integration code because that will not
ensure that the whole buffer is mapped contiguously. Dependi
From: Thierry Reding
Rather than manually creating an SG table in an incorrect way, let the
standard dma_get_sgtable() function do it.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/gem.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/tegra/g
From: Thierry Reding
When an importer wants to map a DMA-BUF, make sure to always actually
map it, irrespective of whether the buffer is contiguous or not.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/gem.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/dr
The variable 'dev' is no longer used and the compiler rightly complains
that it should be removed.
../drivers/gpu/drm/drm_dp_mst_topology.c: In function
‘drm_atomic_get_mst_topology_state’:
../drivers/gpu/drm/drm_dp_mst_topology.c:4187:21: warning: unused variable
‘dev’ [-Wunused-variable]
str
On 2019-08-29 13:30, Robert Chiras wrote:
> Some of the registers, like LCDC_CTRL, CTRL2_OUTSTANDING_REQS and
> CTRL1_RECOVERY_ON_UNDERFLOW needs to be properly cleared/initialized
> for a better start and stop routine.
This patch uses CTRL2_OUTSTANDING_REQS which is only introduced in the
next p
On 10/13/19 2:05 PM, Scott Anderson wrote:
(Sorry to CCs for spam, I made an error in my first posting)
Hi,
There were certainly some interesting changes discussed at the allocator
workshop during XDC this year, and I'd like to just summarise my
thoughts on it and make sure everybody is on the
On 2019-08-29 13:30, Robert Chiras wrote:
> Use BIT(x) and GEN_MASK(h, l) for better representation the inside of
> various registers.
>
> Signed-off-by: Robert Chiras
> Tested-by: Guido Günther
> ---
> drivers/gpu/drm/mxsfb/mxsfb_regs.h | 151
> ++---
> 1 file
https://bugs.freedesktop.org/show_bug.cgi?id=105051
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=91481
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=102972
Martin Peres changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=12431
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=100375
Martin Peres changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=25258
Martin Peres changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=21462
Martin Peres changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=8874
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=89549
Martin Peres changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=8896
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=10975
Martin Peres changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
1 - 100 of 264 matches
Mail list logo
