le in
Exynos5420 and newer SoCs is also added on top of the provided changes.
Patches were tested on Exynos4412 based Odroid U3, Exynos5422
Odroid XU3 and Exynos5433 TM2 boards, on top of Linux next-20171109 kernel.
A simple userspace test tool has been sent together with v1 of this
patchset:
This patch adds Exynos IPP v2 subsystem and userspace API.
New userspace API is focused ONLY on memory-to-memory image processing.
The two remainging IPP operation modes (framebuffer writeback and
local-path output with image processing) can be implemented using
standard DRM features: writeback co
Exynos IPP will be rewritten, so remove current IPP core code and mark
existing drivers as BROKEN.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/Kconfig | 11 +-
drivers/gpu/drm/exynos/Makefile |1 -
drivers/gpu/drm/exynos/exynos_drm_drv.c | 12 -
drivers/gp
This patch adapts Exynos DRM FIMC driver to new IPP v2 core API.
The side effect of this conversion is a switch to driver component API
to register properly in the Exynos DRM core.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/Kconfig |2 +-
drivers/gpu/drm/exynos/exyn
From: Andrzej Pietrasiewicz
There are 3 scaler devices in Exynos5420 SoCs, all are a part of MSCL
power domain. MSCL power domain and SYSMMU controllers (two per each
scaler device) have been already added to exynos5420.dtsi earlier,
so bind them to newly added devices.
Signed-off-by: Andrzej Pi
From: Andrzej Pietrasiewicz
Exynos Scaler is a hardware module, which processes graphic data fetched
from memory and transfers the resultant dato another memory buffer.
Graphics data can be up/down-scaled, rotated, flipped and converted color
space. Scaler hardware modules are a part of Exynos542
This patch adapts Exynos DRM rotator driver to new IPP v2 core API.
The side effect of this conversion is a switch to driver component API
to register properly in the Exynos DRM core.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/Kconfig |2 +-
drivers/gpu/drm/exyno
From: Andrzej Pietrasiewicz
There are two Scaler devices in Exynos5433 SoCs. Add nodes for them and
their SYSMMU controllers.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Marek Szyprowski
---
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 42 ++
1 file changed
This patch adapts Exynos DRM GScaler driver to new IPP v2 core API.
The side effect of this conversion is a switch to driver component API
to register properly in the Exynos DRM core. During the conversion
driver has been adapted to support more specific compatible strings
to distinguish between Ex
On Wed, 08 Nov 2017, "Gustavo A. R. Silva" wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Addresses-Coverity-ID: 141432
> Addresses-Coverity-ID: 141433
> Addresses-Coverity-ID: 141434
> Addresses-Coverity-ID: 141435
> Add
On Wed, Nov 08, 2017 at 04:21:04PM +0100, Noralf Trønnes wrote:
>
> Den 08.11.2017 13.21, skrev Benjamin Gaignard:
> > 2017-11-04 14:04 GMT+01:00 Noralf Trønnes :
> > > Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on
> > > the fact that drm_device holds a pointer to the drm
On Thu, Nov 9, 2017 at 9:11 AM, Marek Szyprowski
wrote:
> From: Andrzej Pietrasiewicz
>
> There are 3 scaler devices in Exynos5420 SoCs, all are a part of MSCL
> power domain. MSCL power domain and SYSMMU controllers (two per each
> scaler device) have been already added to exynos5420.dtsi earlie
On Tue, Nov 07, 2017 at 11:27:21AM +, Russell King wrote:
> Parsing the EDID for HDMI and audio information in the get_modes()
> callback is incorrect - this only parses the EDID read from the
> connector, not any override or firmware provided EDID.
>
> The correct place to parse the EDID for
On Tue, 07 Nov 2017, Russell King wrote:
> Parsing the EDID for HDMI and audio information in the get_modes()
> callback is incorrect - this only parses the EDID read from the
> connector, not any override or firmware provided EDID.
>
> The correct place to parse the EDID for these parameters is t
On Wed, Nov 08, 2017 at 02:21:08PM -0800, Eric Anholt wrote:
> Ville Syrjälä writes:
>
> > On Wed, Nov 08, 2017 at 12:17:28PM -0800, Eric Anholt wrote:
> >> Ville Syrjala writes:
> >>
> >> > From: Ville Syrjälä
> >> >
> >> > Apparently some sinks look at the YQ bits even when receiving RGB,
>
On Wed, Nov 08, 2017 at 11:34:41AM -0800, Eric Anholt wrote:
> I wanted to update the vc4 header so that I could land some igt
> testcases (though I'd much rather just be importing the header into
> igt and ditching libdrm). In the process, I cleaned up some other
> header deltas to the kernel so
On Wed, Nov 08, 2017 at 12:57:30PM -0800, Manasi Navare wrote:
> On Wed, Nov 08, 2017 at 09:30:07PM +0100, Daniel Vetter wrote:
> > Point at the equivalent atomic state and explain that atomic drivers
> > shouldn't really depend upon legacy state.
> >
> > Motivated by questions from Manasi about h
On Thu, Nov 09, 2017 at 09:39:31AM +1000, Dave Airlie wrote:
> From: Dave Airlie
>
> The lease updates missed a few bits of docs, fixed up
> the wrong name on the property lookup fn as well.
>
> Signed-off-by: Dave Airlie
Thanks a lot! Would have typed them myself, but was a bit late yesterday
If the sink device is in HDMI mode, enable infoframe interrupt in scdt
irq handle function else call start_video function immediately, because
in DVI mode, there is no infoframe interrupt provided.
Rename start_hdmi function to start_video and get rid of the old
start_video function. In start_vide
2017년 10월 31일 19:28에 Daniel Vetter 이(가) 쓴 글:
> On Mon, Oct 30, 2017 at 04:39:42PM +0100, Noralf Trønnes wrote:
>> This driver can use drm_fb_helper_lastclose() as its .lastclose callback.
>> It can also use drm_fb_helper_output_poll_changed() as its
>> .output_poll_changed callback.
>>
>> Cc: Ink
It's useful for syncing async connector work like link retraining.
v2: Make it work (Manasi&Ville)
Cc: Manasi Navare
Cc: Maarten Lankhorst
Cc: Ville Syrjälä
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/drm_atomic_helper.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
That's the only wrapper function missing and necessary to cleanup TTM.
Signed-off-by: Christian König
---
include/linux/reservation.h | 23 +++
1 file changed, 23 insertions(+)
diff --git a/include/linux/reservation.h b/include/linux/reservation.h
index 21fc84d82d41..02166e8
Instead of having a confusing wrapper or call the underlying ww_mutex
function directly.
Signed-off-by: Christian König
---
drivers/gpu/drm/qxl/qxl_release.c | 2 +-
drivers/gpu/drm/ttm/ttm_bo.c | 13 +++--
drivers/gpu/drm/ttm/ttm_execbuf_util.c | 8
include/drm
Deleted BOs with the same reservation object can be reaped even if they
can't be reserved.
v2: rebase and we still need to remove/add the BO from/to the LRU.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 39 +++
1 file changed, 31 insertio
Needed for the next patch and makes the code quite a bit easier to
understand.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
index c088703777e2..9
Consistently use the reservation object wrappers instead of accessing
the ww_mutex directly.
Additional to that use the reservation object wrappers directly instead of
calling __ttm_bo_reserve with fixed parameters.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c| 16 +++
Needed for the next patch.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 52
1 file changed, 28 insertions(+), 24 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
index 6f5d18366e6e..50a678b504
Just another alias for ttm_bo_unreserve.
Signed-off-by: Christian König
---
drivers/gpu/drm/nouveau/nouveau_gem.c | 2 +-
include/drm/ttm/ttm_bo_driver.h | 13 -
2 files changed, 1 insertion(+), 14 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_gem.c
b/drivers/gpu
Den 06.11.2017 23.48, skrev Noralf Trønnes:
This driver can use drm_fb_helper_output_poll_changed() as its
.output_poll_changed callback.
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
Signed-off-by: Noralf Trønnes
Reviewed-by: Daniel Vetter
---
I'm resending to get a CI run.
This
The vendor name was "toppoly" but other panels and the vendor list
have defined it as "tpo". So let's fix it in driver and bindings.
Signed-off-by: H. Nikolaus Schaller
---
.../display/panel/{toppoly,td028ttec1.txt => tpo,td028ttec1.txt} | 4 ++--
drivers/gpu/drm/omapdrm/displays/panel-tpo-
On Wed, Nov 8, 2017 at 9:24 AM, Alex Deucher wrote:
> From: Guenter Roeck
>
> ERROR: "__aeabi_uldivmod" [sound/soc/amd/snd-soc-acp-pcm.ko] undefined!
>
> 64-bit divides require special operations to avoid build errors on 32-bit
> systems.
>
> BUG=b:63121716
> TEST="Build i386:allmodconfig"
>
>
I
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 141432
Addresses-Coverity-ID: 141433
Addresses-Coverity-ID: 141434
Addresses-Coverity-ID: 141435
Addresses-Coverity-ID: 141436
Signed-off-by: Gustavo A. R. Silva
---
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 115025
Addresses-Coverity-ID: 115026
Addresses-Coverity-ID: 115027
Addresses-Coverity-ID: 115028
Signed-off-by: Gustavo A. R. Silva
---
drivers/video/fbdev/sis/sis_
On 2017-11-07 16:53, Philippe CORNU wrote:
> + Peter
>
> Hi Peter,
>
> CLUT support on STM32 has been removed thanks to your clean up patch
Support is a bit strong for what I thought was a dead function, or
are you saying that it used to work before my series? Really sorry
if that is the case!
On Wed, Nov 8, 2017 at 11:35 AM, Alex Deucher wrote:
> On Wed, Nov 8, 2017 at 2:30 PM, Guenter Roeck wrote:
> > On Wed, Nov 8, 2017 at 11:18 AM, Deucher, Alexander
> > wrote:
> >>
> >> > -Original Message-
> >> > From: Mark Brown [mailto:broo...@kernel.org]
> >> > Sent: Wednesday, Novem
On Thu, 09 Nov 2017, Jani Nikula wrote:
> On Wed, 08 Nov 2017, "Gustavo A. R. Silva" wrote:
>> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
>> where we are expecting to fall through.
>>
>> Addresses-Coverity-ID: 141432
>> Addresses-Coverity-ID: 141433
>> Addresses-Coverity
This patch set fixes vendor names of the panels
and fixes a problem on omapdrm with enabling
VDD_DSI for OMAP3 which is needed for displaying
the Red and Green channel on OMAP3530 (Pandora).
H. Nikolaus Schaller (4):
omapdrm: fix compatible string for td028ttec1
DTS: GTA04: fix panel compatibi
Hi Laurent,
> Am 09.11.2017 um 04:33 schrieb Laurent Pinchart
> :
>
> Hi Nikolaus,
>
> Thank you for the patch.
>
> On Wednesday, 8 November 2017 23:09:29 EET H. Nikolaus Schaller wrote:
>> The vendor name was "toppoly" but other panels and the vendor list
>> have defined it as "tpo". So let's
Vendor string is "tpo" and not "toppoly".
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap3-gta04.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi
b/arch/arm/boot/dts/omap3-gta04.dtsi
index 4504908c23fe..ec27ed67a22a 10064
commit d178e034d565 ("drm: omapdrm: Move FEAT_DPI_USES_VDDS_DSI feature to dpi
code")
introduced a new match table which turned out to be wrong, at least
for the 600 MHz OpenPandora using the OMAP3530.
The effect was strange: only the Blue channel of the RGB panel was
driven while Red and Green
Can't find these anywhere yet, errors still there.
https://patchwork.freedesktop.org/series/31220/
Regards
//Ernst
2017-09-30 10:25 GMT+02:00 Christian König :
> Am 30.09.2017 um 10:13 schrieb Dan Carpenter:
>>
>> We shifted some code around in commit 9cca0b8e5df0 ("drm/amdgpu: move
>> amdgpu_cs
Hi Laurent,
> Am 09.11.2017 um 07:35 schrieb Laurent Pinchart
> :
>
> Hi Nikolaus,
>
> On Thursday, 9 November 2017 08:05:15 EET H. Nikolaus Schaller wrote:
>>> Am 09.11.2017 um 04:33 schrieb Laurent Pinchart:
>>> On Wednesday, 8 November 2017 23:09:29 EET H. Nikolaus Schaller wrote:
The v
We can remove the "omapdss," prefix.
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap3-pandora-common.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-pandora-common.dtsi
b/arch/arm/boot/dts/omap3-pandora-common.dtsi
index 53e007abdc
Add create_handle support to virtio fb. Without this, screenshot tool
in chromium OS can't work.
Signed-off-by: Lepton Wu
---
drivers/gpu/drm/virtio/virtgpu_display.c | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/gpu/drm/virtio/virtgpu_display.c
b/drivers/gpu/drm/vir
> Am 09.11.2017 um 04:36 schrieb Laurent Pinchart
> :
>
> Hi Nikolaus,
>
> Thank you for the patch.
>
> On Wednesday, 8 November 2017 23:09:31 EET H. Nikolaus Schaller wrote:
>> We can remove the "omapdss," prefix.
>
> I agree but you should explain why.
I can add a sentence if someone helps
[+cc Andy]
On Fri, Nov 03, 2017 at 02:52:41PM +0100, Christian König wrote:
> Just add the extra PCI-ID to the existing fixup.
>
> Signed-off-by: Christian König
I folded all these additional devices into the original quirk.
> ---
> arch/x86/pci/fixup.c | 3 ++-
> 1 file changed, 2 insertions
Hi Laurent,
> Am 09.11.2017 um 04:45 schrieb Laurent Pinchart
> :
>
> Hi Nikolaus,
>
> Thank you for the patch.
>
> On Wednesday, 8 November 2017 23:09:32 EET H. Nikolaus Schaller wrote:
>> commit d178e034d565 ("drm: omapdrm: Move FEAT_DPI_USES_VDDS_DSI feature to
>> dpi code")
>>
>> introduc
On 11/8/2017 11:39 PM, Mark Brown wrote:
On Wed, Nov 08, 2017 at 12:24:03PM -0500, Alex Deucher wrote:
regmap_read(regmap, RT5645_VENDOR_ID2, &val);
+ /*
+* Read after 400msec, as it is the interval required between
+* read and power On.
+*/
+ msleep(
Since commit 4a97a3da420b ("drm: Don't update property values for atomic
drivers") atomic drivers must not update property values as properties
are read from the state instead. To catch remaining users, the
drm_object_property_set_value() function now throws a warning when
called by atomic drivers
2017-11-09 9:20 GMT+01:00 Daniel Vetter :
> On Wed, Nov 08, 2017 at 04:21:04PM +0100, Noralf Trønnes wrote:
>>
>> Den 08.11.2017 13.21, skrev Benjamin Gaignard:
>> > 2017-11-04 14:04 GMT+01:00 Noralf Trønnes :
>> > > Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on
>> > > the
On Thu, 09 Nov 2017, Russell King - ARM Linux wrote:
> On Thu, Nov 09, 2017 at 09:23:18AM +0100, Daniel Vetter wrote:
>> On Tue, Nov 07, 2017 at 11:27:21AM +, Russell King wrote:
>> > Parsing the EDID for HDMI and audio information in the get_modes()
>> > callback is incorrect - this only pars
I've accidentally pushed two incomplete WIP patches to the libdrm master
repository yesterday.
Just noticed the mistake and reverted the two.
Sorry for the noise,
Christian.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.free
The maximum pixel clock depends on the version of the connected MHL
adapter. Add mode_valid callback to filter out modes with too high pixel
clock to avoid failure in mode_fixup later.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/bridge/sil-sii8620.c | 14 ++
1 file changed, 1
https://bugs.freedesktop.org/show_bug.cgi?id=85667
--- Comment #4 from Francois Cartegnie ---
Lockup after playing field interlaced mpeg2 through hw accel.
https://streams.videolan.org/streams/ts/mpeg2-field-encoded-bff.ts
[84260.161266] radeon :01:00.0: ring 0 stalled for more than 10012
https://bugs.freedesktop.org/show_bug.cgi?id=85667
Christian König changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|NEW
Hi Stefan,
Thank you for the patch.
On Thursday, 9 November 2017 11:14:36 EET Stefan Agner wrote:
I notice you have changed the subject line. I'm not sure if the new wording is
better, as this patch doesn't set DPMS to off, it instead skips setting it
manually. How about "drm/fsl-dcu: Don't se
If the sink device is in HDMI mode, enable infoframe interrupt in scdt
irq handle function else call start_video function immediately, because
in DVI mode, there is no infoframe interrupt provided.
Rename start_hdmi function to start_video and get rid of the old
start_video function. In start_vide
From: Colin Ian King
The index to vddci_buf is using profile->ucElbVDDC_Num rather
than profile->ucElbVDDCI_Num; this looks like a copy-n-paste
error from previous code for the vddc_buf array and I'm pretty
sure this is incorrect. Fix this by using the correct variable.
Detected by CoverityScan,
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: c64efcaed73726bd3cfaa46c27768d3331a1ad35
commit: 0bd599b1f523598c05f13a4a562884e82a378c2c [2064/2165] ASoC: AMD: enable
ACP3x drivers build
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-
Hi Dave,
Just added new IPP driver since previous pull request.
We rewrited Exynos DRM IPP driver due to below limitations and issues,
- Userspace API covers memory-2-memory picture operations together with
CRTC writeback and duplicating features, which belongs to video plane.
-
On Thu, 09 Nov 2017, Luís Mendes wrote:
> I've just applied the referred individual patch to kernel-4.14-rc5 and
> the EDID isn't loaded. dw-hdmi gets no firmware at all.
Sorry, I didn't mean you could just cherry-pick that one commit and make
it work. There were a number of preparatory patches b
On Thu, Nov 09, 2017 at 11:17:03AM +, Chris Obbard wrote:
> Hi Everyone,
>
> What's the status of HDMI/SimpleFB driver for H5?
>
> I don't see anything related to HDMI in linux-next dts files:
>
> arch/arm64/boot/dts/allwinner/sun50i-h5-orangepi-pc2.dts (example board)
> arch/arm64/boot/dts
>-Original Message-
>From: Brian Starkey [mailto:brian.star...@arm.com]
>Sent: Tuesday, November 7, 2017 11:40 PM
>To: Shankar, Uma
>Cc: intel-...@lists.freedesktop.org; Syrjala, Ville ;
>Lankhorst, Maarten ; dri-
>de...@lists.freedesktop.org
>Subject: Re: [Intel-gfx] [RFC 1/7] drm: Add
On Monday, October 16, 2017 09:04:46 PM Christophe JAILLET wrote:
> This patch serie tries to fix several issues found in the error handling
> code of 'au1200fb_drv_probe()'.
> The 5 first patches fixes various issues (double free, missing error code,
> un-released resources on error, incorrect IR
On Wednesday, October 18, 2017 04:45:31 PM Ondrej Zary wrote:
> On Wednesday 18 October 2017, David Miller wrote:
> > From: John Paul Adrian Glaubitz
> > Date: Wed, 18 Oct 2017 15:14:27 +0200
> >
> > > Hi Bartlomiej!
> > >
> > > On 10/18/2017 02:56 PM, Bartlomiej Zolnierkiewicz wrote:
> > >> igafb
Hi Laurent,
On 2017-11-09 11:45, Laurent Pinchart wrote:
> Hi Stefan,
>
> Thank you for the patch.
>
> On Thursday, 9 November 2017 11:14:36 EET Stefan Agner wrote:
>
> I notice you have changed the subject line. I'm not sure if the new wording
> is
> better, as this patch doesn't set DPMS to
On Friday, November 03, 2017 06:21:36 PM Aleksandar Markovic wrote:
> From: Aleksandar Markovic
>
> Add documentation for DT binding of Goldfish FB driver. The compatible
> string used by OS for binding the driver is "google,goldfish-fb".
>
> Signed-off-by: Miodrag Dinic
> Signed-off-by: Goran
On 2017-11-06 20:18, Noralf Trønnes wrote:
> Replace driver's code with the generic helpers that do the same thing.
Tested using:
echo devices > /sys/power/pm_test
echo freeze > /sys/power/state
Note, currently I do get, but even without this patches, so this is
something else:
[ 930.992433] -
On Thu, 09 Nov 2017, Luís Mendes wrote:
> Hi Jani,
>
> I tried:
> git clone git://people.freedesktop.org/~airlied/linux -b drm-next
> --depth=1 --single-branch
>
> I got this:
> EDID isn't loaded from file
>
> # cat /proc/cmdline
> console=ttymxc0,115200 root=/dev/sda2 rw video=HDMI-A-1:1920x1080M
Hi,
On Wed, 08 Nov 2017 10:18:03 -0800 Eric Anholt wrote:
> Lothar Waßmann writes:
>
> > Hi,
> >
> > drivers/gpu/drm/bridge/lvds-encoder.c driver is currently
> > dysfunctional due to:
> > |commit 13dfc0540a575b47b2d640b093ac16e9e09474f6
> > |Author: Eric Anholt
> > |Date: Fri Jun 2 13:25:14
https://bugs.freedesktop.org/show_bug.cgi?id=103142
--- Comment #5 from Emil Velikov ---
Gert, should we close this considering 69eee511c63 ("r600/sb: bail out if
prepare_alu_group() doesn't find a proper scheduling") has landed?
--
You are receiving this mail because:
You are the assignee for
On Sunday, November 05, 2017 03:43:05 PM SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 5 Nov 2017 14:54:52 +0100
>
> Add a jump target so that a bit of exception handling can be better reused
> at the end of this function.
>
> This issue was detected by using the Coccinelle softwa
Den 07.11.2017 20.31, skrev Alexey Brodkin:
Hi Noralf,
On Tue, 2017-11-07 at 20:13 +0100, Noralf Trønnes wrote:
There is a new core debugfs file that prints fb/gem info:
/dri//framebuffer
Use drm_gem_cma_print_info() to provide info to that output instead
of using drm_fb_cma_debugfs_show().
On Monday, November 06, 2017 01:17:11 PM Colin King wrote:
> From: Colin Ian King
>
> Variables err_max, err_target and f_best are being assigned values but
> these are never read, hence they are redundant variables and can be
> removed. Cleans up clang warnings:
>
> drivers/video/fbdev/intelfb/
On Monday, November 06, 2017 04:31:18 PM Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Signed-off-by: Gustavo A. R. Silva
Patch queued for 4.15, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
S
On Monday, November 06, 2017 04:40:01 PM Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Signed-off-by: Gustavo A. R. Silva
Patch queued for 4.15, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
S
On Monday, November 06, 2017 04:45:50 PM Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Notice that in this particular case I placed the "fall through" comment
> on its own line, which is what GCC is e
On Wednesday, November 08, 2017 11:10:59 AM Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Addresses-Coverity-ID: 115025
> Addresses-Coverity-ID: 115026
> Addresses-Coverity-ID: 115027
> Addresses-Cove
Den 09.11.2017 16.52, skrev Noralf Trønnes:
Den 07.11.2017 20.31, skrev Alexey Brodkin:
Hi Noralf,
On Tue, 2017-11-07 at 20:13 +0100, Noralf Trønnes wrote:
There is a new core debugfs file that prints fb/gem info:
/dri//framebuffer
Use drm_gem_cma_print_info() to provide info to that outpu
Den 09.11.2017 15.34, skrev Stefan Agner:
On 2017-11-06 20:18, Noralf Trønnes wrote:
Replace driver's code with the generic helpers that do the same thing.
Tested using:
echo devices > /sys/power/pm_test
echo freeze > /sys/power/state
Note, currently I do get, but even without this patches,
On 09/11/17 09:59 AM, Christian König wrote:
> Consistently use the reservation object wrappers instead of accessing
> the ww_mutex directly.
>
> Additional to that use the reservation object wrappers directly instead of
> calling __ttm_bo_reserve with fixed parameters.
>
> Signed-off-by: Christi
https://bugs.freedesktop.org/show_bug.cgi?id=103142
--- Comment #6 from Gert Wollny ---
In debug mode an assertion fires as a reminder that this patch only works
around the real, yet to be understood bug. For that reason I think it would be
better to keep it open (At least the aforementioned bug
On Tuesday, October 24, 2017 08:20:26 AM Kees Cook wrote:
> diff --git a/drivers/video/fbdev/pxa3xx-gcu.c
> b/drivers/video/fbdev/pxa3xx-gcu.c
> index 933619da1a94..e88447eac32c 100644
> --- a/drivers/video/fbdev/pxa3xx-gcu.c
> +++ b/drivers/video/fbdev/pxa3xx-gcu.c
> @@ -513,16 +513,10 @@ pxa3xx
Am 09.11.2017 um 17:50 schrieb Michel Dänzer:
On 09/11/17 09:59 AM, Christian König wrote:
Consistently use the reservation object wrappers instead of accessing
the ww_mutex directly.
Additional to that use the reservation object wrappers directly instead of
calling __ttm_bo_reserve with fixed
On 2017-11-09 17:49, Noralf Trønnes wrote:
> Den 09.11.2017 15.34, skrev Stefan Agner:
>> On 2017-11-06 20:18, Noralf Trønnes wrote:
>>> Replace driver's code with the generic helpers that do the same thing.
>> Tested using:
>> echo devices > /sys/power/pm_test
>> echo freeze > /sys/power/state
>>
On Thu, Nov 9, 2017 at 6:35 AM, Colin King wrote:
> From: Colin Ian King
>
> The index to vddci_buf is using profile->ucElbVDDC_Num rather
> than profile->ucElbVDDCI_Num; this looks like a copy-n-paste
> error from previous code for the vddc_buf array and I'm pretty
> sure this is incorrect. Fix
On 09/11/17 09:59 AM, Christian König wrote:
> Deleted BOs with the same reservation object can be reaped even if they
> can't be reserved.
>
> v2: rebase and we still need to remove/add the BO from/to the LRU.
>
> Signed-off-by: Christian König
> ---
> drivers/gpu/drm/ttm/ttm_bo.c | 39 +++
Daniel Vetter writes:
> On Wed, Nov 08, 2017 at 02:21:08PM -0800, Eric Anholt wrote:
>> Ville Syrjälä writes:
>>
>> > On Wed, Nov 08, 2017 at 12:17:28PM -0800, Eric Anholt wrote:
>> >> Ville Syrjala writes:
>> >>
>> >> > From: Ville Syrjälä
>> >> >
>> >> > Apparently some sinks look at the Y
https://bugs.freedesktop.org/show_bug.cgi?id=102423
Henry Hu changed:
What|Removed |Added
CC||henry.hu...@gmail.com
--- Comment #3 from He
https://bugs.freedesktop.org/show_bug.cgi?id=103653
Bug ID: 103653
Summary: Unreal segfault since gallium/u_threaded: avoid syncs
for get_query_result
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS:
Le 09/11/2017 à 14:12, Bartlomiej Zolnierkiewicz a écrit :
[...]
* patch description was changed to silence issues reported by checkpatch.pl:
WARNING: 'succesful' may be misspelled - perhaps 'successful'?
#4:
'au1200fb_drv_probe()' can not fail after a succesful call to
Odd. Even if I can not
On Tue, Nov 07, 2017 at 01:37:10PM +0530, Sumit Semwal wrote:
> Hi Ville,
>
> On 3 November 2017 at 13:18, Christian König wrote:
> > Patch #4 is Reviewed-by: Christian König .
> >
> > The rest is Acked-by: Christian König .
> >
> > Regards,
> > Christian.
> >
> >
> > Am 02.11.2017 um 21:03 schri
https://bugs.freedesktop.org/show_bug.cgi?id=99801
--- Comment #18 from Harry Wentland ---
Can you retest this on either one of the following trees?
Alex's amd-staging-drm-next tree
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
Dave's drm-next-amd-dc-staging
https://cgit
https://bugs.freedesktop.org/show_bug.cgi?id=103654
Bug ID: 103654
Summary: GL_POINT_SMOOTH not handled
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: nor
On 11/06/2017 07:59 AM, Benjamin Gaignard wrote:
Put include in alphabetic order
Acked-by: Laura Abbott
Signed-off-by: Benjamin Gaignard
---
drivers/staging/android/ion/ion.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/android/ion/i
On 11/06/2017 07:59 AM, Benjamin Gaignard wrote:
Instead a getting only one common device "/dev/ion" for
all the heaps this patch allow to create one device
entry ("/dev/ionX") per heap.
Getting an entry per heap could allow to set security rules
per heap and global ones for all heaps.
Allocatio
Add a variant of rbtree_replace_node() that maintains the leftmost
cached of struct rbtree_root_cached when replacing nodes within the
rbtree.
As drm_mm is the only rb_replace_node() being used on an interval tree,
the mistake looks fairly self-contained. Furthermore the only user of
drm_mm_replac
The majority of the asserts (validating nodes and ranges) are shared
amongst several subtests. This makes identification of which caller
failed hard; but we uniquely identify them if we include the callsite
into the assertion error message (a single frame stacktrace).
Signed-off-by: Chris Wilson
-Original Message-
From: Emil Velikov [mailto:emil.l.veli...@gmail.com]
Sent: Monday, October 30, 2017 6:23 AM
To: Sharma, Deepak
Cc: ML dri-devel ; Deucher, Alexander
; Stéphane Marchesin
Subject: Re: [PATCH] drm/vgem: Fix vgem_init to get drm device avaliable.
On 26 October 2017 at
tree: git://anongit.freedesktop.org/drm-intel drm-intel-next-queued
head: 7f017b19fbce6200a993305425bf930f38fcd9e6
commit: bccd3b831185e75c4138bc3fd5201f3214dfeb3d [1/3] drm/i915: Use
trace_printk to provide a death rattle for GEM
config: x86_64-randconfig-s0-11100726 (attached as .config)
com
1 - 100 of 113 matches
Mail list logo
