https://bugs.freedesktop.org/show_bug.cgi?id=108992
--- Comment #15 from chris ---
(In reply to chris from comment #14)
> I can confirm that the iommu=pt workaround works, also iommu=soft works to
> get gdm started and use the laptop. Sadly i have no idea what impact those
> workarounds have
Hi Daniel,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on v4.20-rc7 next-20181220]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
https://bugs.freedesktop.org/show_bug.cgi?id=108992
--- Comment #14 from chris ---
I can confirm that the iommu=pt workaround works, also iommu=soft works to get
gdm started and use the laptop. Sadly i have no idea what impact those
workarounds have when it comes to performance of the gpu/cpu or
Add interconnect properties such as the source and the destination
ports for MDSS on SDM845.
Signed-off-by: Jayant Shekhar
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
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
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
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
Hi Kangjie,
Thank you for the patch.
On Thursday, 20 December 2018 09:41:16 EET Kangjie Lu wrote:
> Both anx78xx_set_bits() and anx78xx_clear_bits() in the poweron process
> may fail. The fix inserts checks for their return values. If the poweron
> process fails, it calls anx78xx_poweroff().
>
On 12/21/2018 2:59 AM, Stephen Boyd wrote:
Quoting Rob Herring (2018-12-19 15:47:25)
On Wed, Dec 19, 2018 at 4:40 PM Doug Anderson wrote:
On Wed, Dec 19, 2018 at 12:40 PM Doug Anderson wrote:
On Wed, Dec 19, 2018 at 12:09 PM Rob Herring wrote:
...but it does have a frequency, doesn't it?
On Thu, Dec 20, 2018 at 7:47 PM Daniel Vetter wrote:
>
> On Thu, Dec 20, 2018 at 10:07 AM Tomasz Figa wrote:
> >
> > Hi Helen,
> >
> > On Fri, Dec 14, 2018 at 10:35 AM Helen Koike
> > wrote:
> > >
> > > Hi Tomasz,
> > >
> > > On 12/13/18 2:02 AM, Tomasz Figa wrote:
> > > > On Thu, Dec 6, 2018
https://bugs.freedesktop.org/show_bug.cgi?id=109124
Bug ID: 109124
Summary: [AMD][TAHITI XT] csgo new battle royal mode bad
performance
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux
On 2018.12.20 12:33:35 +0100, Gerd Hoffmann wrote:
> On Thu, Dec 20, 2018 at 08:45:09AM +, Zhang, Tina wrote:
> >
> >
> > > -Original Message-
> > > From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org]
> > > On
> > > Behalf Of Gerd Hoffmann
> > > Sent: Wednesday,
https://bugs.freedesktop.org/show_bug.cgi?id=108992
--- Comment #13 from Brian ---
FYI, as a workaround, you can use the kernel opt:
iommu=pt
..at least, on 4.20 rc7, which is the only one I've tried that on, but it
should work with others.
--
You are receiving this mail because:
You are
+ intel-gfx and dri-devel
Hi,
This is the Gvt-g local display direct flip discussion. And please reference
here
(https://lists.freedesktop.org/archives/intel-gvt-dev/2018-December/004594.html)
to see what the feature is.
Mostly, with Gvt-g local display direct flip feature, vGPU can directly
https://bugzilla.kernel.org/show_bug.cgi?id=201539
--- Comment #6 from Tony Chaveiro (tcha...@gmail.com) ---
kernel parameters: amdgpu.cik_support=1 amdgpu.dc=0
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=201539
Tony Chaveiro (tcha...@gmail.com) changed:
What|Removed |Added
CC||tcha...@gmail.com
> 在 2018年12月20日，19:22，Michel Dänzer 写道：
>
> From: Michel Dänzer
Reviewed-by: Junwei Zhang
>
> No need for pr_err here, the pr_err message in ttm_bo_evict is enough
> to draw attention to something not going as planned.
>
> Signed-off-by: Michel Dänzer
> ---
>
> Similar to a previous
Ah, thanks. I was on drm-next branch. I will switch to msm-next.
On Thu, Dec 20, 2018 at 11:47 AM Jordan Crouse
wrote:
> On Thu, Dec 20, 2018 at 10:47:02AM -0800, Chia-I Wu wrote:
> > memptrs_bo is used to store msm_rbmemptrs. Size it correctly.
> >
> > Signed-off-by: Chia-I Wu
>
> Thanks
Hi Kangjie,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.20-rc7 next-20181220]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Thu, 2018-12-20 at 09:10 -0800, Rodrigo Vivi wrote:
> On Thu, Dec 20, 2018 at 02:21:20PM +0100, Hans de Goede wrote:
> > Call intel_psr_enable() and intel_edp_drrs_enable() on pipe updates
> > to make
> > sure that we enable PSR / DRRS (when applicable) on fastsets.
I am probably missing
Hi Kangjie,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.20-rc7 next-20181220]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
https://bugs.freedesktop.org/show_bug.cgi?id=108843
--- Comment #7 from alex14...@yahoo.com ---
Tried with wip from 12/19 and dc=1: display now turns on when laptop is opened,
and the error messages no longer appear.
--
You are receiving this mail because:
You are the assignee for the
On Mon, 17 Dec 2018 13:36:42 +0100, Heiko Stuebner wrote:
> Add the compatible and grf values and allow the driver to also
> not select a specific crtc input on systems with only one vop.
>
> Signed-off-by: Heiko Stuebner
> ---
> .../display/rockchip/dw_mipi_dsi_rockchip.txt | 1 +
>
On Mon, 17 Dec 2018 13:36:41 +0100, Heiko Stuebner wrote:
> Add the compatible and allow the driver to also not set any crtc input
> on socs that only have one vop. While that was already possible
> because the driver checked against the grf-reg being 0, make that
> var an int as "0x0" is a valid
On Mon, Dec 17, 2018 at 01:36:40PM +0100, Heiko Stuebner wrote:
> The rk3368 only has one vop block and thus the dw_hdmi does not need to
> do the source selection.
>
> Signed-off-by: Heiko Stuebner
> ---
> .../display/rockchip/dw_hdmi-rockchip.txt | 1 +
Acked-by: Rob Herring
>
On Mon, 17 Dec 2018 13:36:37 +0100, Heiko Stuebner wrote:
> Needed as input for the dsi controller.
>
> Signed-off-by: Heiko Stuebner
> ---
> include/dt-bindings/clock/rk3368-cru.h | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring
On Mon, 17 Dec 2018 13:36:36 +0100, Heiko Stuebner wrote:
> Add the clock ids so that they can be exported from the clock driver
> and referenced in the rk3368 devicetree.
>
> Signed-off-by: Heiko Stuebner
> ---
> include/dt-bindings/clock/rk3368-cru.h | 2 ++
> 1 file changed, 2 insertions(+)
Quoting Rob Herring (2018-12-19 15:47:25)
> On Wed, Dec 19, 2018 at 4:40 PM Doug Anderson wrote:
> > On Wed, Dec 19, 2018 at 12:40 PM Doug Anderson
> > wrote:
> > > On Wed, Dec 19, 2018 at 12:09 PM Rob Herring wrote:
> > > ...but it does have a frequency, doesn't it?
> > >
> > > + compatible
https://bugs.freedesktop.org/show_bug.cgi?id=109122
Bug ID: 109122
Summary: blank screen on rx580 starting with kernel 4.19.9
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
On Tue, Dec 11, 2018 at 10:19 PM Maxime Ripard
wrote:
>
> On Mon, Dec 10, 2018 at 09:47:19PM +0530, Jagan Teki wrote:
> > Video start delay can be computed by subtracting total vertical
> > timing with front porch timing and with adding 1 delay line for TCON.
> >
> > BSP code form BPI-M64-bsp is
On 12/19/18 5:39 PM, Zengtao (B) wrote:
Hi laura:
-Original Message-
From: Laura Abbott [mailto:labb...@redhat.com]
Sent: Thursday, December 20, 2018 2:10 AM
To: Zengtao (B) ; sumit.sem...@linaro.org
Cc: Greg Kroah-Hartman ; Arve Hjønnevåg
; Todd Kjos ; Martijn Coenen
; Joel Fernandes
Quoting Eric Engestrom (2018-12-19 08:23:40)
> Signed-off-by: Eric Engestrom
> ---
> RELEASING | 27 ---
> 1 file changed, 8 insertions(+), 19 deletions(-)
>
> diff --git a/RELEASING b/RELEASING
> index 7e03e3b9acb1cbfb261a..d1ad8e3b4ad16d4ca14f 100644
> --- a/RELEASING
On Thu, Dec 20, 2018 at 10:47:02AM -0800, Chia-I Wu wrote:
> memptrs_bo is used to store msm_rbmemptrs. Size it correctly.
>
> Signed-off-by: Chia-I Wu
Thanks for your patch. I'm really glad somebody is looking seriously at this
code. We have this in msm-next:
On Thu, Dec 20, 2018 at 10:46:45AM -0800, Chia-I Wu wrote:
> It gets the generic states from the adreno core.
>
> This also adds a missing NULL check in msm_gpu_open.
>
> Signed-off-by: Chia-I Wu
Thanks for the patch. We have an expanded version of the 6xx gpu state in
msm-next [1]. You can
Hi,
On Thu, Dec 20, 2018 at 9:30 AM Jordan Crouse wrote:
>
> Add documentation for the interconnect and interconnect-names bindings
> for the GPU node as detailed by bindings/interconnect/interconnect.txt.
>
> Signed-off-by: Jordan Crouse
> ---
>
>
Hi,
On Thu, Dec 20, 2018 at 9:30 AM Jordan Crouse wrote:
>
> Try to get the interconnect path for the GPU and vote for the maximum
> bandwidth to support all frequencies. This is needed for performance.
> Later we will want to scale the bandwidth based on the frequency to
> also optimize for
Expedite job deletion from ring mirror list to the HW fence signal
callback instead from finish_work, together with waiting for all
such fences to signal in drm_sched_stop we garantee that
already signaled job will not be processed twice.
Remove the sched finish fence callback and just submit
Hi Daniel,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on v4.20-rc7 next-20181220]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
Decauple sched threads stop and start and ring mirror
list handling from the policy of what to do about the
guilty jobs.
When stoppping the sched thread and detaching sched fences
from non signaled HW fenes wait for all signaled HW fences
to complete before rerunning the jobs.
v2: Fix
On Thu, 20 Dec 2018 at 14:45, Daniel Vetter wrote:
>
> On Thu, Dec 20, 2018 at 01:50:26PM +, Emil Velikov wrote:
> > On Wed, 19 Dec 2018 at 20:36, Daniel Vetter wrote:
> > >
> > > On Wed, Dec 19, 2018 at 07:22:45PM +, Emil Velikov wrote:
> > > > From: Emil Velikov
> > > >
> > > >
I screwed up a rebase somehow.
v2: Drop bogus hunk.
v3: Really drop bogus hunk (Lubomir).
Cc: Lubomir Rintel
Signed-off-by: Daniel Vetter
---
Documentation/gpu/drm-kms-helpers.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/gpu/drm-kms-helpers.rst
memptrs_bo is used to store msm_rbmemptrs. Size it correctly.
Signed-off-by: Chia-I Wu
---
drivers/gpu/drm/msm/msm_gpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/msm/msm_gpu.c b/drivers/gpu/drm/msm/msm_gpu.c
index 11aac8337066..d23049eb29c4 100644
---
It gets the generic states from the adreno core.
This also adds a missing NULL check in msm_gpu_open.
Signed-off-by: Chia-I Wu
---
drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 44 +++
drivers/gpu/drm/msm/msm_debugfs.c | 2 +-
2 files changed, 45 insertions(+), 1
On Thu, Dec 20, 2018 at 07:35:15PM +0100, Daniel Vetter wrote:
> > Err, with streaming DMA buffer sharing is trivial. The coherent DMA
> > allocator is what causes all kinds of horrible hacks that can't actually
> > work on various platforms.
>
> Hm, I thought the streaming dma api is the one
On Thu, Dec 20, 2018 at 7:33 PM Christoph Hellwig wrote:
>
> On Thu, Dec 20, 2018 at 07:29:37PM +0100, Daniel Vetter wrote:
> > What we most definitely not want to end up with though is actually
> > streaming dma, because with that all the zero copy buffer sharing
> > tricks become pointless.
On Thu, Dec 20, 2018 at 6:38 PM Kazlauskas, Nicholas
wrote:
>
> On 12/20/18 12:09 PM, Daniel Vetter wrote:
> > On Thu, Dec 20, 2018 at 6:03 PM Alex Deucher wrote:
> >>
> >> + Harry
> >>
> >> On Thu, Dec 20, 2018 at 11:54 AM Daniel Vetter wrote:
> >>>
> >>> On Thu, Dec 20, 2018 at 5:40 PM Alex
Regards
Shashank
On 12/12/2018 2:08 AM, Uma Shankar wrote:
HDR source metadata set and get property implemented in this
patch.
Again, HDR output metadata ? How about re-arranging the line like "This
patch implements get() and set() functions for HDR output metadata
property" just to make it
On Thu, Dec 20, 2018 at 07:29:37PM +0100, Daniel Vetter wrote:
> What we most definitely not want to end up with though is actually
> streaming dma, because with that all the zero copy buffer sharing
> tricks become pointless. There's pretty epic amounts of hacks to work
> around this, I have no
Nicolas Saenz Julienne writes:
> This patch exposes backlight control into userspace by creating a
> backlight device instead of directly accessing the PWM registers.
>
> The backlight driver can't go on a separate file as it shares the I2C
> bus & address with the panel.
I remember some
On Thu, Dec 20, 2018 at 6:39 PM Christoph Hellwig wrote:
>
> On Thu, Dec 20, 2018 at 05:49:39PM +0200, Oleksandr Andrushchenko wrote:
> > This is the only patch [1], no series. And at the moment I think
> > there is nothing to review as I am not sure how to deal with those
> > shmem pages: this
Regards
Shashank
On 12/12/2018 2:08 AM, Uma Shankar wrote:
Attach HDR metadata property to connector object.
v2: Rebase
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/i915/intel_hdmi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_hdmi.c
Regards
Shashank
On 12/12/2018 2:08 AM, Uma Shankar wrote:
CEA 861.3 spec adds colorimetry data block for HDMI.
Parsing the block to get the colorimetry data from
panel.
v2: Rebase
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/drm_edid.c | 24
Regards
Shashank
On 12/12/2018 2:08 AM, Uma Shankar wrote:
HDR metadata block is introduced in CEA-861.3 spec.
Parsing the same to get the panel's HDR metadata.
v2: Rebase and added Ville's POC changes to the patch.
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/drm_edid.c | 45
On 12/12/2018 03:20 PM, Noralf Trønnes wrote:
>
> Den 12.12.2018 12.05, skrev Daniel Vetter:
>> On Mon, Dec 10, 2018 at 08:02:55PM +0100, Noralf Trønnes wrote:
>>> When unregistering fbdev using unregister_framebuffer(), any bound
>>> console will unbind automatically. This is working fine if
Regards
Shashank
On 12/12/2018 2:08 AM, Uma Shankar wrote:
Add bit field and macro for extended tag in CEA block. Also,
declare macros for HDR metadata block.
This should have been a part of patch, where these macros are being
used, so that we can see it being used properly. While re-basing
On 12/03/2018 01:24 PM, Geert Uytterhoeven wrote:
> Remove dependencies on HAS_DMA where a Kconfig symbol depends on another
> symbol that implies HAS_DMA, and, optionally, on "|| COMPILE_TEST".
> In most cases this other symbol is an architecture or platform specific
> symbol, or PCI.
>
>
[ added dri-devel ML & fbdev ML to Cc: ]
On 12/03/2018 12:47 PM, Lubomir Rintel wrote:
> A missing space in an error message.
>
> Signed-off-by: Lubomir Rintel
Patch queued for 4.21, thanks.
> ---
> drivers/video/fbdev/pxa168fb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
On 12/03/2018 03:53 PM, Timur Tabi wrote:
> On 12/3/18 12:43 AM, Wen Yang wrote:
>> The null check on >cmap is redundant since cmap is a struct
>> inside fb_info and can never be null, so the check is always true.
>> we may remove it.
>>
>> Signed-off-by: Wen Yang
>
> Acked-by: Timur Tabi
On 12/02/2018 05:14 AM, Yangtao Li wrote:
> Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
>
> Signed-off-by: Yangtao Li
Patch queued for 4.21, thanks.
[ subject line was fixed to "fbdev" from "media" while applying ]
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R Institute
Regards
Shashank
On 12/12/2018 2:08 AM, Uma Shankar wrote:
This patch adds a blob property to get HDR metadata
information from userspace. This will be send as part
of AVI Infoframe to panel.
v2: Rebase and modified the metadata structure elements
as per Ville's POC changes.
Signed-off-by:
On 11/28/2018 04:37 PM, Colin King wrote:
> From: Colin Ian King
>
> There is a spelling mistake in the module parameter description, fix it.
>
> Signed-off-by: Colin Ian King
Patch queued for 4.21, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R Institute Poland
Samsung
On Thu, Dec 20, 2018 at 05:49:39PM +0200, Oleksandr Andrushchenko wrote:
> This is the only patch [1], no series. And at the moment I think
> there is nothing to review as I am not sure how to deal with those
> shmem pages: this patch is rather to start a discussion on how shmem
> pages can be
On 12/20/18 12:09 PM, Daniel Vetter wrote:
> On Thu, Dec 20, 2018 at 6:03 PM Alex Deucher wrote:
>>
>> + Harry
>>
>> On Thu, Dec 20, 2018 at 11:54 AM Daniel Vetter wrote:
>>>
>>> On Thu, Dec 20, 2018 at 5:40 PM Alex Deucher wrote:
+ Nicholas
On Thu, Dec 20, 2018 at 5:47 AM
On 11/26/2018 10:57 PM, Peter Rosin wrote:
> If there are extra logos (CONFIG_FB_LOGO_EXTRA) the heights of these
> extra logos are not considered when centering the first logo vertically.
>
> Signed-off-by: Peter Rosin
Patch queued for 4.21, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
On 11/26/2018 10:57 PM, Peter Rosin wrote:
> In preparation for allowing centering of the bootup logo, make
> fb_show_logo_line return where the next free framebuffer line is,
> instead of returning the height of the shown logo.
>
> Signed-off-by: Peter Rosin
Patch queued for 4.21, thanks.
On Thu, Dec 20, 2018 at 11:57:40AM -0500, Sean Paul wrote:
>
> Hi Dave and Daniel,
> A late spectre fix for you to pull for 4.20 final.
>
> drm-misc-fixes-2018-12-20:
> Fix spectre v1 vuln in drm_ioctl
>
> Cheers, Sean
Thanks, applied.
-Daniel
>
>
> The following changes since commit
Regards
Shashank
On 12/11/2018 11:44 PM, Uma Shankar wrote:
This patch attaches the colorspace connector property to the
hdmi connector. Based on colorspace change, modeset will be
triggered to switch to new colorspace.
Based on colorspace property value create an infoframe
with appropriate
Try to get the interconnect path for the GPU and vote for the maximum
bandwidth to support all frequencies. This is needed for performance.
Later we will want to scale the bandwidth based on the frequency to
also optimize for power but that will require some device tree
infrastructure that does
Add documentation for the interconnect and interconnect-names bindings
for the GPU node as detailed by bindings/interconnect/interconnect.txt.
Signed-off-by: Jordan Crouse
---
Documentation/devicetree/bindings/display/msm/gpu.txt | 4
1 file changed, 4 insertions(+)
diff --git
Add interconnect consumer definitions for the sdm845 GPU to device tree.
This patchset includes the a6xx gpu support for interconnect as previously
seen here:
https://patchwork.kernel.org/patch/10718587/
It was pulled into this patchset because the interconnect-name was removed from
the DT at
On Thu, Dec 20, 2018 at 6:16 PM Michel Dänzer wrote:
>
> On 2018-12-20 6:09 p.m., Daniel Vetter wrote:
> > On Thu, Dec 20, 2018 at 6:03 PM Alex Deucher wrote:
> >> On Thu, Dec 20, 2018 at 11:54 AM Daniel Vetter wrote:
> >
> >>> Not sure about the gamma thing since we had opposite bugs on i915
>
On 2018-12-20 6:09 p.m., Daniel Vetter wrote:
> On Thu, Dec 20, 2018 at 6:03 PM Alex Deucher wrote:
>> On Thu, Dec 20, 2018 at 11:54 AM Daniel Vetter wrote:
>
>>> Not sure about the gamma thing since we had opposite bugs on i915
>>> about gamma not being vsynced and tearing terribly. Cursor is
On Thu, Dec 20, 2018 at 02:21:20PM +0100, Hans de Goede wrote:
> Call intel_psr_enable() and intel_edp_drrs_enable() on pipe updates to make
> sure that we enable PSR / DRRS (when applicable) on fastsets.
>
> Note calling these functions when PSR / DRRS has already been enabled is a
> no-op, so
On Thu, Dec 20, 2018 at 6:03 PM Alex Deucher wrote:
>
> + Harry
>
> On Thu, Dec 20, 2018 at 11:54 AM Daniel Vetter wrote:
> >
> > On Thu, Dec 20, 2018 at 5:40 PM Alex Deucher wrote:
> > >
> > > + Nicholas
> > >
> > > On Thu, Dec 20, 2018 at 5:47 AM Daniel Vetter wrote:
> > > >
> > > > On Thu,
On Tue, Dec 18, 2018 at 05:06:38PM +0530, Jagan Teki wrote:
> On Sat, Dec 15, 2018 at 3:32 AM Sean Paul wrote:
> >
> > On Sat, Dec 15, 2018 at 02:11:01AM +0530, Jagan Teki wrote:
> > > Feiyang FY07024DI26A30-D is 1024x600, 4-lane MIPI-DSI LCD panel.
> > >
> > > Add panel driver for it.
> > >
> >
+ Harry
On Thu, Dec 20, 2018 at 11:54 AM Daniel Vetter wrote:
>
> On Thu, Dec 20, 2018 at 5:40 PM Alex Deucher wrote:
> >
> > + Nicholas
> >
> > On Thu, Dec 20, 2018 at 5:47 AM Daniel Vetter wrote:
> > >
> > > On Thu, Dec 20, 2018 at 10:07 AM Tomasz Figa wrote:
> > > >
> > > > Hi Helen,
> > >
On 11/19/2018 02:36 AM, YueHaibing wrote:
> 'info->modes' got allocated with devm_kcalloc in of_get_pxafb_display.
>
> This gives this error message:
> ./drivers/video/fbdev/pxafb.c:2238:2-7: WARNING: invalid free of devm_
> allocated data
>
> Fixes: c8f96304ec8b4 ("video: fbdev: pxafb:
Hi Dave and Daniel,
A late spectre fix for you to pull for 4.20 final.
drm-misc-fixes-2018-12-20:
Fix spectre v1 vuln in drm_ioctl
Cheers, Sean
The following changes since commit 7566ec393f4161572ba6f11ad5171fd5d59b0fbd:
Linux 4.20-rc7 (2018-12-16 15:46:55 -0800)
are available in the Git
On 12/20/2018 05:55 PM, Bartlomiej Zolnierkiewicz wrote:
>
> On 11/16/2018 12:02 PM, YueHaibing wrote:
>> 'info->modes' got allocated with devm_kcalloc in of_get_pxafb_display.
>>
>> This gives this error message:
>> ./drivers/video/fbdev/pxafb.c:2238:2-7: WARNING: invalid free of devm_
>>
On Thu, Dec 20, 2018 at 9:36 AM Brajeswar Ghosh
wrote:
>
> Remove reg_helper.h which is included more than once
>
> Signed-off-by: Brajeswar Ghosh
Applied. thanks!
Alex
> ---
> .../gpu/drm/amd/display/dc/i2caux/dce110/i2c_hw_engine_dce110.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff
On 11/16/2018 12:02 PM, YueHaibing wrote:
> 'info->modes' got allocated with devm_kcalloc in of_get_pxafb_display.
>
> This gives this error message:
> ./drivers/video/fbdev/pxafb.c:2238:2-7: WARNING: invalid free of devm_
> allocated data
>
> Signed-off-by: YueHaibing
Patch queued for
On Thu, Dec 20, 2018 at 9:36 AM Brajeswar Ghosh
wrote:
>
> Remove custom_float.h which is included more than once
>
> Signed-off-by: Brajeswar Ghosh
Applied. thanks!
Alex
> ---
> drivers/gpu/drm/amd/display/dc/dcn10/dcn10_hw_sequencer_debug.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff
On Thu, Dec 20, 2018 at 5:40 PM Alex Deucher wrote:
>
> + Nicholas
>
> On Thu, Dec 20, 2018 at 5:47 AM Daniel Vetter wrote:
> >
> > On Thu, Dec 20, 2018 at 10:07 AM Tomasz Figa wrote:
> > >
> > > Hi Helen,
> > >
> > > On Fri, Dec 14, 2018 at 10:35 AM Helen Koike
> > > wrote:
> > > >
> > > >
On Wed, Dec 19, 2018 at 3:41 AM Brajeswar Ghosh
wrote:
>
> Remove custom_float.h which is included more than once
>
> Signed-off-by: Brajeswar Ghosh
Applied. thanks!
Alex
> ---
> drivers/gpu/drm/amd/display/dc/dcn10/dcn10_hw_sequencer.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git
On Tue, Dec 18, 2018 at 8:06 AM Colin King wrote:
>
> From: Colin Ian King
>
> There are several variables that are defined and never used and hence can
> be removed. Remove them. Cleans up clang -Wunused-const-variable warnings:
>
> warning: ‘dvi_hdmi_dongle_signature_str’ defined but not used
On 11/26/2018 10:19 PM, Peter Rosin wrote:
> On 2018-11-26 15:33, Bartlomiej Zolnierkiewicz wrote:
>> On 11/26/2018 03:16 PM, Peter Rosin wrote:
>>> Ping?!
>>
>> Hi,
>>
>> Thank you for your patch, it will be considered for 4.21 (as it is not
>> a recent regression + I'm busy with other things
On 12/20/2018 9:36 PM, Winkler, Tomas wrote:
+static void __exit mei_hdcp_exit(void)
+{
+ mei_hdcp_component_cleanup(>dev);
Don’t think you can do that, no guarantees this will be valid pointer
As we discussed offline, we have the below line at cleanup.
So valid pointer is made sure. I
[ added dri-devel ML to Cc: ]
On 11/02/2018 11:23 PM, Alexey Khoroshilov wrote:
> clps711x_fb_probe() increments refcnt of disp device node by
> of_parse_phandle() and leaves it undecremented on both
> successful and error paths.
>
> Found by Linux Driver Verification project
+ Nicholas
On Thu, Dec 20, 2018 at 5:47 AM Daniel Vetter wrote:
>
> On Thu, Dec 20, 2018 at 10:07 AM Tomasz Figa wrote:
> >
> > Hi Helen,
> >
> > On Fri, Dec 14, 2018 at 10:35 AM Helen Koike
> > wrote:
> > >
> > > Hi Tomasz,
> > >
> > > On 12/13/18 2:02 AM, Tomasz Figa wrote:
> > > > On Thu,
[ added Petr & Sergey to Cc: ]
Hi,
On 10/30/2018 04:44 PM, Prarit Bhargava wrote:
> On text-based systems the 'quiet' boot option will show printk levels
> higher than CONSOLE_LOGLEVEL_QUIET. The displaying of the Tux logo
> during boot can cause some consoles to lose display data and as a
Hi,
On 11/26/2018 11:02 AM, Konstantin Khorenko wrote:
> Scrollback frame buffer is rather big - 32K,
> so it requires 3rd order page, so let's use kvmalloc() instead of
> ordinary kmalloc() for it.
Is it actually safe to use non-contiguous memory for softback_buf?
> Signed-off-by: Konstantin
https://bugs.freedesktop.org/show_bug.cgi?id=95517
--- Comment #11 from Dima ---
I don't know if it's relevant or not, due my using amdgpu-pro driver, but I get
this massages sometime:
[14849.076326] gmc_v8_0_process_interrupt: 165 callbacks suppressed
[14849.076331] amdgpu :01:00.0: GPU
From: C, Ramalingam
Sent: Thursday, December 20, 2018 18:00
To: Daniel Vetter ; Winkler, Tomas
Cc: Greg KH ; Rafael J. Wysocki
; intel-gfx ; dri-devel
; Sean Paul ; Shankar,
Uma ; Syrjala, Ville ;
Chris Wilson
Subject: Re: [PATCH v9 35/39] misc/mei/hdcp: Component framework for I915
On 12/19/2018 12:15 PM, C, Ramalingam wrote:
Tomas and Daniel,
From the discussion on this thread, I infer following understanding:
* At present(v9) I915 wants to be hard binded to mei_hdcp
device-driver binding status through components
o This means I915 driver load will get
https://bugs.freedesktop.org/show_bug.cgi?id=109117
--- Comment #4 from Michel Dänzer ---
We don't enable write-combining for the ring buffers though, do we?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
On 12/20/18 5:36 PM, Christoph Hellwig wrote:
On Tue, Dec 18, 2018 at 08:20:22PM +0100, Noralf Trønnes wrote:
+ if (!dma_map_sg(dev->dev, xen_obj->sgt->sgl, xen_obj->sgt->nents,
+ DMA_BIDIRECTIONAL)) {
Are you using the DMA streaming API as a way to flush the
On 12/18/2018 02:19 PM, Rob Clark wrote:
> On Fri, Oct 26, 2018 at 10:09 AM Rob Clark wrote:
>>
>> BACKLIGHT_CLASS_DEVICE is already tristate, but a dependency
>> FB_BACKLIGHT prevents it from being built as a module. There
>> doesn't seem to be any particularly good reason for this, so
>>
On Wed, Dec 19, 2018 at 02:14:52PM +0100, Gerd Hoffmann wrote:
>
> > > > + if (!dma_map_sg(dev->dev, xen_obj->sgt->sgl, xen_obj->sgt->nents,
> > > > + DMA_BIDIRECTIONAL)) {
> > >
> > >
> > > Are you using the DMA streaming API as a way to flush the caches?
> > Yes
> > > Does this
On Tue, Dec 18, 2018 at 08:20:22PM +0100, Noralf Trønnes wrote:
> > + if (!dma_map_sg(dev->dev, xen_obj->sgt->sgl, xen_obj->sgt->nents,
> > + DMA_BIDIRECTIONAL)) {
>
>
> Are you using the DMA streaming API as a way to flush the caches?
This looks rather broken. Please send
1 - 100 of 215 matches
Mail list logo
