On 2019/1/7, 9:41 PM, "Brian Starkey" wrote:
Hi James,
A few minor comments.
On Mon, Dec 24, 2018 at 08:58:46AM +, james qian wang (Arm Technology
China) wrote:
> D71 consists of a number of Register Blocks, every Block controls a
> specific HW function, ever
Please disregard. This patch can't be submitted stand-alone, I will
re-submit as part of a v6 of "imx-media: Fixes for interlaced capture"
patchset.
Steve
On 12/14/18 3:46 PM, Steve Longerbeam wrote:
The function ipu_csi_init_interface() was inverting the F-bit for
NTSC case, in the CCIR_COD
One of the more common cases of allocation size calculations is finding the
size of a structure that has a zero-sized array at the end, along with memory
for some number of elements for that array. For example:
struct foo {
int stuff;
void *entry[];
};
instance = kzalloc(sizeof(struct foo
> Subject: [PATCH 2/2] drm/msm/gpu: fix building without debugfs
>
> When debugfs is disabled, but coredump is turned on, the adreno driver fails
> to
> build:
>
> drivers/gpu/drm/msm/adreno/a3xx_gpu.c:460:4: error: 'struct msm_gpu_funcs'
> has no member named 'show'
>.show = adreno_show,
>
Dear Maarten,
Thank you very much for the quick response.
On 01/08/19 16:37, Maarten Lankhorst wrote:
> Op 08-01-2019 om 16:07 schreef Paul Menzel:
>> Building Linux 5.0-rc1 fails with the errors below. Please find the
>> configuration file attached.
>>
>> ```
>> $ make -j120
>> […]
>> drivers/
I wanted to test-compile etnaviv on x86 after making a tree-wide change
to it. Unfortunately, Kconfig has a bad dependency, so I couldn't.
Signed-off-by: Matthew Wilcox
diff --git a/drivers/gpu/drm/etnaviv/Kconfig b/drivers/gpu/drm/etnaviv/Kconfig
index 041a77e400d4..342591a1084e 100644
--- a/
Signed-off-by: Matthew Wilcox
diff --git a/MAINTAINERS b/MAINTAINERS
index 32d76a90..44888eb121d8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5141,7 +5141,7 @@ DRM DRIVERS FOR VIVANTE GPU IP
M: Lucas Stach
R: Russell King
R: Christian Gmeiner
-L: etna...@lists.freede
Move mipi_dsi_dcs_set_display_off() from innolux_panel_disable()
to innolux_panel_unprepare(), so they are consistent with
innolux_panel_enable() and innolux_panel_prepare().
This also fixes some mode check and irq timeout issue in MTK dsi code.
Since some dsi code (e.g. mtk_dsi) have following c
To support interlaced scan with planar formats, cpmem SLUV must
be programmed with the correct chroma line stride. For full and
partial planar 4:2:2 (YUV422P, NV16), chroma line stride must
be doubled. For full and partial planar 4:2:0 (YUV420, YVU420, NV12),
chroma line stride must _not_ be double
Dear Linux folks,
Building Linux 5.0-rc1 fails with the errors below. Please find the
configuration file attached.
```
$ make -j120
[…]
drivers/gpu/vga/vgaarb.c: In function ‘__vga_tryget’:
drivers/gpu/vga/vgaarb.c:286:14: error: ‘PCI_VGA_STATE_CHANGE_DECODES’
undeclared (first use in this func
Hi all,
Commit e845f099f1c6 ("drm/i915/dsc: Add Per connector debugfs node for
DSC support/enable") causes a Clang warning:
drivers/gpu/drm/i915/i915_debugfs.c:4961:17: warning: address of array
'intel_dp->dsc_dpcd' will always evaluate to 'true' [-Wpointer-bool-conversion]
if (i
The primecell.txt and cpus.txt files were converted into YAML. This
patch updates old references with new ones.
Fixes: d3c207eeb905 ("dt-bindings: arm: Convert primecell binding to
json-schema")
Fixes: 672951cbd1b7 ("dt-bindings: arm: Convert cpu binding to json-schema")
Signed-off-by: Otto Sabar
The function ipu_csi_init_interface() was inverting the F-bit for
NTSC case, in the CCIR_CODE_1/2 registers. The result being that
for NTSC bottom-top field order, the CSI would swap fields and
capture in top-bottom order.
Instead, base field swap on the field order of the input to the CSI,
and th
While trying to temporarily hide a plane, one thing that was attempted
was to call (from libdrm)
drmModeSetPlane(fd, plane_id, crtc_id, fb_id, 0,
0, 0, 0, 0, 0, 0, 0, 0);
This call causes a pair of "Division by zero in kernel." messages. Kill
those messages, but pr
Le mar. 8 janv. 2019 à 20:30, Sam Ravnborg a écrit :
I just notice the a typo in the title of the commit message reply ->rely ?
>
> drmP.h was the only header file in the past and a lot
> of files rely on that drmP.h defines everything.
> The goal is to one day to delete drmP.h and
> as a step to
Hi Tomi,
On 03.01.2019 12:59, Tomi Valkeinen wrote:
> Hi,
>
> We have TC358867 on our board, which I believe is almost identical to
> TC358767. We're using it with a DP connector instead of eDP with a fixed
> panel.
>
> I have tested these patches only on TI's 4.14 based kernel, as
> unfortunately
On Tue, Jan 08, 2019 at 11:59:30AM -0300, Ezequiel Garcia wrote:
> Move the code around so the driver is probed the bus
> .probe and removed from the bus .remove callbacks.
> This commit is just a cleanup and shouldn't affect
> functionality.
That one works.
thanks,
Gerd
__
On Tue, Jan 08, 2019 at 10:21:52AM -0600, Gustavo A. R. Silva wrote:
> One of the more common cases of allocation size calculations is finding the
> size of a structure that has a zero-sized array at the end, along with memory
> for some number of elements for that array. For example:
>
> struct f
Hi Andrzej,
On 09/01/19 10:22, Andrzej Hajda wrote:
> Hi Tomi,
>
> On 03.01.2019 12:59, Tomi Valkeinen wrote:
>> Hi,
>>
>> We have TC358867 on our board, which I believe is almost identical to
>> TC358767. We're using it with a DP connector instead of eDP with a fixed
>> panel.
>>
>> I have teste
+CC: Rafael J. Wysocki
On 08.01.2019 16:07, Russell King - ARM Linux wrote:
> On Tue, Jan 08, 2019 at 03:33:54PM +0100, Andrzej Hajda wrote:
>> On 08.01.2019 14:21, Russell King - ARM Linux wrote:
>>> On Tue, Jan 08, 2019 at 01:27:56PM +0100, Andrzej Hajda wrote:
On 08.01.2019 12:38, Russell
On 2019-01-08 8:25 p.m., Sasha Levin wrote:
> From: Nicholas Kazlauskas
>
> [ Upstream commit 520f08df45fbe300ed650da786a74093d658b7e1 ]
>
> When variable refresh rate is active [...]
Variable refresh rate (FreeSync) support is only landing in 5.0,
therefore this fix isn't needed in older kerne
On Wed, Jan 9, 2019 at 10:13 AM Andrzej Hajda wrote:
>
> +CC: Rafael J. Wysocki
>
> On 08.01.2019 16:07, Russell King - ARM Linux wrote:
> > On Tue, Jan 08, 2019 at 03:33:54PM +0100, Andrzej Hajda wrote:
> >> On 08.01.2019 14:21, Russell King - ARM Linux wrote:
> >>> On Tue, Jan 08, 2019 at 01:27
On Wed, Jan 09, 2019 at 10:24:01AM +0100, Rafael J. Wysocki wrote:
> On Wed, Jan 9, 2019 at 10:13 AM Andrzej Hajda wrote:
> >
> > +CC: Rafael J. Wysocki
> >
> > On 08.01.2019 16:07, Russell King - ARM Linux wrote:
> > > On Tue, Jan 08, 2019 at 03:33:54PM +0100, Andrzej Hajda wrote:
> > >> On 08.0
On 1/9/2019 10:50 AM, Doug Anderson wrote:
...but in the meantime Rajendra has had to change his bindings, so you
still need to spin this to account for Rajendra's v9 bindings [2].
Specifically you need to make changes like:
- compatible = "operating-points-v2-qco
https://bugs.freedesktop.org/show_bug.cgi?id=109246
--- Comment #12 from Michel Dänzer ---
(In reply to tme from comment #9)
> Setting amdgpu.dc=1 on 4.15.18 and 4.16.18 does not reproduce the problem.
> It does, however, reproduce on 4.17.19.
Can you bisect between 4.16.18 and 4.17.19?
(I see
The videomode.h header inclusion is an artifact from the patches
development, remove it.
Suggested-by: Sakari Ailus
Signed-off-by: Maxime Ripard
---
include/linux/phy/phy-mipi-dphy.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/phy/phy-mipi-dphy.h
b/include/linux/phy/phy-
Now that we have everything we need in the phy framework to allow to tune
the phy parameters, let's convert the Cadence DSI bridge to that API
instead of creating a ad-hoc driver for its phy.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/bridge/Kconfig| 1 +-
drivers/gpu/drm/bridge/cdns
The lanes parameter is not solely about the number of lanes, but it also
carries the fact that those are the first lanes in use during the
transmission.
It was implicit so far, so make sure it's explicit now.
Suggested-by: Sakari Ailus
Signed-off-by: Maxime Ripard
---
include/linux/phy/phy-mip
The Cadence D-PHY bindings was defined as part of the DSI block so far.
However, since it's now going to be a separate driver, we need to move the
binding to a file of its own.
Signed-off-by: Maxime Ripard
---
Documentation/devicetree/bindings/display/bridge/cdns,dsi.txt | 21 +---
Documenta
Hi,
Here is a set of patches to allow the phy framework consumers to test and
apply runtime configurations.
This is needed to support more phy classes that require tuning based on
parameters depending on the current use case of the device, in addition to
the power state management already provide
The current configuration of the DSI bridge and its associated D-PHY is
intertwined. In order to ease the future conversion to the phy framework
for the D-PHY part, let's split the configuration in two.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/bridge/cdns-dsi.c | 96 +
Now that we have everything in place in the PHY framework to deal in a
generic way with MIPI D-PHY phys, let's convert our PHY driver and its
associated DSI driver to that new API.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/sun4i/Kconfig | 11 +-
drivers/gpu/drm/sun4i/Makefile
Cadence has designed a D-PHY that can be used by the, currently in tree,
DSI bridge (DRM), CSI Transceiver and CSI Receiver (v4l2) drivers.
Only the DSI driver has an ad-hoc driver for that phy at the moment, while
the v4l2 drivers are completely missing any phy support. In order to make
that phy
The Init and wakeup D-PHY parameters are in the micro/milliseconds range,
putting the values real close to the types limits if they were in
picoseconds.
Move them to microseconds which should be better fit.
Suggested-by: Sakari Ailus
Signed-off-by: Maxime Ripard
---
drivers/phy/phy-core-mipi-d
Now that our MIPI D-PHY driver has been converted to the phy framework,
let's move it into the drivers/phy directory.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/sun4i/Kconfig | 10 +-
drivers/gpu/drm/sun4i/Makefile | 1 +-
drivers/gpu/drm/sun4i/sun6i_mipi_dphy
Am Dienstag, den 08.01.2019, 12:50 -0800 schrieb Matthew Wilcox:
> > Signed-off-by: Matthew Wilcox
Thanks, applied to etnaviv/next.
Regards,
Lucas
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 32d76a90..44888eb121d8 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5141,7 +5141,7 @@ D
Am Dienstag, den 08.01.2019, 12:43 -0800 schrieb Matthew Wilcox:
> I wanted to test-compile etnaviv on x86 after making a tree-wide change
> to it. Unfortunately, Kconfig has a bad dependency, so I couldn't.
>
> Signed-off-by: Matthew Wilcox
I think we even want to relax this some more in the f
Hi Benjamin.
On Wed, Jan 09, 2019 at 09:21:39AM +0100, Benjamin Gaignard wrote:
> Le mar. 8 janv. 2019 à 20:30, Sam Ravnborg a écrit :
> I just notice the a typo in the title of the commit message reply ->rely ?
Randy already told me this, but I missed that in the update.
Will fix in v4 if this
Am Mittwoch, den 09.01.2019, 11:12 +0200 schrieb Tomi Valkeinen:
> Hi Andrzej,
>
> On 09/01/19 10:22, Andrzej Hajda wrote:
> > Hi Tomi,
> >
> > On 03.01.2019 12:59, Tomi Valkeinen wrote:
> > > Hi,
> > >
> > > We have TC358867 on our board, which I believe is almost identical to
> > > TC358767. W
On Tue, Jan 08, 2019 at 12:25:07PM +0100, Gerd Hoffmann wrote:
> Conversion to atomic modesetting, step one.
> Add atomic crtc helper callbacks.
>
> Signed-off-by: Gerd Hoffmann
> ---
> drivers/gpu/drm/bochs/bochs_kms.c | 25 +
> 1 file changed, 25 insertions(+)
>
> diff
On Tue, Jan 08, 2019 at 12:25:19PM +0100, Gerd Hoffmann wrote:
> The buffer object must be reserved before calling
> ttm_bo_validate for pinning/unpinning.
>
> Signed-off-by: Gerd Hoffmann
Seems a bit a bisect fumble in your series here: legacy kms code reserved
the ttm bo before calling boch_bo
On 09.01.2019 10:51, Lucas Stach wrote:
> Am Mittwoch, den 09.01.2019, 11:12 +0200 schrieb Tomi Valkeinen:
>> Hi Andrzej,
>>
>> On 09/01/19 10:22, Andrzej Hajda wrote:
>>> Hi Tomi,
>>>
>>> On 03.01.2019 12:59, Tomi Valkeinen wrote:
Hi,
We have TC358867 on our board, which I believe i
On Tue, Jan 08, 2019 at 12:31:36PM +, Peter Rosin wrote:
> While trying to temporarily hide a plane, one thing that was attempted
> was to call (from libdrm)
>
> drmModeSetPlane(fd, plane_id, crtc_id, fb_id, 0,
> 0, 0, 0, 0, 0, 0, 0, 0);
>
> This call causes a pair
Am 07.01.19 um 20:47 schrieb Grodzovsky, Andrey:
On 01/07/2019 09:13 AM, Christian König wrote:
Am 03.01.19 um 18:42 schrieb Grodzovsky, Andrey:
On 01/03/2019 11:20 AM, Grodzovsky, Andrey wrote:
On 01/03/2019 03:54 AM, Koenig, Christian wrote:
Am 21.12.18 um 21:36 schrieb Grodzovsky, Andrey:
On Tue, 2019-01-08 at 16:15 -0800, Steve Longerbeam wrote:
> The function ipu_csi_init_interface() was inverting the F-bit for
> NTSC case, in the CCIR_CODE_1/2 registers. The result being that
> for NTSC bottom-top field order, the CSI would swap fields and
> capture in top-bottom order.
>
> Inst
On Wed, 9 Jan 2019 11:12:24 +0100
Daniel Vetter wrote:
> On Tue, Jan 08, 2019 at 12:31:36PM +, Peter Rosin wrote:
> > While trying to temporarily hide a plane, one thing that was attempted
> > was to call (from libdrm)
> >
> > drmModeSetPlane(fd, plane_id, crtc_id, fb_id, 0,
> >
On Wed, 9 Jan 2019 11:37:19 +
Peter Rosin wrote:
> On 2019-01-09 11:12, Daniel Vetter wrote:
> > On Tue, Jan 08, 2019 at 12:31:36PM +, Peter Rosin wrote:
> >> While trying to temporarily hide a plane, one thing that was attempted
> >> was to call (from libdrm)
> >>
> >>drmModeSetPla
>-Original Message-
>From: Roper, Matthew D
>Sent: Wednesday, January 9, 2019 1:15 AM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; Syrjala,
>Ville
>; emil.l.veli...@gmail.com; Lankhorst, Maarten
>
>Subject: Re: [v4 10/12] drm/i915: Add HLG EOT
>-Original Message-
>From: Brian Starkey [mailto:brian.star...@arm.com]
>Sent: Tuesday, January 8, 2019 7:37 PM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>Lankhorst,
>Maarten ; Syrjala, Ville
>;
>Sharma, Shashank ; nd
>Subject: Re: [v6 0/
>-Original Message-
>From: Brian Starkey [mailto:brian.star...@arm.com]
>Sent: Tuesday, January 8, 2019 7:43 PM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>Lankhorst,
>Maarten ; Syrjala, Ville
>;
>Sharma, Shashank ; nd
>Subject: Re: [v6 1/
On Wed, Jan 09, 2019 at 10:33:17AM +0100, Maxime Ripard wrote:
> Hi,
>
> Here is a set of patches to allow the phy framework consumers to test and
> apply runtime configurations.
>
> This is needed to support more phy classes that require tuning based on
> parameters depending on the current use
Hi Maxime,
On Wed, Jan 09, 2019 at 10:33:24AM +0100, Maxime Ripard wrote:
> The Cadence D-PHY bindings was defined as part of the DSI block so far.
> However, since it's now going to be a separate driver, we need to move the
> binding to a file of its own.
>
> Signed-off-by: Maxime Ripard
Revie
On Wed, Jan 09, 2019 at 10:33:25AM +0100, Maxime Ripard wrote:
> Cadence has designed a D-PHY that can be used by the, currently in tree,
> DSI bridge (DRM), CSI Transceiver and CSI Receiver (v4l2) drivers.
>
> Only the DSI driver has an ad-hoc driver for that phy at the moment, while
> the v4l2 d
Since commit 2bcd3ecab773 when switching mode from X11 (ubuntu mate for
example) the display gets blurry, looking like an invalid framebuffer width.
This commit fixed atomic crtc modesetting but didn't update the display
parameters when changing mode, but only when starting a mode setting after
a
The TPO (Toppoly) TPG110 is a pretty generic display driver
similar in vein to the Ilitek 93xx devices. It is not a panel
per se but a driver used with several low-cost noname panels.
This is used on the Nomadik NHK15 combined with a OSD
OSD057VA01CT display for WVGA 800x480.
The driver is pretty
https://bugs.freedesktop.org/show_bug.cgi?id=109246
--- Comment #13 from Nicholas Kazlauskas ---
(In reply to Michel Dänzer from comment #12)
> (In reply to tme from comment #9)
> > Setting amdgpu.dc=1 on 4.15.18 and 4.16.18 does not reproduce the problem.
> > It does, however, reproduce on 4.17.
On Wed, Jan 09, 2019 at 11:10:44AM +0100, Daniel Vetter wrote:
> On Tue, Jan 08, 2019 at 12:25:19PM +0100, Gerd Hoffmann wrote:
> > The buffer object must be reserved before calling
> > ttm_bo_validate for pinning/unpinning.
> >
> > Signed-off-by: Gerd Hoffmann
>
> Seems a bit a bisect fumble in
https://bugs.freedesktop.org/show_bug.cgi?id=104362
nmr changed:
What|Removed |Added
CC||nnmmrr88...@gmail.com
--- Comment #10 from nmr -
On 09/01/19 11:51, Lucas Stach wrote:
> For the series:
>
> Tested-by: Lucas Stach
>
> on a device with TC358767 and a 4.20 based kernel.
Thanks Lucas.
Does the device use TC358767 as eDP+panel, or as full DP with an
external connector? We have the latter, and I think there are some
missing p
https://bugs.freedesktop.org/show_bug.cgi?id=104362
--- Comment #11 from nmr ---
Created attachment 143037
--> https://bugs.freedesktop.org/attachment.cgi?id=143037&action=edit
dmesg dump for hang
--
You are receiving this mail because:
You are the assignee for the bug.___
Hi Tomi,
Am Mittwoch, den 09.01.2019, 16:55 +0200 schrieb Tomi Valkeinen:
> On 09/01/19 11:51, Lucas Stach wrote:
>
> > For the series:
> >
> > > > Tested-by: Lucas Stach
> >
> > on a device with TC358767 and a 4.20 based kernel.
>
> Thanks Lucas.
>
> Does the device use TC358767 as eDP+pane
On 01/09/2019 05:22 AM, Christian König wrote:
> Am 07.01.19 um 20:47 schrieb Grodzovsky, Andrey:
>>
>> On 01/07/2019 09:13 AM, Christian König wrote:
>>> Am 03.01.19 um 18:42 schrieb Grodzovsky, Andrey:
On 01/03/2019 11:20 AM, Grodzovsky, Andrey wrote:
> On 01/03/2019 03:54 AM, Koenig,
https://bugs.freedesktop.org/show_bug.cgi?id=109234
--- Comment #11 from Sibren Vasse ---
I've been running into this issue multiple times a day. I noticed I hit the
OOPS a lot more frequent when my system was under load (e.g. compiling a
kernel) and then opening a new tab in Firefox.
Don't ask
https://bugs.freedesktop.org/show_bug.cgi?id=109234
--- Comment #10 from Sibren Vasse ---
Created attachment 143038
--> https://bugs.freedesktop.org/attachment.cgi?id=143038&action=edit
Bisect result
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=109234
--- Comment #12 from Michel Dänzer ---
Looks like this should be reported to Christoph Hellwig and other kernel DMA
mapping helper developers then. Please Cc the dri-devel mailing list when doing
so.
--
You are receiving this mail because:
You
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 79e539453b34 DRM: i915: add mode setting support.
The bot has tested the following trees: v4.20.0, v4.19.13, v4.14.91, v4.9.148,
v4.4.169, v3.18.131.
v4.20.0: Failed to apply! Pos
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 79e539453b34 DRM: i915: add mode setting support.
The bot has tested the following trees: v4.20.0, v4.19.13, v4.14.91, v4.9.148,
v4.4.169, v3.18.131.
v4.20.0: Failed to apply! Pos
Hi,
On Wed, Jan 9, 2019 at 6:38 AM Georgi Djakov wrote:
>
> Hi Jayant,
>
> On 12/21/18 08:20, Jayant Shekhar wrote:
> > From: Sravanthi Kollukuduru
> >
> > The interconnect framework is designed to provide a
> > standard kernel interface to control the settings of
> > the interconnects on a SoC.
Hi Daniel,
On Tue, 2019-01-08 at 19:21 +0100, Daniel Vetter wrote:
> On Tue, Jan 8, 2019 at 3:51 PM Paul Kocialkowski
> wrote:
> > During an atomic commit, the HVS is configured with a display list
> > for the channel matching the associated CRTC. The Pixel Valve (CRTC)
> > and encoder are also c
https://bugs.freedesktop.org/show_bug.cgi?id=109235
Michel Dänzer changed:
What|Removed |Added
QA Contact|dri-devel@lists.freedesktop |xorg-t...@lists.x.org
Hi Sean,
I do recall seeing you at XDC2017, I do not believe I spoke with you at the
event.
I will not name the name, but I had one developer who strongly asked me to
convert to atomic mode setting, but I refused due to the state of the code at
the time.
Now, the KMS device support is mostly co
On 09.01.2019 15:13, Robert Chiras wrote:
> Currently, the enable of the axi clock return status is ignored, causing
> issues when the enable fails then we try to disable it. Therefore, it is
> better to check the return status and disable it only when enable
> succeeded.
> Also, remove the helper
https://bugs.freedesktop.org/show_bug.cgi?id=108098
--- Comment #9 from Daniel Stone ---
(In reply to Michel Dänzer from comment #7)
> FWIW, I advise against paying too much attention to fin4478. They are not
> involved in driver development and known for making rather questionable
> suggestions
On Wed, Jan 9, 2019 at 3:54 PM Gerd Hoffmann wrote:
>
> On Wed, Jan 09, 2019 at 11:10:44AM +0100, Daniel Vetter wrote:
> > On Tue, Jan 08, 2019 at 12:25:19PM +0100, Gerd Hoffmann wrote:
> > > The buffer object must be reserved before calling
> > > ttm_bo_validate for pinning/unpinning.
> > >
> > >
https://bugs.freedesktop.org/show_bug.cgi?id=107652
Mart Raudsepp changed:
What|Removed |Added
CC||l...@gentoo.org
--- Comment #17 from Ma
Hi,
I was really pleased to see that the damage helper had landed. Now I can
do framebuffer flushing solely through the display pipe functions. This
prepares the ground for the removal of struct tinydrm_device in my next
series.
Note:
The damage helper isn't in drm-misc-next yet, it will show up
This switches to drm_atomic_helper_dirtyfb() as the framebuffer dirty
handler. All flushing will now happen in the pipe functions.
Also enable the damage plane property for all except repaper which can
only do full updates.
ili9225:
This change made ili9225_init() equal to mipi_dbi_init() so use
This adds a .fb_create helper that sets the .dirty callback to
drm_atomic_helper_dirtyfb().
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_gem_framebuffer_helper.c | 47 +---
include/drm/drm_gem_framebuffer_helper.h | 3 ++
2 files changed, 44 insertions(+), 6 deletio
Useful for drivers that only care about the combined damage.
Cc: Deepak Rawat
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_damage_helper.c | 43 +
include/drm/drm_damage_helper.h | 3 ++
2 files changed, 46 insertions(+)
diff --git a/drivers/gpu/drm/dr
This prepares for the switch to drm_atomic_helper_dirtyfb() in the next
patch. The damage helper returns a drm_rect so switch to that everywhere
including using a pointer in the dirty functions.
This is a non-functional change except for the debug print which looks a
bit different.
Signed-off-by:
The interconnect API provides an interface for consumer drivers to express
their bandwidth needs in the SoC. This data is aggregated and the on-chip
interconnect hardware is configured to the appropriate power/performance
profile.
MDSS is one of the interconnect consumers which uses the interconne
From: Sravanthi Kollukuduru
Since the upstream interconnect bus framework has landed
upstream, the existing references of custom bus scaling
needs to be cleaned up.
Changes in v2:
- Fixed build error due to partial clean up
Changes in v3:
- Condense multiple lines into a single
From: Sravanthi Kollukuduru
The interconnect framework is designed to provide a
standard kernel interface to control the settings of
the interconnects on a SoC.
The interconnect API uses a consumer/provider-based model,
where the providers are the interconnect buses and the
consumers could be va
From: Sravanthi Kollukuduru
Add interconnect properties such as interconnect provider specifier
, the edge source and destination ports which are required by the
interconnect API to configure interconnect path for MDSS.
Changes in v2:
- none
Changes in v3:
- Remove common proper
Hi Rob,
On Tue, Dec 18, 2018 at 10:32 AM Jordan Crouse wrote:
>
> Now that more of the sdm845 bindings are headed upstream this a refresh of
> of https://patchwork.freedesktop.org/series/39308/ to add bindings and nodes
> for the GPU/GMU and GPU SMMU for sdm845. v7 of this patchset also removes
>
Hi Noralf.
>
> I was really pleased to see that the damage helper had landed. Now I can
> do framebuffer flushing solely through the display pipe functions. This
> prepares the ground for the removal of struct tinydrm_device in my next
> series.
I browsed through the code - and the code paths I
On Wed, Jan 9, 2019 at 12:36 PM Daniel Vetter wrote:
>
> On Wed, Jan 9, 2019 at 3:54 PM Gerd Hoffmann wrote:
> >
> > On Wed, Jan 09, 2019 at 11:10:44AM +0100, Daniel Vetter wrote:
> > > On Tue, Jan 08, 2019 at 12:25:19PM +0100, Gerd Hoffmann wrote:
> > > > The buffer object must be reserved befor
From: Daniele Castagna
Add the KMS plane rotation property to the DRM rockchip driver,
for SoCs RK3328, RK3368 and RK3399.
RK3288 only supports rotation at the display level (i.e. CRTC),
but for now we are only interested in plane rotation.
This commit only adds support for the value of reflect
This commit splits the registers for RK3288 from those
for RK3328, RK3368 and RK3399. It seems RK3288 does not
support plane x-y-mirroring, and so in order to support this
for the other SoCs, we need to have separate set of registers
for win0 and win1.
Signed-off-by: Ezequiel Garcia
---
drivers/
Fix a small typo in the macros VOP argument. The macro argument
is currently wrongly named "x", and then never used. The code
built fine almost by accident, as the macros are always used
in a context where a proper "vop" symbol exists.
This fix is almost cosmetic, as the resulting code shouldn't c
Here's a small series supporting plane reflection (aka. mirroring)
properties on RK3328, RK3368, and RK3399 SoCs.
Note that RK3288 specification doesn't seem to document registers
for plane mirroring, but instead it only seems to support mirroring
at the display (CRTC) level.
A small typo cleanup
Hi Linus.
On Wed, Jan 09, 2019 at 02:53:31PM +0100, Linus Walleij wrote:
> The TPO (Toppoly) TPG110 is a pretty generic display driver
> similar in vein to the Ilitek 93xx devices. It is not a panel
> per se but a driver used with several low-cost noname panels.
>
> This is used on the Nomadik NH
Den 09.01.2019 19.26, skrev Sam Ravnborg:
> Hi Noralf.
>
>>
>> I was really pleased to see that the damage helper had landed. Now I can
>> do framebuffer flushing solely through the display pipe functions. This
>> prepares the ground for the removal of struct tinydrm_device in my next
>> series.
On Wed, Jan 9, 2019 at 1:20 PM Doug Anderson wrote:
>
> Hi Rob,
>
> On Tue, Dec 18, 2018 at 10:32 AM Jordan Crouse wrote:
> >
> > Now that more of the sdm845 bindings are headed upstream this a refresh of
> > of https://patchwork.freedesktop.org/series/39308/ to add bindings and nodes
> > for the
On Wed, Jan 09, 2019 at 05:52:20PM +0100, Paul Kocialkowski wrote:
> Hi Daniel,
>
> On Tue, 2019-01-08 at 19:21 +0100, Daniel Vetter wrote:
> > On Tue, Jan 8, 2019 at 3:51 PM Paul Kocialkowski
> > wrote:
> > > During an atomic commit, the HVS is configured with a display list
> > > for the channe
Hi Kevin,
On Wed, Jan 09, 2019 at 06:09:00PM +0100, Kevin Brace wrote:
> Hi Sean,
>
> I do recall seeing you at XDC2017, I do not believe I spoke with you at
> the event. I will not name the name, but I had one developer who
> strongly asked me to convert to atomic mode setting, but I refused du
Hi Dave, Daniel,
Fixes for 5.0. Highlights:
- Powerplay fixes
- Virtual display pinning fixes
- Golden register updates for vega
- Pitch and gem size validation fixes
- Fix for error case in sr-iov init
- Disable page tables in system memory on RV due to issues with IOMMU
reported on some platf
On Wed, Jan 09, 2019 at 06:49:53PM +0100, Noralf Trønnes wrote:
> This adds a .fb_create helper that sets the .dirty callback to
> drm_atomic_helper_dirtyfb().
>
> Signed-off-by: Noralf Trønnes
> ---
> drivers/gpu/drm/drm_gem_framebuffer_helper.c | 47 +---
> include/drm/drm_gem_
On Wed, Jan 9, 2019 at 6:50 PM Noralf Trønnes wrote:
>
> Hi,
>
> I was really pleased to see that the damage helper had landed. Now I can
> do framebuffer flushing solely through the display pipe functions. This
> prepares the ground for the removal of struct tinydrm_device in my next
> series.
A
On Wed, Jan 09, 2019 at 09:39:45PM +0100, Daniel Vetter wrote:
> Hi Kevin,
>
> On Wed, Jan 09, 2019 at 06:09:00PM +0100, Kevin Brace wrote:
> > Hi Sean,
> >
> > I do recall seeing you at XDC2017, I do not believe I spoke with you at
> > the event. I will not name the name, but I had one develope
1 - 100 of 120 matches
Mail list logo
