On Fri, 6 Dec 2019 08:53:27 +0100
Boris Brezillon wrote:
> On Thu, 5 Dec 2019 17:08:02 -0600
> Rob Herring wrote:
>
> > On Fri, Nov 29, 2019 at 8:33 AM Boris Brezillon
> > wrote:
> > >
> > > On Fri, 29 Nov 2019 14:24:48 +
> > > Steven Price wrote:
> > >
> > > > On 29/11/2019 13:59,
On Thu, Dec 5, 2019 at 11:13 AM Paolo Bonzini wrote:
>
> On 04/12/19 22:41, syzbot wrote:
> > syzbot has bisected this bug to:
> >
> > commit 2de50e9674fc4ca3c6174b04477f69eb26b4ee31
> > Author: Russell Currey
> > Date: Mon Feb 8 04:08:20 2016 +
> >
> > powerpc/powernv: Remove support f
On 2019/12/05 19:16, Dmitry Vyukov wrote:
> On Thu, Dec 5, 2019 at 11:13 AM Paolo Bonzini wrote:
>>
>> On 04/12/19 22:41, syzbot wrote:
>>> syzbot has bisected this bug to:
>>>
>>> commit 2de50e9674fc4ca3c6174b04477f69eb26b4ee31
>>> Author: Russell Currey
>>> Date: Mon Feb 8 04:08:20 2016 +
Hello,
syzbot found the following crash on:
HEAD commit:282ffdf3 Add linux-next specific files for 20191205
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=165627f2e0
kernel config: https://syzkaller.appspot.com/x/.config?x=29372c0243b4b980
dashboard
Panfrost driver is shouting an error if the regulator init
return an -EPROBE_DEFFER. This is a not a real error and
it doesn't require to be display.
Check if the error is not an EPROBE_DEFFER before displaying it.
Signed-off-by: Clément Péron
---
drivers/gpu/drm/panfrost/panfrost_device.c | 6
On Thu, Dec 5, 2019 at 3:13 PM Yongqiang Niu wrote:
>
> please double confirm is this dump stack log is ruining on MT8173 real
> IC or not.
> if yes, that may caused ovl hang when disable layer not in blanking,
> then cause vblank time out.
> i will disable overlay with cmdq in next version.
>
It
Hi Jani,
Thanks for the review.
On Wed, Nov 20, 2019 at 6:41 AM Jani Nikula wrote:
>
> On Mon, 04 Nov 2019, Rajat Jain wrote:
> > Move the code that populates the ACPI device ID for devices, into
> > more appripriate intel_acpi.c. This is done in preparation for more
> > users of this code (in
Certain laptops now come with panels that have integrated privacy
screens on them. This patch adds support for such panels by adding
a privacy-screen property to the intel_connector for the panel, that
the userspace can then use to control and check the status.
Identifying the presence of privacy
Lookup and attach ACPI nodes for intel connectors. The lookup is done
in compliance with ACPI Spec 6.3
https://uefi.org/sites/default/files/resources/ACPI_6_3_final_Jan30.pdf
(Ref: Pages 1119 - 1123).
This can be useful for any connector specific platform properties. (This
will be used for privacy
czw., 5 gru 2019 o 09:11 Linus Walleij napisał(a):
>
> The PWM backlight still supports passing a enable GPIO line as
> platform data using the legacy API.
>
> It turns out that ever board using this mechanism except one
> is pass .enable_gpio = -1. So we drop all these cargo-culted -1's
> from a
On Wed, Nov 20, 2019 at 7:04 AM Jani Nikula wrote:
>
> On Mon, 04 Nov 2019, Rajat Jain wrote:
> > Certain laptops now come with panels that have integrated privacy
> > screens on them. This patch adds support for such panels by adding
> > a privacy-screen property to the intel_connector for the p
On Thu, Dec 5, 2019 at 11:53 AM Paolo Bonzini wrote:
>
> On 05/12/19 11:31, Dmitry Vyukov wrote:
> >> Ah, and because the machine is a KVM guest, kvm_wait appears in a lot of
> >> backtrace and I get to share syzkaller's joy every time. :)
> > I don't see any mention of "kvm" in the crash report.
+ Zhao Yakui
On 12/5/19 10:55 AM, Jani Nikula wrote:
> On Wed, 04 Dec 2019, Benjamin GAIGNARD wrote:
>> On 12/4/19 10:35 AM, Thomas Zimmermann wrote:
>>> Hi
>>>
>>> Am 19.11.19 um 14:47 schrieb Benjamin Gaignard:
When compiling with W=1 few warnings about unused variables show up.
This
On Wed, Nov 20, 2019 at 6:51 AM Jani Nikula wrote:
>
> On Mon, 04 Nov 2019, Rajat Jain wrote:
> > Lookup and attach ACPI nodes for intel connectors. The lookup is done
> > in compliance with ACPI Spec 6.3
> > https://uefi.org/sites/default/files/resources/ACPI_6_3_final_Jan30.pdf
> > (Ref: Pages
The driver forgets to call component_del in remove to match component_add
in probe.
Add the missed call to fix it.
Signed-off-by: Chuhong Yuan
---
drivers/gpu/drm/exynos/exynos_drm_gsc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_gsc.c
b/drivers/gpu/dr
On 2019/12/05 19:22, Paolo Bonzini wrote:
> Ah, and because the machine is a KVM guest, kvm_wait appears in a lot of
> backtrace and I get to share syzkaller's joy every time. :)
>
> This bisect result is bogus, though Tetsuo found the bug anyway.
> Perhaps you can exclude commits that only touch
Add ctm property support
Signed-off-by: Yongqiang Niu
---
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 10 -
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 61 -
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 11 ++
3 files changed, 80 insertions(+), 2 deletion
In qxl_gem_object_create_with_handle(), handle's memory is not
allocated on the heap. Checking for failure of handle via BUG_ON
is unnecessary. This patch eliminates the check.
Signed-off-by: Aditya Pakki
---
drivers/gpu/drm/qxl/qxl_gem.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/driver
On Thu, Dec 5, 2019 at 11:41 AM Tetsuo Handa
wrote:
>
> On 2019/12/05 19:22, Paolo Bonzini wrote:
> > Ah, and because the machine is a KVM guest, kvm_wait appears in a lot of
> > backtrace and I get to share syzkaller's joy every time. :)
> >
> > This bisect result is bogus, though Tetsuo found th
Hello,
syzbot found the following crash on:
HEAD commit:2f13437b Merge tag 'trace-v5.5-2' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=104fcc2ae0
kernel config: https://syzkaller.appspot.com/x/.config?x=608557e57ce07817
da
On Thu, Dec 5, 2019 at 11:22 AM Paolo Bonzini wrote:
>
> On 05/12/19 11:16, Dmitry Vyukov wrote:
> > On Thu, Dec 5, 2019 at 11:13 AM Paolo Bonzini wrote:
> >>
> >> On 04/12/19 22:41, syzbot wrote:
> >>> syzbot has bisected this bug to:
> >>>
> >>> commit 2de50e9674fc4ca3c6174b04477f69eb26b4ee31
>
The driver uses kfree() to release the resource allocated by
framebuffer_alloc(), which does not match.
Use framebuffer_release() instead to fix it.
Fixes: 638772c7553f ("fb: add support of LCD display controller on pxa168/910
(base layer)")
Signed-off-by: Chuhong Yuan
---
drivers/video/fbdev/p
On Thu, Dec 5, 2019 at 3:05 PM Daniel Vetter wrote:
>
> On Thu, Dec 5, 2019 at 2:38 PM syzbot
> wrote:
> >
> > syzbot has bisected this bug to:
> >
> > commit 979c11ef39cee79d6f556091a357890962be2580
> > Author: Ayan Kumar Halder
> > Date: Tue Jul 17 17:13:46 2018 +
> >
> > drm/sun4i:
nv50_msto_disable() does not call nv50_outp_release() to match
nv50_outp_acquire() like other disable().
Add the missed call to fix it.
Signed-off-by: Chuhong Yuan
---
drivers/gpu/drm/nouveau/dispnv50/disp.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/n
Move the code that populates the ACPI device ID for devices, into
more appripriate intel_acpi.c. This is done in preparation for more
users of this code (in next patch).
Signed-off-by: Rajat Jain
---
v3: * Renamed the function to intel_acpi_*
* Used forward declaration for structure instead o
The driver forgets to free the requested irq in remove and probe
failure.
Add the missed calls to fix it.
Signed-off-by: Chuhong Yuan
---
Changes in v2:
- Modify commit message.
drivers/video/fbdev/vesafb.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/video/fbdev/vesafb.c b/d
syzbot has bisected this bug to:
commit 979c11ef39cee79d6f556091a357890962be2580
Author: Ayan Kumar Halder
Date: Tue Jul 17 17:13:46 2018 +
drm/sun4i: Substitute sun4i_backend_format_is_yuv() with format->is_yuv
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15d2f97ee00
On Thu, Dec 5, 2019 at 11:41 AM Tetsuo Handa
wrote:
>
> On 2019/12/05 19:22, Paolo Bonzini wrote:
> > Ah, and because the machine is a KVM guest, kvm_wait appears in a lot of
> > backtrace and I get to share syzkaller's joy every time. :)
> >
> > This bisect result is bogus, though Tetsuo found th
drivers/gpu/drm/tegra/sor.c:3984:12: warning: 'tegra_sor_resume' defined but
not used [-Wunused-function]
drivers/gpu/drm/tegra/sor.c:3970:12: warning: 'tegra_sor_suspend' defined but
not used [-Wunused-function]
drivers/gpu/drm/tegra/sor.c:3937:12: warning: 'tegra_sor_runtime_resume'
defined bu
On Wed, Dec 4, 2019 at 10:27 AM Tomi Valkeinen wrote:
>
> Hi Andrey,
>
> On 19/06/2019 08:27, Andrey Smirnov wrote:
>
> > @@ -748,22 +748,19 @@ static int tc_set_video_mode(struct tc_data *tc,
> >
> > static int tc_wait_link_training(struct tc_data *tc)
> > {
> > - u32 timeout = 1000;
> >
>
> Hi Jerry,
>
> On Tue, 26 Nov 2019 at 08:14, Jerry Han wrote:
> >
> > Support Boe Himax8279d 8.0" 1200x1920 TFT LCD panel, it is a MIPI DSI
> > panel.
> >
> > V9:
> > - Adjust init code, make the format more concise
> > - kill off default_off_cmds (Emil)
> > - use mipi_dsi_dcs_set_display_{on,o
Support Boe Himax8279d 8.0" 1200x1920 TFT LCD panel, it is a MIPI DSI
panel.
V9:
- Adjust init code, make the format more concise
- kill off default_off_cmds (Emil)
- use mipi_dsi_dcs_set_display_{on,off} in their enable/disable
callbacks. (Emil)
- Adjusting the delay function (Emil)
V8:
- mo
Several MGA G200 SE machines don't respect the value of the startadd
register field. After more feedback on affected machines, neither PCI
subvendor ID nor the internal ID seem to hint towards the bug. All
affected machines have a PCI ID of 0x0522 (i.e., G200 SE A). It was
decided to flag all G200
From: Thomas Hellstrom
The drm/ttm module is using a modified on-stack copy of the
struct vm_area_struct to be able to set a page protection with customized
caching. Fix that by adding a vmf_insert_mixed_prot() function similar
to the existing vmf_insert_pfn_prot() for use with drm/ttm.
I'd like
From: Thomas Hellstrom
The TTM module today uses a hack to be able to set a different page
protection than struct vm_area_struct::vm_page_prot. To be able to do
this properly, add the needed vm functionality as vmf_insert_mixed_prot().
Cc: Andrew Morton
Cc: Michal Hocko
Cc: "Matthew Wilcox (Or
From: Thomas Hellstrom
TTM graphics buffer objects may, transparently to user-space, move
between IO and system memory. When that happens, all PTEs pointing to the
old location are zapped before the move and then faulted in again if
needed. When that happens, the page protection caching mode- an
[Why]
When change the connection status in a MST topology, mst device
which detect the event will send out CONNECTION_STATUS_NOTIFY messgae.
e.g. src-mst-mst-sst => src-mst (unplug) mst-sst
Currently, under the above case of unplugging device, ports which have
been allocated payloads and are no l
A call to udl_render_hline() returns the number of identical and
sent pixels. None of these values is used. Remove the parameters.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Emil Velikov
Acked-by: Gerd Hoffmann
---
drivers/gpu/drm/udl/udl_drv.h | 3 +--
drivers/gpu/drm/udl/udl_fb.c
Udl's damage-handling code requires clean up before switching the driver
to simple-pipe helpers. Patches 1, 2 and 7 remove unused state variables
and statistics. Patches 3 to 5 reorganize the damage handler to be more
readable. Patch 6 moves dma-buf begin/end calls into the damage handler,
so they
Computing the clip rectable in a separate helper function makes the
damage-handler code more readable.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Emil Velikov
Acked-by: Gerd Hoffmann
---
drivers/gpu/drm/udl/udl_fb.c | 48
1 file changed, 32 insertions(+)
None of the udl driver's statistics counters is used anywhere. Remove
them.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Emil Velikov
Acked-by: Gerd Hoffmann
---
drivers/gpu/drm/udl/udl_drv.h | 4
drivers/gpu/drm/udl/udl_fb.c | 14 +-
2 files changed, 1 insertion(+), 17 del
We now do the fast tests before the potentially expensive vmap operation.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Emil Velikov
Acked-by: Gerd Hoffmann
---
drivers/gpu/drm/udl/udl_fb.c | 19 +++
drivers/gpu/drm/udl/udl_transfer.c | 1 -
2 files changed, 7 insertions
The field lost_pixels in struct udl_device was supposed to signal an
error during USB transfers of the framebuffer data. The driver would
have to schedule a re-transfer at a later point. This code was never
implemented. Remove lost_pixels and return regular error codes instead.
Signed-off-by: Thom
Computing the cpp value's logarithm in a separate helper function makes
the damage-handler code more readable.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Emil Velikov
Acked-by: Gerd Hoffmann
---
drivers/gpu/drm/udl/udl_fb.c | 17 -
1 file changed, 12 insertions(+), 5 deletio
The damage-handler code now invokes dma_buf_{begin,end}_access()
for imported buffers. These calls were missing from the page-flip
and modesetting code paths. The patch also fixes an bug in the
orignal where an error code was overwritten by the result of
dma_buf_end_cpu_access().
v2:
* onl
The GMA500 driver is using the legacy GPIO API to fetch
three optional display control GPIO lines from the SFI
description used by the Medfield platform.
Switch this over to use GPIO descriptors and delete the
custom platform data.
We create three new static locals in the tc35876x bridge
code but
Add bindings for iMX8MQ Display Controller Subsystem.
Signed-off-by: Laurentiu Palcu
Reviewed-by: Rob Herring
---
.../bindings/display/imx/nxp,imx8mq-dcss.yaml | 86 ++
1 file changed, 86 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/imx/n
Currently the drm/imx/ directory is compiled only if DRM_IMX is set. Adding a
new IMX related IP in the same directory would need DRM_IMX to be set, which
would
bring in also IPUv3 core driver...
The current patch would allow adding new IPs in the imx/ directory without
needing
to set DRM_IMX.
Hi,
This patchset adds initial DCSS support for iMX8MQ chip. Initial support
includes only graphics plane support (no video planes), no HDR10 capabilities,
no graphics decompression (only linear, tiled and super-tiled buffers allowed).
Support for the rest of the features will be added incrementa
On 05/12/2019 22:11, Clément Péron wrote:
> Panfrost driver is shouting an error if the regulator init
> return an -EPROBE_DEFFER. This is a not a real error and
> it doesn't require to be display.
>
> Check if the error is not an EPROBE_DEFFER before displaying it.
>
> Signed-off-by: Clément Pér
> Several MGA G200 SE machines don't respect the value of the startadd
> register field. After more feedback on affected machines, neither PCI
> subvendor ID nor the internal ID seem to hint towards the bug. All
> affected machines have a PCI ID of 0x0522 (i.e., G200 SE A). It was
> decided to flag
On Thu, Dec 05, 2019 at 11:15:23PM +0100, Daniel Vetter wrote:
> On Thu, Nov 28, 2019 at 12:39:30PM +0100, Gerd Hoffmann wrote:
> > On Wed, Nov 27, 2019 at 10:25:22AM +0100, Gerd Hoffmann wrote:
> > > The fake offset is going to stay, so change the calling convention for
> > > drm_gem_object_funcs.
On Thu, Dec 05, 2019 at 05:42:31PM -0600, Aditya Pakki wrote:
> In qxl_gem_object_create_with_handle(), handle's memory is not
> allocated on the heap. Checking for failure of handle via BUG_ON
> is unnecessary. This patch eliminates the check.
The check makes sure the caller doesn't pass in handl
On Fri, Dec 6, 2019 at 11:07 AM Gerd Hoffmann wrote:
>
> On Thu, Dec 05, 2019 at 11:15:23PM +0100, Daniel Vetter wrote:
> > On Thu, Nov 28, 2019 at 12:39:30PM +0100, Gerd Hoffmann wrote:
> > > On Wed, Nov 27, 2019 at 10:25:22AM +0100, Gerd Hoffmann wrote:
> > > > The fake offset is going to stay,
On Fri, Dec 06, 2019 at 11:07:24AM +0100, Gerd Hoffmann wrote:
> On Thu, Dec 05, 2019 at 11:15:23PM +0100, Daniel Vetter wrote:
> > Looks like unrelated flukes, this happens occasionally. If you're paranoid
> > hit the retest button on patchwork to double-check.
> > -Daniel
>
> Guess you kicked CI
Hi Adrian,
And sorry for this late reply.
Your patches look good and we ("stm guys") understand that v1.01 is very
different to v1.30/31.
We are doing our best to review & test your patches and we will go back
to you asap.
Many thanks,
Philippe :-)
On 12/2/19 8:33 PM, Adrian Ratiu wrote:
> Ha
On Fri 06-12-19 09:24:26, Thomas Hellström (VMware) wrote:
[...]
> @@ -283,11 +282,26 @@ vm_fault_t ttm_bo_vm_fault_reserved(struct vm_fault
> *vmf,
> pfn = page_to_pfn(page);
> }
>
> + /*
> + * Note that the value of @prot at this poi
On Fri, Dec 6, 2019 at 11:22 AM Gerd Hoffmann wrote:
>
> On Fri, Dec 06, 2019 at 11:07:24AM +0100, Gerd Hoffmann wrote:
> > On Thu, Dec 05, 2019 at 11:15:23PM +0100, Daniel Vetter wrote:
> > > Looks like unrelated flukes, this happens occasionally. If you're paranoid
> > > hit the retest button on
Add a missing 'depends on DRM' for the DRM_DP_CEC config
option. Without that enabling DRM_DP_CEC will force CEC_CORE
to =y instead of =m if DRM=m as well.
Signed-off-by: Hans Verkuil
---
diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index 1168351267fd..e8e478d6da9c 100644
--- a/
Hallo Thomas,
On Thursday, 5 December 2019 18:20:06 GMT Thomas Zimmermann wrote:
> Hi
>
> Am 05.12.19 um 17:30 schrieb Mihail Atanassov:
> > The 'dev' name causes some confusion with 'struct device' [1][2], so use
> > 'drm' instead since this seems to be the prevalent name for 'struct
> > drm_dev
https://bugzilla.kernel.org/show_bug.cgi?id=205661
Artem S. Tashkinov (a...@gmx.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Hi
Am 06.12.19 um 12:25 schrieb Mihail Atanassov:
> Hallo Thomas,
>
> On Thursday, 5 December 2019 18:20:06 GMT Thomas Zimmermann wrote:
>> Hi
>>
>> Am 05.12.19 um 17:30 schrieb Mihail Atanassov:
>>> The 'dev' name causes some confusion with 'struct device' [1][2], so use
>>> 'drm' instead since
On Fri, Dec 06, 2019 at 12:10:15PM +0100, Daniel Vetter wrote:
> On Fri, Dec 6, 2019 at 11:22 AM Gerd Hoffmann wrote:
> >
> > > Guess you kicked CI? Just got CI mails, now reporting success, without
> > > doing anything. So I'll go push v3 to misc-next.
> >
> > Oops, spoke too soon. Next mail a
Udl has a single display pipeline with a primary plane; perfect for
simple-pipe helpers. Convert it over. The old encoder and CRTC code
becomes unused and obsolete.
Exported formats for the primary plane are RGB565 and XRGB, with
the latter being emulated. The 16-bit format is the default and
With only a single display pipeline and primary plane, udl is perfect
for simple-pipe helpers. Patches 1 to 4 do the convertion. This enables
atomic modesetting for udl devices.
Patches 5 to 8 clean up handling of color depth and framebuffers. With
universal planes that come with simple pipe, disp
The only caller of udl_handle_damage() in the plane-update function
in udl_modeset.c. Move udl_handle_damage() there.
v2:
* remove udl_fb.c in a separate patch
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Vetter
Reviewed-by: Emil Velikov
---
drivers/gpu/drm/udl/udl_drv.h |
DPMS functionality is only used by the CRTC's enable and disable
functions. Inline the code.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/udl/udl_modeset.c | 84 +++
1 file changed, 30 insertions(+), 54 deletions(-)
diff --git a/drivers/gpu/drm/udl/udl_modese
We can use the generic suspend/resume helpers for atomic modesetting.
Switch udl over.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/udl/udl_drv.c | 7 ++-
drivers/gpu/drm/udl/udl_drv.h | 1 -
drivers/gpu/drm/udl/udl_modeset.c | 14 --
3 files changed, 2 insertio
The current default color depth of 24 bpp is not even supported by
the driver. Being the native format for communicating with the adapter,
16 bpp is the correct choice.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/udl/udl_drv.c | 2 +-
drivers/gpu/drm/udl/udl_modeset.c | 2 +-
2 file
The remaining code in udl_fb.c is unused. Remove the file entirely.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/udl/Makefile | 2 +-
drivers/gpu/drm/udl/udl_fb.c | 51
2 files changed, 1 insertion(+), 52 deletions(-)
delete mode 100644 drivers/gpu/
To mimic simple-pipe, we initialize the connector before the rest of
the display pipeline.
v2:
* remove unnecessary calls to drm_connector_{register,unregister}()
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/udl/udl_connector.c | 9 +++--
drivers
The infrastruture for atomic modesetting allows us to use the generic
code for dirty-FB and damage handling. Switch over udl and remove the
driver's implementation. The simple-pipe's update function now picks up
the primary plane's damage and updates a minimal region of the screen.
Signed-off-by:
The udl driver stores the currently active framebuffer to know from
where to accept damage updates.
With the conversion to plane-state damage handling, this is not necessary
any longer. The currently active framebuffer and damaged area are always
stored in the plane state.
Signed-off-by: Thomas Z
On Thu, Dec 05, 2019 at 09:39:35PM +0200, Ville Syrjälä wrote:
> On Tue, Dec 03, 2019 at 12:36:27PM -0500, Sean Paul wrote:
> > From: Sean Paul
> >
> > Now that we can rely on transcoder disable to toggle signalling off,
> > it's less of a catastrophe if get_hw_state() returns false.
> >
> > Onc
From: Thierry Reding
CRTC is an abbreviation and should be all caps in prose. Update all
kerneldoc comments to use a consistent spelling.
v2: remove hunk unrelated to the CRTC spelling fixes
Reviewed-by: Thomas Zimmermann
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/drm_atomic.c
From: Thierry Reding
These are just a couple of things that I came across as I was reading
through the code and comments.
v2: added one more hunk that ended up in the wrong patch
Reviewed-by: Thomas Zimmermann
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/drm_atomic_helper.c | 12 ++-
On Thu, Dec 05, 2019 at 09:33:19PM +0200, Ville Syrjälä wrote:
> On Tue, Dec 03, 2019 at 12:36:26PM -0500, Sean Paul wrote:
> > From: Sean Paul
> >
> > Currently we rely on intel_hdcp_disable() to disable HDCP signalling in
> > the DDI Function Control register. This patch adds a safety net by al
Hi Michal,
On Fri, 2019-12-06 at 11:30 +0100, Michal Hocko wrote:
> On Fri 06-12-19 09:24:26, Thomas Hellström (VMware) wrote:
> [...]
> > @@ -283,11 +282,26 @@ vm_fault_t ttm_bo_vm_fault_reserved(struct
> > vm_fault *vmf,
> > pfn = page_to_pfn(page);
> > }
> >
>
On Fri 06-12-19 14:16:10, Thomas Hellstrom wrote:
> Hi Michal,
>
> On Fri, 2019-12-06 at 11:30 +0100, Michal Hocko wrote:
> > On Fri 06-12-19 09:24:26, Thomas Hellström (VMware) wrote:
> > [...]
> > > @@ -283,11 +282,26 @@ vm_fault_t ttm_bo_vm_fault_reserved(struct
> > > vm_fault *vmf,
> > >
On Hyper-V, Generation 1 VMs can directly use VM's physical memory for
their framebuffers. This can improve the efficiency of framebuffer and
overall performence for VM. The physical memory assigned to framebuffer
must be contiguous. We use CMA allocator to get contiguouse physicial
memory when the
On 18. 11. 19 12:41, Chuhong Yuan wrote:
The driver forgets to disable the regulator in remove like what is done
in probe failure.
Add the missed call to fix it.
Signed-off-by: Chuhong Yuan
---
drivers/video/fbdev/ssd1307fb.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/vide
Hi Daniel,
Thank you for your feedback!
> From: Daniel Vetter On Behalf Of Daniel Vetter
> Sent: 07 November 2019 19:30
> Subject: Re: [PATCH v3 3/8] drm: Add bus timings helper
>
> On Thu, Nov 07, 2019 at 09:26:21PM +0200, Laurent Pinchart wrote:
> > Hi Fabrizio,
> >
> > Thank you for the patc
Hi Rob,
> From: Rob Herring
> Sent: 29 August 2019 15:03
> Subject: Re: [PATCH v3 1/8] dt-bindings: display: Add bindings for LVDS
> bus-timings
>
> On Wed, Aug 28, 2019 at 1:36 PM Fabrizio Castro
> wrote:
> >
> > Dual-LVDS connections need markers in the DT, this patch adds
> > some common do
Hi Laurent,
Thank you for your feedback!
> From: devicetree-ow...@vger.kernel.org On
> Behalf Of Laurent Pinchart
> Sent: 07 November 2019 18:01
> Subject: Re: [PATCH v3 1/8] dt-bindings: display: Add bindings for LVDS
> bus-timings
>
> Hello Fabrizio,
>
> On Thu, Aug 29, 2019 at 02:38:06PM
Hello,
syzbot found the following crash on:
HEAD commit:b0d4beaa Merge branch 'next.autofs' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11b97e41e0
kernel config: https://syzkaller.appspot.com/x/.config?x=f07a23020fd7d21a
da
Hi Laurent,
Thank you for your feedback!
> From: Laurent Pinchart
> Sent: 07 November 2019 18:12
> Subject: Re: [PATCH v3 2/8] dt-bindings: display: Add idk-2121wr binding
>
> Hi Fabrizio,
>
> Thank you for the patch.
>
> On Wed, Aug 28, 2019 at 07:36:36PM +0100, Fabrizio Castro wrote:
> > Ad
Hi Laurent,
Thank you for your feedback!
> From: linux-kernel-ow...@vger.kernel.org
> On Behalf Of Laurent Pinchart
> Sent: 07 November 2019 19:26
> Subject: Re: [PATCH v3 3/8] drm: Add bus timings helper
>
> Hi Fabrizio,
>
> Thank you for the patch.
>
> On Wed, Aug 28, 2019 at 07:36:37PM +0
On 2019-12-05 11:55 a.m., David (Dingchen) Zhang wrote:
> [why]
> We need to minimally initialize the remote aux channel, e.g. the
> crc work struct of remote aux to dump the sink's DPRX CRCs in MST
> setup.
>
> [how]
> Add helper that only initializes the crc work struct of the remote
> aux, hook
On 2019-12-06 10:30 a.m., Harry Wentland wrote:
> On 2019-12-05 11:55 a.m., David (Dingchen) Zhang wrote:
>> [why]
>> We need to minimally initialize the remote aux channel, e.g. the
>> crc work struct of remote aux to dump the sink's DPRX CRCs in MST
>> setup.
>>
>> [how]
>> Add helper that only i
On Thu, Nov 28, 2019 at 2:54 PM Robin Murphy wrote:
>
> When we have devfreq, also try to register a basic cooling device in
> case GPU workloads manage to hit thermal throttling thresholds.
>
> Signed-off-by: Robin Murphy
> ---
> drivers/gpu/drm/panfrost/panfrost_devfreq.c | 32 ++--
On Fri, Nov 29, 2019 at 7:59 AM Boris Brezillon
wrote:
>
> Hello,
>
> I've recently come to test a 5.4 kernel on a rk3288 platform (T760),
> and, as reported by many people on #panfrost, I've hit a page-fault
> storm when running various GL apps.
>
> This series tries to address the problems I cou
On Mon, Nov 18, 2019 at 11:30 AM Steven Price wrote:
>
> Currently when setting a frequency in panfrost_devfreq_target the
> returned frequency is the actual frequency that the clock driver reports
> (the return of clk_get_rate()). However, where the provided OPPs don't
> precisely match the frequ
> On Dec 6, 2019, at 4:04 AM, Gerd Hoffmann wrote:
>
>> Several MGA G200 SE machines don't respect the value of the startadd
>> register field. After more feedback on affected machines, neither PCI
>> subvendor ID nor the internal ID seem to hint towards the bug. All
>> affected machines have a
Reviewed-by: Lyude Paul
I'll go ahead and push this to drm-misc-next-fixes right now, thanks!
On Thu, 2019-12-05 at 17:00 +0800, Wayne Lin wrote:
> [Why]
>
> This patch is trying to address the issue observed when hotplug DP
> daisy chain monitors.
>
> e.g.
> src-mstb-mstb-sst -> src (unplug)
The pull request you sent on Fri, 6 Dec 2019 13:31:06 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2019-12-06
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7ada90eb9c7ae4a8eb066f8e9b4d80122f0363db
Thank you!
--
Deet-doot-dot, I am a bot.
https://kor
On Fri, 2019-12-06 at 14:24 -0500, Lyude Paul wrote:
> Reviewed-by: Lyude Paul
>
> I'll go ahead and push this to drm-misc-next-fixes right now, thanks!
Whoops-meant to say drm-misc-next here, anyway, pushed!
>
> On Thu, 2019-12-05 at 17:00 +0800, Wayne Lin wrote:
> > [Why]
> >
> > This patch
[AMD Official Use Only - Internal Distribution Only]
Hi All:
I just checked the CI report
https://patchwork.freedesktop.org/series/70530/. The failures described in
there are not quite related to my patch. Seems it is a false-positive. Does
anyone know something about the issue described i
[why]
We need to minimally initialize the remote aux channel, e.g. the
crc work struct of remote aux to dump the sink's DPRX CRCs in MST
setup.
[how]
Add helper that only initializes the crc work struct of the remote
aux, hooke crc work queue to 'drm_dp_aux_crc_work'. Then call this
helper in DP M
dpu_hw_ctl* is checked for NULL when passed as an argument
to several functions. It will never be NULL, so remove the
checks.
Signed-off-by: Drew Davenport
---
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 10 --
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c | 12 ++-
dpu_encoder_virt.phys_encs[0:num_phys_encs-1] will not be NULL so don't
check.
Also fix multiline strings that caused checkpatch warning.
Signed-off-by: Drew Davenport
---
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 162
1 file changed, 61 insertions(+), 101 deletions(-)
1 - 100 of 111 matches
Mail list logo
