Hi Dave and Daniel,
here are the 2 fixes from this week's drm-misc-next.
Best regards
Thomas
drm-misc-fixes-2021-01-27:
* drm/vc4: Fix LBM size calculation; Fix high resolutions for hvs5
The following changes since commit a37eef63bc9e16e06361b539e528058146af80ab:
drm/syncobj: Fix
Hey Dave,
Mostly a regression fixes here, a couple of which could lead to
display hanging, and have been affecting a number of users.
Ben.
The following changes since commit 8ef23b6f6a79e6fa2a169081d2d76011fffa0482:
drm/nouveau/disp/ga10[24]: initial support (2021-01-15 10:25:24 +1000)
are
On Tue, 26 Jan 2021 17:58:34 +0100,
Uwe Kleine-König wrote:
>
> All amba drivers return 0 in their remove callback. Together with the
> driver core ignoring the return value anyhow, it doesn't make sense to
> return a value here.
>
> Change the remove prototype to return void, which makes it
On Wed, Jan 27, 2021 at 02:19:27PM +0800, carlis wrote:
> hi,i will fix it like below:
> par->gpio.te = devm_gpiod_get_index_optional(dev, "te", 0,
> GPIOD_IN); if (IS_ERR(par->gpio.te)) {
> rc = PTR_ERR(par->gpio.te);
> pr_err("Failed to request te gpio: %d\n",
On Tue, Jan 26, 2021 at 05:58:34PM +0100, Uwe Kleine-König wrote:
> All amba drivers return 0 in their remove callback. Together with the
> driver core ignoring the return value anyhow, it doesn't make sense to
> return a value here.
>
> Change the remove prototype to return void, which makes it
On Wed, Jan 27, 2021 at 09:32:20AM +0800, Carlis wrote:
> @@ -82,6 +111,29 @@ enum st7789v_command {
> */
> static int init_display(struct fbtft_par *par)
> {
> + int rc;
> + struct device *dev = par->info->device;
> +
> + par->gpio.te = devm_gpiod_get_index_optional(dev, "te", 0,
On Wed, Jan 27, 2021 at 09:32:20AM +0800, Carlis wrote:
> @@ -82,6 +111,29 @@ enum st7789v_command {
> */
> static int init_display(struct fbtft_par *par)
> {
> + int rc;
> + struct device *dev = par->info->device;
> +
> + par->gpio.te = devm_gpiod_get_index_optional(dev, "te", 0,
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #5 from Jerome C (m...@jeromec.com) ---
Created attachment 294879
--> https://bugzilla.kernel.org/attachment.cgi?id=294879=edit
Kernel log
Unfortunately it crashed again although I've noticed it's been crashing a lot
less (4-5
https://bugzilla.kernel.org/show_bug.cgi?id=211033
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
Am 2021-01-21 um 2:40 p.m. schrieb Daniel Vetter:
> Recently there was a fairly long thread about recoreable hardware page
> faults, how they can deadlock, and what to do about that.
>
> While the discussion is still fresh I figured good time to try and
> document the conclusions a bit.
>
>
https://bugzilla.kernel.org/show_bug.cgi?id=211033
Shawn Anastasio (sh...@anastas.io) changed:
What|Removed |Added
CC||sh...@anastas.io
On Tue, Jan 26, 2021 at 9:53 PM Andy Shevchenko
wrote:
>
> On Tue, Jan 26, 2021 at 8:33 PM Hans de Goede wrote:
> > On 1/26/21 6:14 PM, Andy Shevchenko wrote:
> > > On Tue, Jan 26, 2021 at 6:55 PM Patrik Jakobsson
> > > wrote:
> > >> On Tue, Jan 26, 2021 at 4:51 PM Andy Shevchenko
> > >>
To charge device memory allocations, we need to (1) identify appropriate
cgroup to charge (currently decided at object creation time), and (2)
make the charging call at the time that memory pages are being allocated.
For (1), see prior DRM patch which associates current task's cgroup with
GEM
Following control is introduced in order to display total memory that
exists for the DRM device. DRM drivers can advertise this value by
writing to drm_device.drmcg_props. This is needed in order to effectively
use the other memory controls.
Normally for system memory this is available to the user
Add basic .seq_show and .write functions for use with DRM cgroup control
files. This is based on original work from Kenny Ho and extracted from
patches [1] and [2]. Has been simplified to remove having different file
types and functions for each.
[1]
From: Kenny Ho
drmcg initialization involves allocating a per cgroup, per device data
structure and setting the defaults. There are two entry points for
drmcg init:
1) When struct drmcg is created via css_alloc, initialization is done
for each device
2) When DRM devices are created after
This patch adds tracking of which cgroup to make charges against for a
given GEM object. We associate the current task's cgroup with GEM objects
as they are created. First user of this is for charging DRM cgroup for
device memory allocations. The intended behavior is for device drivers to
make
We'd like to revisit the proposal of a GPU cgroup controller for managing
GPU devices but with just a basic set of controls. This series is based on
the prior patch series from Kenny Ho [1]. We take Kenny's base patches
which implement the basic framework for the controller, but we propose an
From: Kenny Ho
With the increased importance of machine learning, data science and
other cloud-based applications, GPUs are already in production use in
data centers today. Existing GPU resource management is very coarse
grain, however, as sysadmins are only able to distribute workload on a
Here we introduce a general purpose drm_cgroup_try_charge and uncharge
pair of functions. This is modelled after the existing RDMA cgroup controller,
and the idea is for these functions to be used for charging/uncharging all
current and future DRM resource controls.
Two new controls are added in
From: Kenny Ho
Since the drm subsystem can be compiled as a module and drm devices can
be added and removed during run time, add several functions to bind the
drm subsystem as well as drm devices with drmcg.
Two pairs of functions:
drmcg_bind/drmcg_unbind - used to bind/unbind the drm subsystem
Single control below is added to DRM cgroup controller in order to track
user execution time for GPU devices. It is up to device drivers to
charge execution time to the cgroup via drm_cgroup_try_charge().
sched.runtime
Read-only value, displays current user execution time for each DRM
The KTD253 backlight might already be on when the driver
is probed: then we don't really know what the current
ratio is and all light intensity settings will be off
relative to what it was at boot.
To fix this, bring up the backlight OFF then move it to
the default backlight from there so we know
Hi,
On Tue, Jan 26, 2021 at 05:55:11AM -0800, menglong8.d...@gmail.com wrote:
> From: Menglong Dong
>
> The 'r' in dsi_vc_send_short() is of type 'unsigned int', so the
> 'r < 0' can't be true.
>
> Fix this by introducing a 'err' insteaded.
>
> Fixes: 1ed6253856cb
> ("drm/omap: dsi: switch
On Tue, Jan 26, 2021 at 8:33 PM Hans de Goede wrote:
> On 1/26/21 6:14 PM, Andy Shevchenko wrote:
> > On Tue, Jan 26, 2021 at 6:55 PM Patrik Jakobsson
> > wrote:
> >> On Tue, Jan 26, 2021 at 4:51 PM Andy Shevchenko
> >> wrote:
> >>> On Tue, Jan 26, 2021 at 5:25 PM Patrik Jakobsson
> >>> wrote:
-randconfig-r034-20210126 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project
925ae8c790c7e354f12ec14a6cac6aa49fc75b29)
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
On Tue, Jan 26, 2021 at 06:56:52PM +0100, Uwe Kleine-König wrote:
> I'm surprised to see that the remove callback introduced in 2952ecf5df33
> ("coresight: etm4x: Refactor probing routine") has an __exit annotation.
In general, remove callbacks should not have an __exit annotation.
__exit _can_
On Thu, Jan 21, 2021 at 6:39 AM Rob Herring wrote:
>
> On Wed, Jan 20, 2021 at 03:23:51PM +0900, Masahiro Yamada wrote:
> > As commit d0e628cd817f ("kbuild: doc: clarify the difference between
> > extra-y and always-y") explained, extra-y should be used for listing
> > the prerequsites of
Hi,
On 1/26/21 6:14 PM, Andy Shevchenko wrote:
> On Tue, Jan 26, 2021 at 6:55 PM Patrik Jakobsson
> wrote:
>> On Tue, Jan 26, 2021 at 4:51 PM Andy Shevchenko
>> wrote:
>>>
>>> On Tue, Jan 26, 2021 at 5:25 PM Patrik Jakobsson
>>> wrote:
On Tue, Jan 26, 2021 at 1:37 PM Andy Shevchenko
adjust_managed_page_count() as called by free_reserved_page() properly
handles pages in a highmem zone, so we can reuse it for
free_highmem_page().
We can now get rid of totalhigh_pages_inc() and simplify
free_reserved_page().
Cc: Andrew Morton
Cc: Thomas Gleixner
Cc: "Peter Zijlstra (Intel)"
Let's simplify and unify free_highmem_page() and free_reserved_page().
Gave it a quick test in i386 QEMU with 4G of RAM - seems to work just fine.
David Hildenbrand (2):
video: fbdev: acornfb: remove free_unused_pages()
mm: simplify free_highmem_page() and free_reserved_page()
This function is never used and it is one of the last remaining user of
__free_reserved_page(). Let's just drop it.
Cc: Andrew Morton
Cc: Thomas Gleixner
Cc: "Peter Zijlstra (Intel)"
Cc: Mike Rapoport
Cc: Oscar Salvador
Cc: Michal Hocko
Cc: Wei Yang
Cc: "Gustavo A. R. Silva"
Cc: Sam
Hello,
On Tue, Jan 26, 2021 at 05:08:40PM +, Suzuki K Poulose wrote:
> On 1/26/21 4:58 PM, Uwe Kleine-König wrote:
> > All amba drivers return 0 in their remove callback. Together with the
> > driver core ignoring the return value anyhow, it doesn't make sense to
> > return a value here.
> >
On Tue, Jan 26, 2021 at 08:40:35PM +0800, Carlis wrote:
> @@ -82,6 +111,29 @@ enum st7789v_command {
> */
> static int init_display(struct fbtft_par *par)
> {
> + int rc;
> + struct device *dev = par->info->device;
> +
> + par->gpio.te = devm_gpiod_get_index_optional(dev, "te", 0,
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #11 from bola...@163.com ---
No HSA_AMD option, it's only for 64bit kernel
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #10 from Alex Deucher (alexdeuc...@gmail.com) ---
does setting CONFIG_HSA_AMD=n fix it?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #9 from bola...@163.com ---
(In reply to Alex Deucher from comment #8)
> (In reply to bolando from comment #7)
> > Yes,maybe Ubuntu kernel applyed some patch? Otherwise AMDGPU driver only
> > worked on X86_64 ? The radeon drivers
All amba drivers return 0 in their remove callback. Together with the
driver core ignoring the return value anyhow, it doesn't make sense to
return a value here.
Change the remove prototype to return void, which makes it explicit that
returning an error value doesn't work as expected. This
On 26-01-21, 17:58, Uwe Kleine-König wrote:
> All amba drivers return 0 in their remove callback. Together with the
> driver core ignoring the return value anyhow, it doesn't make sense to
> return a value here.
>
> Change the remove prototype to return void, which makes it explicit that
>
On Tue, Jan 26, 2021 at 6:55 PM Patrik Jakobsson
wrote:
> On Tue, Jan 26, 2021 at 4:51 PM Andy Shevchenko
> wrote:
> >
> > On Tue, Jan 26, 2021 at 5:25 PM Patrik Jakobsson
> > wrote:
> > > On Tue, Jan 26, 2021 at 1:37 PM Andy Shevchenko
> > > wrote:
> > > >
> > > > Hi guys,
> > > >
> > > >
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #8 from Alex Deucher (alexdeuc...@gmail.com) ---
(In reply to bolando from comment #7)
> Yes,maybe Ubuntu kernel applyed some patch? Otherwise AMDGPU driver only
> worked on X86_64 ? The radeon drivers worked well on 32bit kernel. I
From: Uwe Kleine-König https://lists.freedesktop.org/mailman/listinfo/dri-devel
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_drv.h | 1 +
drivers/gpu/drm/qxl/qxl_kms.c | 22 --
drivers/gpu/drm/qxl/qxl_release.c | 2 ++
3 files changed, 23 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/qxl/qxl_drv.h
Signed-off-by: Gerd Hoffmann
Reviewed-by: Daniel Vetter
Acked-by: Thomas Zimmermann
---
drivers/gpu/drm/qxl/qxl_display.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/qxl/qxl_display.c
b/drivers/gpu/drm/qxl/qxl_display.c
index
qxl_primary_atomic_disable must check whenever the framebuffer bo has a
shadow surface and in case it has check the shadow primary status.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_display.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/qxl/qxl_display.c
Balances the qxl_create_bo(..., pinned=true, ...);
call in qxl_release_bo_alloc().
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_release.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/qxl/qxl_release.c
b/drivers/gpu/drm/qxl/qxl_release.c
index
In case we have a shadow surface on shutdown release
it so it doesn't leak.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_display.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/qxl/qxl_display.c
b/drivers/gpu/drm/qxl/qxl_display.c
index
Almost there. Still getting this on driver unbind:
kobject: '(null)' ((ptrval)): is not initialized, yet kobject_put(=
) is being called
[ ... ]
Call Trace:
ttm_device_fini+0x133/0x1b0 [ttm]
qxl_ttm_fini+0x2f/0x40 [qxl]
qxl_device_fini+0x88/0x120 [qxl]
patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Christian-K-nig/drm-ttm-rework-ttm_tt-page-limit-v3/20210126-140030
base:
On Tue, Jan 26, 2021 at 4:51 PM Andy Shevchenko
wrote:
>
> On Tue, Jan 26, 2021 at 5:25 PM Patrik Jakobsson
> wrote:
> > On Tue, Jan 26, 2021 at 1:37 PM Andy Shevchenko
> > wrote:
> > >
> > > Hi guys,
> > >
> > > This is first part of Intel MID outdated platforms removal. It's
> > > collected
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #7 from bola...@163.com ---
Yes,maybe Ubuntu kernel applyed some patch? Otherwise AMDGPU driver only worked
on X86_64 ? The radeon drivers worked well on 32bit kernel. I have Caicos and
Oland chipset radeon graphic cards,all be drived
On Tue, Jan 26, 2021 at 5:25 PM Patrik Jakobsson
wrote:
> On Tue, Jan 26, 2021 at 1:37 PM Andy Shevchenko
> wrote:
> >
> > Hi guys,
> >
> > This is first part of Intel MID outdated platforms removal. It's collected
> > into
> > immutable branch with a given tag, please pull to yours subsystems.
On Tue, Jan 26, 2021 at 1:37 PM Andy Shevchenko
wrote:
>
> Hi guys,
>
> This is first part of Intel MID outdated platforms removal. It's collected
> into
> immutable branch with a given tag, please pull to yours subsystems.
Hi Andy,
Do you plan on eventually removing X86_INTEL_MID completely?
Quoting Emil Renner Berthing (2021-01-26 15:01:55)
> This converts the driver to use the new tasklet API introduced in
> commit 12cc923f1ccc ("tasklet: Introduce new initialization API")
>
> Signed-off-by: Emil Renner Berthing
>
> ---
> v2: Rebased on drm-intel-next
Ta. Saves me having to do
https://bugzilla.kernel.org/show_bug.cgi?id=211349
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
Hi Hridya,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.11-rc5]
[cannot apply to next-20210125]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use
Not used any more.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_module.c | 50
drivers/gpu/drm/ttm/ttm_module.h | 2 --
2 files changed, 52 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_module.c b/drivers/gpu/drm/ttm/ttm_module.c
index
This is just another feature which is only used by VMWGFX, so move
it into the driver instead.
I've tried to add the accounting sysfs file to the kobject of the drm
minor, but I'm not 100% sure if this works as expected.
v2: fix typo in KFD and avoid 64bit divide
Signed-off-by: Christian König
TTM implements a rather extensive accounting of allocated memory.
There are two reasons for this:
1. It tries to block userspace allocating a huge number of very small
BOs without accounting for the kmalloced memory.
2. Make sure we don't over allocate and run into an OOM situation
during
On Tue, Jan 26, 2021 at 4:23 PM Hans de Goede wrote:
>
> Hi,
>
> On 1/26/21 1:38 PM, Andy Shevchenko wrote:
> > Hi guys,
> >
> > This is first part of Intel MID outdated platforms removal. It's collected
> > into
> > immutable branch with a given tag, please pull to yours subsystems.
> >
> >
+++ Christoph Hellwig [21/01/21 08:49 +0100]:
To uncouple the livepatch code from module loader internals move a
slightly refactored version of klp_find_object_module to module.c
This allows to mark find_module static and removes one of the last
users of module_mutex outside of module.c.
Hi,
On 1/26/21 1:38 PM, Andy Shevchenko wrote:
> Hi guys,
>
> This is first part of Intel MID outdated platforms removal. It's collected
> into
> immutable branch with a given tag, please pull to yours subsystems.
>
> (All changes are tagged by the respective maintainers)
>
> Thanks,
>
>
Hi Maxime,
On Wed, Nov 18, 2020 at 06:48:05PM +0100, Maxime Ripard wrote:
> On Mon, Oct 12, 2020 at 02:00:30AM +0300, Laurent Pinchart wrote:
> > > -static int drm_of_lvds_get_remote_pixels_type(
> > > - const struct device_node *port_node)
> > > +static int
your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Christian-K-nig/drm-ttm-rework-ttm_tt-page-limit-v3/20210126-1
Hi Laurent and Kieran,
Do you forget to attach cubic_lut_property with crtc?
drm_object_attach_property(>base, config->cubic_lut_property,
cubic_lut_size);
在 2020/12/21 9:57, Laurent Pinchart 写道:
From: Kieran Bingham
Extend the existing color management properties to support provision
of
Hi Laurent and Kieran,
Do you forget to attach cubic_lut_property with crtc?
drm_object_attach_property(>base, config->cubic_lut_property,
cubic_lut_size);
在 2020/12/21 9:57, Laurent Pinchart 写道:
From: Kieran Bingham
Extend the existing color management properties to support provision
of a
On Thu, Jan 21, 2021 at 05:35:35PM +0100, Maxime Ripard wrote:
> Many drivers reference the plane->state pointer in order to get the
> current plane state in their atomic_update or atomic_disable hooks,
> which would be the new plane state in the global atomic state since
> _swap_state happened
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #5 from bola...@163.com ---
I have tested with many kernels and firmwares but failed ! To compare with
Ubuntu 20.4 LTS kern log,my kern log lack of "kfd: added device" and "amdgpu
:06:00.0: amdgpu: Topology: Add APU node
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #4 from bola...@163.com ---
Created attachment 294861
--> https://bugzilla.kernel.org/attachment.cgi?id=294861=edit
GCC version
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #3 from bola...@163.com ---
Created attachment 294859
--> https://bugzilla.kernel.org/attachment.cgi?id=294859=edit
Kernel config file
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #2 from bola...@163.com ---
Created attachment 294857
--> https://bugzilla.kernel.org/attachment.cgi?id=294857=edit
Kernel log without kfd fd kfd: added device 1002:15dd and amdgpu: Topology:
Add APU node [0x0:0x0]
--
You may
https://bugzilla.kernel.org/show_bug.cgi?id=211349
--- Comment #1 from bola...@163.com ---
Created attachment 294855
--> https://bugzilla.kernel.org/attachment.cgi?id=294855=edit
Main Error
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=211349
Bug ID: 211349
Summary: IB test failed on sdma0 ! AMDGPU driver for Raven APU
(ryzen 2400G) hangs!
Product: Drivers
Version: 2.5
Kernel Version: 5.10.9
Hardware: i386
patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Christian-K-nig/drm-ttm-rework-ttm_tt-page-limit-v3/20210126-140030
base:
Hi Oliver,
On Mon, Jan 25, 2021 at 7:17 PM Oliver Graute wrote:
> I would prefer mine, because I got a wrong colored penguin on bootup
> with yours :-)
I have originally passed .bpc = 8, but looking at the panel datasheet,
this should be:
.bpc = 6 instead.
In your patch, you pass the timing
Hi Daniel,
just in case you read that when you come back from vacation.
I've tested this quite extensively and apart from the typo in the KFD in
patch #3 it looks pretty solid now.
E.g. no lockdep or KASAN splat when I use the debugfs stuff. Is this
sufficient?
Thanks,
Christian.
Am
Quoting Douglas Anderson (2021-01-15 14:44:18)
> On an Innolux N116BCA panel that I have in front of me, sometimes HPD
> simply doesn't assert no matter how long you wait for it. As per the
> very wise advice of The IT Crowd ("Have you tried turning it off and
> on again?") it appears that power
From: zhangxuezhi
For st7789v ic,add tearing signal detect to avoid screen tearing
Signed-off-by: zhangxuezhi
---
v3:modify author name
---
drivers/staging/fbtft/fb_st7789v.c | 134 -
drivers/staging/fbtft/fbtft.h | 1 +
2 files changed, 134
Quoting Douglas Anderson (2021-01-15 14:44:17)
> If a panel has an hpd_absent_delay specified then we know exactly how
> long the maximum time is before HPD must be asserted. That means we
> can use it as a timeout for polling the HPD pin instead of using an
> arbitrary timeout. This is
On Mon, 2021-01-25 at 15:48 +0200, Laurentiu Palcu wrote:
> Hi Liu Ying,
>
> Just some minor comments below.
>
> On Thu, Jan 21, 2021 at 03:14:22PM +0800, Liu Ying wrote:
> > This patch introduces i.MX8qm/qxp Display Processing Unit(DPU) DRM support.
> >
> > DPU is comprised of two main
On 16/01/21, Fabio Estevam wrote:
> On Sat, Jan 16, 2021 at 9:49 AM Oliver Graute wrote:
>
> > > power-supply = <_touch_3v3> is not correct, as the reg_touch_3v3
> > > does not power the LCD.
> >
> > yes, but how is the LCD correctly powered then?
>
> J4 is powered by VCC_5V and VCC_3V#.
>
> >
Lockdep complains about an AA deadlock when rebooting the device.
WARNING: possible recursive locking detected
5.4.91 #1 Not tainted
reboot/5213 is trying to acquire lock:
ff80d13391b0
On Mon, Jan 11, 2021 at 3:44 PM Yongqiang Niu
wrote:
>
> This patch add component POSTMASK,
>
> Signed-off-by: Yongqiang Niu
> ---
> drivers/gpu/drm/mediatek/Makefile| 1 +
> drivers/gpu/drm/mediatek/mtk_disp_postmask.c | 160
> +++
>
Hi Ville,
On Fri, Jan 22, 2021 at 02:07:22PM +0200, Ville Syrjälä wrote:
> On Thu, Jan 21, 2021 at 05:35:31PM +0100, Maxime Ripard wrote:
> > Many drivers reference the plane->state pointer in order to get the
> > current plane state in their atomic_check hook, which would be the old
> > plane
On Sat, Jan 23, 2021 at 08:14:03PM +0900, Ryutaroh Matsumoto wrote:
> From: Lucas Nussbaum
> Subject: Re: [PATCH 2/2] drm/vc4: Correct POS1_SCL for hvs5
> Date: Sat, 23 Jan 2021 09:05:48 +0100
>
> > On 21/01/21 at 11:57 +0100, Maxime Ripard wrote:
> >> From: Dom Cobley
> >>
> >> Fixes failure
Add MIPI rx DPI input support
Reported-by: kernel test robot
Signed-off-by: Xin Ji
---
drivers/gpu/drm/bridge/analogix/anx7625.c | 326 --
drivers/gpu/drm/bridge/analogix/anx7625.h | 20 +-
2 files changed, 285 insertions(+), 61 deletions(-)
diff --git
This patch adds bindings for i.MX8qxp/qm Display Prefetch Resolve Gasket.
Reviewed-by: Rob Herring
Signed-off-by: Liu Ying
---
v6->v7:
* No change.
v5->v6:
* No change.
v4->v5:
* No change.
v3->v4:
* Improve compatible property by using enum instead of oneOf+const. (Rob)
* Add Rob's R-b tag.
This patch adds bindings for i.MX8qxp/qm Display Processing Unit.
Reviewed-by: Rob Herring
Signed-off-by: Liu Ying
---
v6->v7:
* Add Rob's R-b tag back.
v5->v6:
* Use graph schema. So, drop Rob's R-b tag as review is needed.
v4->v5:
* No change.
v3->v4:
* Improve compatible property by using
Hi Yannick
On 1/15/21 3:32 PM, Yannick Fertre wrote:
Enable CEC support for STMicroelectronics as loadable module.
Signed-off-by: Yannick Fertre
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
28.12.2020 18:49, Dmitry Osipenko пишет:
> Display controller (DC) performs isochronous memory transfers, and thus,
> has a requirement for a minimum memory bandwidth that shall be fulfilled,
> otherwise framebuffer data can't be fetched fast enough and this results
> in a DC's data-FIFO underflow
Quoting Douglas Anderson (2021-01-15 14:44:20)
> This panel is quite similar to the similarly named N116BGE panel (the
> nominal timings are, in fact identical). However, let's add a new
> entry because the full range of clocks listed for N116BGE aren't
> supported for N116BCA-EA1, at least
Hi Ville,
On Fri, Jan 22, 2021 at 02:15:07PM +0200, Ville Syrjälä wrote:
> On Thu, Jan 21, 2021 at 05:35:33PM +0100, Maxime Ripard wrote:
> > Some drivers are storing the plane->state pointer in atomic_update and
> > atomic_disable in a variable simply called state, while the state passed
> > as
Lockdep complains about an AA deadlock when rebooting the device.
WARNING: possible recursive locking detected
5.4.91 #1 Not tainted
reboot/5213 is trying to acquire lock:
ff80d13391b0
Hi,
On Mon, 2021-01-11 at 15:22 +0100, Maxime Ripard wrote:
> Hi,
>
> Here's a series introducing the CEC support for the BCM2711 found on the
> RaspberryPi4.
>
> The BCM2711 HDMI controller uses a similar layout for the CEC registers, the
> main difference being that the interrupt handling
This patch helps complete Use DRM_MODESET_LOCK_ALL* helpers instead of
boilerplate todo in Documentation/gpu/todo.rst
Signed-off-by: Joseph Schulte
---
drivers/gpu/drm/drm_client_modeset.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
Hi,
This is the v7 series to introduce i.MX8qm/qxp Display Processing Unit(DPU)
DRM support.
DPU is comprised of a blit engine for 2D graphics, a display controller
and a command sequencer. Outside of DPU, optional prefetch engines can
fetch data from memory prior to some DPU fetchunits of
Hi all, this patch series implement MIPI rx DPI feature. Please help to review.
This is the v3 version, any mistakes, please let me know,
I'll fix it in the next series.
Change history:
v3: Fix Rob Herring, Dan Carpenter, Nicolas comments
- Split the patch, fix not correct return data
- Fix
Add myself as the maintainer of the i.MX8qxp DPU DRM driver.
Signed-off-by: Liu Ying
---
v6->v7:
* No change.
v5->v6:
* No change.
v4->v5:
* No change.
v3->v4:
* No change.
v2->v3:
* No change.
v1->v2:
* No change.
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git
Add 'bus-type' and 'data-lanes' define for port0, add HDCP support
flag and DP tx lane0 and lane1 swing register array define.
Signed-off-by: Xin Ji
---
.../bindings/display/bridge/analogix,anx7625.yaml | 57 --
1 file changed, 54 insertions(+), 3 deletions(-)
diff --git
fixed the below warning:
./drivers/gpu/drm/msm/msm_gem.c:991:3-9: WARNING: NULL check before some
freeing functions is not needed.
Signed-off-by: Tian Tao
---
drivers/gpu/drm/msm/msm_gem.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/msm/msm_gem.c
1 - 100 of 107 matches
Mail list logo
