https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #26 from rtmasura+ker...@hotmail.com ---
and just got another crash, only watching a video in chrome. Guess the chrome
bit at the end might be more important than I thought
I *think* I've turned off the glx for xfwm.. we'll see. My
On Sat, Jun 27, 2020 at 12:51:50AM -0400, B K Karthik wrote:
> fbtft-bus.c:
>
> fixing ERROR: space prohibited before that close parenthesis ')' by removing
> that space and ',' in line 65 and 67.
>
> Signed-off-by: B K Karthik
> ---
> drivers/staging/fbtft/fbtft-bus.c | 4 ++--
> 1 file
On Sat, 2020-06-27 at 00:51 -0400, B K Karthik wrote:
> fbtft-bus.c:
>
> fixing ERROR: space prohibited before that close parenthesis ')' by removing
> that space and ',' in line 65 and 67.
[]
> diff --git a/drivers/staging/fbtft/fbtft-bus.c
> b/drivers/staging/fbtft/fbtft-bus.c
> index
On Sat, Jun 27, 2020 at 12:50:04AM -0400, B K Karthik wrote:
> fbtft-bus.c:
>
> fixing ERROR: space prohibited before that close parenthesis ')' by removing
> that space and ',' in line 65 and 67.
>
> Signed-off-by: B K Karthik
> ---
> drivers/staging/fbtft/fbtft-bus.c | 4 ++--
> 1 file
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #25 from rtmasura+ker...@hotmail.com ---
Same kernel (5.7.4) and I'll try to reproduce it, and if it happens I'll turn
off the screen tear and try to reproduce again
Let me know if that's anything I can provide you
--
You are
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #24 from rtmasura+ker...@hotmail.com ---
I've been up and stable on XFCE4 since that last message, but just crashed
today with a bit of a different error. This happened after I turned on a screen
tear fix:
xfconf-query -c xfwm4 -p
Hi Linus,
I love your patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-exynos/exynos-drm-next
tegra-drm/drm/tegra/for-next drm-tip/drm-tip linus/master v5.8-rc2
next-20200626]
[cannot apply to drm/drm-next]
[If your patch
Hi, Hsin-Yi:
Hsin-Yi Wang 於 2020年6月22日 週一 下午11:57寫道：
>
> Disable the plane if it's not visible. Otherwise mtk_ovl_layer_config()
> would proceed with invalid plane and we may see vblank timeout.
>
Applied to mediatek-drm-next [1], thanks.
[1]
From: Bhanuprakash Modem
v3:
* Rebase (Manasi)
v2:
* Rebase (Manasi)
As both VRR min and max are already part of drm_display_info,
drm can expose this VRR range for each connector.
Hence this logic should move to core DRM.
This reverts commit 727962f030c23422a01e8b22d0f463815fb15ec4.
The OMAP DRM driver includes into the two
hdmi4.c and hdmi5.c files but does not use any symbols from
these files. Drop the includes.
Cc: Tomi Valkeinen
Cc: Tony Lindgren
Cc: Jyri Sarha
Signed-off-by: Linus Walleij
---
drivers/gpu/drm/omapdrm/dss/hdmi4.c | 1 -
This file includes but does not use any
symbols from it, drop the include.
Cc: Patrik Jakobsson
Signed-off-by: Linus Walleij
---
drivers/gpu/drm/gma500/psb_intel_drv.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/gma500/psb_intel_drv.h
Hi Dave, Daniel,
First pull for 5.9. Big feature here is initial support for a new GPU,
sienna cichlid.
The following changes since commit 9ca1f474cea0edc14a1d7ec933e5472c0ff115d3:
Merge tag 'amd-drm-next-5.8-2020-05-27' of
git://people.freedesktop.org/~agd5f/linux into drm-next (2020-05-28
On Fri, Jun 26, 2020 at 08:25:18AM -0700, Rob Clark wrote:
> On Fri, Jun 26, 2020 at 6:46 AM Daniel Vetter wrote:
> >
> > On Thu, Jun 25, 2020 at 09:24:38AM -0700, Rob Clark wrote:
> > > On Thu, Jun 25, 2020 at 8:55 AM Daniel Vetter
> > > wrote:
> > > >
> > > > On Thu, Jun 25, 2020 at 4:17 PM
On Wed, Jun 24, 2020 at 07:03:10PM -0400, Lyude Paul wrote:
> Add some kind of vblank workers. The interface is similar to regular
> delayed works, and is mostly based off kthread_work. It allows for
> scheduling delayed works that execute once a particular vblank sequence
> has passed. It also
On Wed, Jun 24, 2020 at 07:03:09PM -0400, Lyude Paul wrote:
> This got me confused for a bit while looking over this code: I had been
> planning on adding some blocking function calls into this function, but
> seeing the irqsave/irqrestore variants of spin_(un)lock() didn't make it
> very clear
The SKY81452 backlight driver just obtains a GPIO (named "gpios"
in the device tree) drives it high and leaves it high until the
driver is removed.
Switch to use GPIO descriptors for this, simple and
straight-forward.
Cc: Gyungoh Yoo
Signed-off-by: Linus Walleij
---
The only way the platform data for the SKY81452 ever gets populated
is through the device tree.
The MFD device is bothered with this for no reason at all. Just
allocate the platform data in the driver and be happy.
Cc: Gyungoh Yoo
Signed-off-by: Linus Walleij
---
drivers/mfd/sky81452.c
Add support for using per-instance pagetables if all the dependencies are
available.
Signed-off-by: Jordan Crouse
---
drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 43 +++
drivers/gpu/drm/msm/msm_ringbuffer.h | 1 +
2 files changed, 44 insertions(+)
diff --git
Add support for allocating an address space instance. Targets that support
per-instance pagetables should implement their own function to allocate a
new instance. The default will return the existing generic address space.
Signed-off-by: Jordan Crouse
---
drivers/gpu/drm/msm/msm_drv.c | 15
This is a new refresh of support for auxiliary domains for arm-smmu-v2
and per-instance pagetables for drm/msm. The big change here from past
efforts is that outside of creating a single aux-domain to enable TTBR0
all of the per-instance pagetables are created and managed exclusively
in drm/msm
Add support to create a io-pgtable for use by targets that support
per-instance pagetables. In order to support per-instance pagetables the
GPU SMMU device needs to have the qcom,adreno-smmu compatible string and
split pagetables and auxiliary domains need to be supported and enabled.
Use the aperture settings from the IOMMU domain to set up the virtual
address range for the GPU. This allows us to transparently deal with
IOMMU side features (like split pagetables).
Signed-off-by: Jordan Crouse
---
drivers/gpu/drm/msm/adreno/adreno_gpu.c | 13 +++--
Another iteration of the split-pagetable support for arm-smmu and the Adreno GPU
SMMU. After email discussions [1] we opted to make a arm-smmu implementation for
specifically for the Adreno GPU and use that to enable split pagetable support
and later other implementation specific bits that we
The pull request you sent on Fri, 26 Jun 2020 14:26:34 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2020-06-26
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6a6c9b220a7fb7c8285ad1739ac3c909584feb43
Thank you!
--
Deet-doot-dot, I am a bot.
Hi Philipp,
On 6/26/20 2:38 AM, Philipp Zabel wrote:
Hi Steve,
On Thu, 2020-06-25 at 11:13 -0700, Steve Longerbeam wrote:
Use a bit-mask of EOF irqs to determine when all required idmac
channel EOFs have been received for a tile conversion, and only do
tile completion processing after all
Am 26.06.20 um 19:39 schrieb Ruhl, Michael J:
-Original Message-
From: dri-devel On Behalf Of
Christian König
Sent: Wednesday, June 24, 2020 9:36 AM
To: dri-devel@lists.freedesktop.org
Subject: [PATCH 1/2] drm/ttm: cleanup
ttm_mem_type_manager_func.get_node interface
Instead of
>-Original Message-
>From: dri-devel On Behalf Of
>Christian König
>Sent: Wednesday, June 24, 2020 9:36 AM
>To: dri-devel@lists.freedesktop.org
>Subject: [PATCH 2/2] drm/ttm: make TT creation purely optional
>
>We only need the page array when the BO is about to be accessed.
>
>So not
>-Original Message-
>From: dri-devel On Behalf Of
>Christian König
>Sent: Wednesday, June 24, 2020 9:36 AM
>To: dri-devel@lists.freedesktop.org
>Subject: [PATCH 1/2] drm/ttm: cleanup
>ttm_mem_type_manager_func.get_node interface
>
>Instead of signaling failure by setting the node pointer
On Tue, 23 Jun 2020 15:31:33 +0200
Mauro Carvalho Chehab wrote:
> The main goal of this series is to finish the ReST conversion. After this
> series, we have just those files still in plain old format:
>
> - Documentation/RCU/RTFP.txt
> - Documentation/atomic_bitops.txt
> -
In cases such as DRM_FORMAT_MOD_SAMSUNG_16_16_TILE, the modifier
describes a generic pixel re-ordering which can be applicable to
multiple vendors.
Define an alias: DRM_FORMAT_MOD_GENERIC_16_16_TILE, which can be
used to describe this layout in a vendor-neutral way, and add a
comment about the
On Fri, Jun 26, 2020 at 06:15:36PM +0200, Daniel Vetter wrote:
> On Fri, Jun 26, 2020 at 5:21 PM Brian Starkey wrote:
> >
> > On Fri, Jun 26, 2020 at 05:16:53PM +0200, Daniel Vetter wrote:
> > > On Fri, Jun 26, 2020 at 4:16 PM Brian Starkey
> > > wrote:
> > > >
> > > > Hi Daniel,
> > > >
> > >
Hi Andrzej
On Fri, Jun 26, 2020 at 12:01:00PM +0200, Andrzej Hajda wrote:
> During probe every time driver gets resource it should usually check for
> error printk some message if it is not -EPROBE_DEFER and return the error.
> This pattern is simple but requires adding few lines after any
On Fri, Jun 26, 2020 at 5:21 PM Brian Starkey wrote:
>
> On Fri, Jun 26, 2020 at 05:16:53PM +0200, Daniel Vetter wrote:
> > On Fri, Jun 26, 2020 at 4:16 PM Brian Starkey wrote:
> > >
> > > Hi Daniel,
> > >
> > > On Fri, Jun 26, 2020 at 04:07:43PM +0200, Daniel Vetter wrote:
> > > > On Fri, Jun
On Fri, Jun 26, 2020 at 12:01 PM Andrzej Hajda wrote:
>
> /sys/kernel/debug/devices_deferred property contains list of deferred devices.
> This list does not contain reason why the driver deferred probe, the patch
> improves it.
> The natural place to set the reason is probe_err function
On Fri, Jun 26, 2020 at 12:01 PM Andrzej Hajda wrote:
>
> During probe every time driver gets resource it should usually check for
> error printk some message if it is not -EPROBE_DEFER and return the error.
> This pattern is simple but requires adding few lines after any resource
> acquisition
(retry with $subject)
Hi Dave,
A few fixes, mostly fallout from the address space refactor and dpu
color processing.
The following changes since commit 1cb2c4a2c89b2004a36399860c85a1af9b3fcba7:
Revert "drm/msm/dpu: add support for clk and bw scaling for display"
(2020-06-01 20:56:18 -0700)
Hi Christian,
On Fri, 26 Jun 2020, 18:10 Daniel Vetter, wrote:
> On Fri, Jun 26, 2020 at 9:03 AM Christian König
> wrote:
> >
> > Am 26.06.20 um 06:43 schrieb Sumit Semwal:
> > > On Fri, 26 Jun 2020 at 01:24, Daniel Vetter wrote:
> > >> Ignoring everything else ...
> > >>
> > >> On Thu, Jun
On Fri, 26 Jun 2020, Daniel Thompson wrote:
> On Thu, Jun 25, 2020 at 11:33:34AM +0100, Lee Jones wrote:
> > On Thu, 25 Jun 2020, Daniel Thompson wrote:
> >
> > > On Wed, Jun 24, 2020 at 03:57:16PM +0100, Lee Jones wrote:
> > > > Kerneldoc syntax is used, but not complete. Descriptions
Hi Dave,
A few fixes, mostly fallout from the address space refactor and dpu
color processing.
The following changes since commit 1cb2c4a2c89b2004a36399860c85a1af9b3fcba7:
Revert "drm/msm/dpu: add support for clk and bw scaling for display"
(2020-06-01 20:56:18 -0700)
are available in the
On Fri, Jun 26, 2020 at 6:46 AM Daniel Vetter wrote:
>
> On Thu, Jun 25, 2020 at 09:24:38AM -0700, Rob Clark wrote:
> > On Thu, Jun 25, 2020 at 8:55 AM Daniel Vetter
> > wrote:
> > >
> > > On Thu, Jun 25, 2020 at 4:17 PM Rob Clark wrote:
> > > >
> > > > On Thu, Jun 25, 2020 at 5:35 AM Daniel
On Fri, Jun 26, 2020 at 05:16:53PM +0200, Daniel Vetter wrote:
> On Fri, Jun 26, 2020 at 4:16 PM Brian Starkey wrote:
> >
> > Hi Daniel,
> >
> > On Fri, Jun 26, 2020 at 04:07:43PM +0200, Daniel Vetter wrote:
> > > On Fri, Jun 26, 2020 at 3:52 PM Brian Starkey
> > > wrote:
> > > >
> > > > In
On Fri, Jun 26, 2020 at 4:16 PM Brian Starkey wrote:
>
> Hi Daniel,
>
> On Fri, Jun 26, 2020 at 04:07:43PM +0200, Daniel Vetter wrote:
> > On Fri, Jun 26, 2020 at 3:52 PM Brian Starkey wrote:
> > >
> > > In cases such as DRM_FORMAT_MOD_SAMSUNG_16_16_TILE, the modifier
> > > describes a generic
On 26/06/2020 17:22, Chris Wilson wrote:
Quoting Lionel Landwerlin (2020-06-26 13:21:00)
Trying to explain a bit how this thing works. In my opinion diagrams
are a bit easier to understand than words.
Signed-off-by: Lionel Landwerlin
---
drivers/dma-buf/dma-fence-chain.c | 37
Quoting Lionel Landwerlin (2020-06-26 13:21:00)
> Trying to explain a bit how this thing works. In my opinion diagrams
> are a bit easier to understand than words.
>
> Signed-off-by: Lionel Landwerlin
> ---
> drivers/dma-buf/dma-fence-chain.c | 37 +++
> 1 file
On 2020-06-17 14:07, Huang Jiachai wrote:
> Hi Jonas Karlman,
>
> Is there an another yuv 10bit format with 4:4:4 sub-simpling but
> has no padding?
>
> Maybe we can call it DRM_FORMAT_NV30:
>
> { .format = DRM_FORMAT_NV30, .depth = 0,
>.num_planes = 2, .char_per_block = {
Hi Daniel,
On Fri, Jun 26, 2020 at 04:07:43PM +0200, Daniel Vetter wrote:
> On Fri, Jun 26, 2020 at 3:52 PM Brian Starkey wrote:
> >
> > In cases such as DRM_FORMAT_MOD_SAMSUNG_16_16_TILE, the modifier
> > describes a generic pixel re-ordering which can be applicable to
> > multiple vendors.
> >
On Fri, Jun 26, 2020 at 3:52 PM Brian Starkey wrote:
>
> In cases such as DRM_FORMAT_MOD_SAMSUNG_16_16_TILE, the modifier
> describes a generic pixel re-ordering which can be applicable to
> multiple vendors.
>
> Define an alias: DRM_FORMAT_MOD_GENERIC_16_16_TILE, which can be
> used to describe
On Fri, Jun 26, 2020 at 03:40:20PM +0200, Daniel Vetter wrote:
> Adding Lyude, she's been revamping all the lifetime refcouting in the
> dp code last few kernel releases. At a glance I don't even have an
> idea what's going wrong here ...
Already fixed by Imre I believe.
7d11507605a7
In cases such as DRM_FORMAT_MOD_SAMSUNG_16_16_TILE, the modifier
describes a generic pixel re-ordering which can be applicable to
multiple vendors.
Define an alias: DRM_FORMAT_MOD_GENERIC_16_16_TILE, which can be
used to describe this layout in a vendor-neutral way, and add a
comment about the
On 26/06/2020 15:43, Daniel Vetter wrote:
On Fri, Jun 26, 2020 at 2:21 PM Lionel Landwerlin
wrote:
Trying to explain a bit how this thing works. In my opinion diagrams
are a bit easier to understand than words.
kerneldoc supports in-line DOT graphs, see e.g.
On Thu, Jun 25, 2020 at 09:24:38AM -0700, Rob Clark wrote:
> On Thu, Jun 25, 2020 at 8:55 AM Daniel Vetter wrote:
> >
> > On Thu, Jun 25, 2020 at 4:17 PM Rob Clark wrote:
> > >
> > > On Thu, Jun 25, 2020 at 5:35 AM Daniel Vetter
> > > wrote:
> > > >
> > > > On Thu, Jun 25, 2020 at 1:58 PM
Adding Lyude, she's been revamping all the lifetime refcouting in the
dp code last few kernel releases. At a glance I don't even have an
idea what's going wrong here ...
-Daniel
On Thu, Jun 25, 2020 at 12:22 PM Luis Henriques wrote:
>
> Hi!
>
> I've been seeing this warning occasionally, not
On Fri, Jun 26, 2020 at 01:40:40PM +0200, Thierry Reding wrote:
> On Fri, Jun 26, 2020 at 01:06:58PM +0200, Karol Herbst wrote:
> > On Tue, Jun 23, 2020 at 3:03 PM Mikko Perttunen wrote:
> > >
> > > # Host1x/TegraDRM UAPI proposal
> > >
> > > This is a proposal for a stable UAPI for Host1x and
On Fri, Jun 26, 2020 at 10:25:45AM +0100, Daniel Stone wrote:
> Hi,
>
> On Fri, 26 Jun 2020 at 10:00, Pekka Paalanen wrote:
> > On Thu, 25 Jun 2020 12:44:36 +0200 Daniel Vetter wrote:
> > > Maybe an aside, but the guideline is for autoconfiguration:
> > > - Light up everything that has
https://bugzilla.kernel.org/show_bug.cgi?id=208333
Bug ID: 208333
Summary: No desktop on 5.8 rc1 rc2 with Gtx 760 driver nouveau
Product: Drivers
Version: 2.5
Kernel Version: 5.8 rc2
Hardware: All
OS: Linux
On Fri, Jun 26, 2020 at 3:04 PM Christian König
wrote:
>
> Am 25.06.20 um 18:02 schrieb Christian König:
> > Am 25.06.20 um 17:52 schrieb Christian König:
> >> Am 25.06.20 um 17:44 schrieb Daniel Vetter:
> >>> On Thu, Jun 25, 2020 at 11:50 AM Christian König
> >>> wrote:
> I've pushed
On Fri, Jun 26, 2020 at 3:12 PM Daniel Vetter wrote:
>
> On Fri, Jun 26, 2020 at 3:04 PM Christian König
> wrote:
> >
> > Am 25.06.20 um 18:02 schrieb Christian König:
> > > Am 25.06.20 um 17:52 schrieb Christian König:
> > >> Am 25.06.20 um 17:44 schrieb Daniel Vetter:
> > >>> On Thu, Jun 25,
Am 25.06.20 um 18:02 schrieb Christian König:
Am 25.06.20 um 17:52 schrieb Christian König:
Am 25.06.20 um 17:44 schrieb Daniel Vetter:
On Thu, Jun 25, 2020 at 11:50 AM Christian König
wrote:
I've pushed patches #1, #2 and #5-#8 of this series to drm-misc-next.
I think you left an unresolved
On Fri, 26 Jun 2020 12:05:16 +
Simon Ser wrote:
> On Friday, June 26, 2020 11:15 AM, Pekka Paalanen wrote:
>
> > I have no opinion really if adding yet another set of the same
> > definitions is good or not. We do need the UAPI doc, but that does not
> > necessarily mean we also need
On Fri, Jun 26, 2020 at 2:21 PM Lionel Landwerlin
wrote:
>
> Trying to explain a bit how this thing works. In my opinion diagrams
> are a bit easier to understand than words.
kerneldoc supports in-line DOT graphs, see e.g.
https://dri.freedesktop.org/docs/drm/gpu/drm-kms.html#overview
If that
On Fri, Jun 26, 2020 at 9:03 AM Christian König
wrote:
>
> Am 26.06.20 um 06:43 schrieb Sumit Semwal:
> > On Fri, 26 Jun 2020 at 01:24, Daniel Vetter wrote:
> >> Ignoring everything else ...
> >>
> >> On Thu, Jun 25, 2020 at 9:28 PM Jani Nikula
> >> wrote:
> >>> As a side note, there seem to
Trying to explain a bit how this thing works. In my opinion diagrams
are a bit easier to understand than words.
Signed-off-by: Lionel Landwerlin
---
drivers/dma-buf/dma-fence-chain.c | 37 +++
1 file changed, 37 insertions(+)
diff --git
On Friday, June 26, 2020 11:15 AM, Pekka Paalanen wrote:
> I have no opinion really if adding yet another set of the same
> definitions is good or not. We do need the UAPI doc, but that does not
> necessarily mean we also need definition code in UAPI headers.
>
> I give this one a shrug.
But
Hi,
On 19/06/2020 00:09, Doug Anderson wrote:
> Hi,
>
> On Tue, Jun 9, 2020 at 5:05 AM Harigovindan P wrote:
>>
>> ti-sn65dsi86 bridge is enumerated as a runtime device. When
>> suspend is triggered, PM core adds a refcount on all the
>> devices and calls device suspend, since usage count is
>>
On Fri, Jun 26, 2020 at 01:06:58PM +0200, Karol Herbst wrote:
> On Tue, Jun 23, 2020 at 3:03 PM Mikko Perttunen wrote:
> >
> > # Host1x/TegraDRM UAPI proposal
> >
> > This is a proposal for a stable UAPI for Host1x and TegraDRM, to replace
> > the current TegraDRM UAPI that is behind `STAGING`
This patch adds a commandline toggle for the Panel Self-Refresh feature
to the analogix_dp bridge driver, much like the one in i915.
This is required to work around a hardware fault in some Pinebook Pro units
from the May 2020 batch whose display panels seem to behave sporadically
when PSR is
Add a toggle to enable/disable PSR from the kernel commandline.
This is useful in situations where PSR is supported by the hardware
but is not desired by the user. One such use case is working around
hardware errata.
Signed-off-by: Shawn Anastasio
---
On Fri, Jun 26, 2020 at 1:13 PM Mikko Perttunen wrote:
>
> On 6/26/20 2:06 PM, Karol Herbst wrote:
> > On Tue, Jun 23, 2020 at 3:03 PM Mikko Perttunen wrote:
> >>
> >> # Host1x/TegraDRM UAPI proposal
> >>
> >> This is a proposal for a stable UAPI for Host1x and TegraDRM, to replace
> >> the
On 6/26/20 2:06 PM, Karol Herbst wrote:
On Tue, Jun 23, 2020 at 3:03 PM Mikko Perttunen wrote:
# Host1x/TegraDRM UAPI proposal
This is a proposal for a stable UAPI for Host1x and TegraDRM, to replace
the current TegraDRM UAPI that is behind `STAGING` and quite obsolete in
many ways.
I
On Fri, Jun 26, 2020 at 12:25:00PM +0200, Linus Walleij wrote:
> This driver has no in-kernel users. The device can only be populated
> by board files since it does not support device tree nor ACPI,
> and nothing in the kernel creates a device named "ot200-backlight".
>
> This driver has been in
On Tue, Jun 23, 2020 at 3:03 PM Mikko Perttunen wrote:
>
> # Host1x/TegraDRM UAPI proposal
>
> This is a proposal for a stable UAPI for Host1x and TegraDRM, to replace
> the current TegraDRM UAPI that is behind `STAGING` and quite obsolete in
> many ways.
>
> I haven't written any implementation
drm-misc-next-2020-06-26:
drm-misc-next for v5.9:
Cross-subsystem Changes:
- Improve dma-buf docs.
Core Changes:
- Add NV15, Q410, Q401 yuv formats.
- Add uncompressed AFBC modifier.
- Add DP helepr for reading Ignore MSA from DPCD.
- Add missing panel type for some panels
- Optimize drm/mm hole
These if statements are supposed to be true if we ended the
list_for_each_entry() loops without hitting a break statement but they
don't work.
In the first loop, we increment "i" after the "if (i == unit)" condition
so we don't necessarily know that "i" is not equal to unit at the end of
the
The "entry" pointer is an offset from the list head and it doesn't
point to a valid vmw_legacy_display_unit struct. Presumably the
intent was to point to the last entry.
Also the "i++" wasn't used so I have removed that as well.
Fixes: d7e1958dbe4a ("drm/vmwgfx: Support older hardware.")
On Fri, 26 Jun 2020 13:34:01 +0300
Dan Carpenter wrote:
> The problem is that the iterator is already at the list head so the
> list_for_each_entry_from() loop is a no-op and we don't call the
> the iter->funcs->post_disable() functions. This should be
> list_for_each_entry() instead.
>
>
The problem is that the iterator is already at the list head so the
list_for_each_entry_from() loop is a no-op and we don't call the
the iter->funcs->post_disable() functions. This should be
list_for_each_entry() instead.
Fixes: 033bfe7538a1 ("drm/vc4: dsi: Fix bridge chain handling")
This driver has no in-kernel users. The device can only be populated
by board files since it does not support device tree nor ACPI,
and nothing in the kernel creates a device named "ot200-backlight".
This driver has been in the kernel since 2012. If it is used by
out-of-tree code that code should
Hi All,
Thanks for multiple comments.
Changes since v5:
- removed patch adding macro, dev_err_probe(dev, PTR_ERR(ptr), ...) should be
used instead,
- added dev_dbg logging in case of -EPROBE_DEFER,
- renamed functions and vars according to comments,
- extended docs,
- cosmetics.
Original
In case of error during resource acquisition driver should print error
message only in case it is not deferred probe, using dev_err_probe helper
solves the issue. Moreover it records defer probe reason for debugging.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/bridge/sil-sii8620.c | 21
/sys/kernel/debug/devices_deferred property contains list of deferred devices.
This list does not contain reason why the driver deferred probe, the patch
improves it.
The natural place to set the reason is probe_err function introduced recently,
ie. if probe_err will be called with -EPROBE_DEFER
Using dev_err_probe code has following advantages:
- shorter code,
- recorded defer probe reason for debugging,
- uniform error code logging.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/bridge/lvds-codec.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git
During probe every time driver gets resource it should usually check for
error printk some message if it is not -EPROBE_DEFER and return the error.
This pattern is simple but requires adding few lines after any resource
acquisition code, as a result it is often omitted or implemented only
On Thu, Jun 25, 2020 at 11:33:34AM +0100, Lee Jones wrote:
> On Thu, 25 Jun 2020, Daniel Thompson wrote:
>
> > On Wed, Jun 24, 2020 at 03:57:16PM +0100, Lee Jones wrote:
> > > Kerneldoc syntax is used, but not complete. Descriptions required.
> > >
> > > Prevents warnings like:
> > >
> > >
On Fri, Jun 26, 2020 at 01:25:12AM +0200, Linus Walleij wrote:
> This driver includes but does not use any
> symbols from that file, drop the include.
>
> Signed-off-by: Linus Walleij
Reviewed-by: Daniel Thompson
> ---
> drivers/video/backlight/lms501kf03.c | 1 -
> 1 file changed, 1
Hi Steve,
On Thu, 2020-06-25 at 11:13 -0700, Steve Longerbeam wrote:
> Use a bit-mask of EOF irqs to determine when all required idmac
> channel EOFs have been received for a tile conversion, and only do
> tile completion processing after all EOFs have been received. Otherwise
> it was found that
On Wed, 2020-06-17 at 15:40 -0700, Steve Longerbeam wrote:
> Combine the rotate_irq() and norotate_irq() handlers into a single
> eof_irq() handler.
>
> Signed-off-by: Steve Longerbeam
Reviewed-by: Philipp Zabel
regards
Philipp
> ---
> drivers/gpu/ipu-v3/ipu-image-convert.c | 58
Hi,
On Fri, 26 Jun 2020 at 10:00, Pekka Paalanen wrote:
> On Thu, 25 Jun 2020 12:44:36 +0200 Daniel Vetter wrote:
> > Maybe an aside, but the guideline is for autoconfiguration:
> > - Light up everything that has connector status connected.
> > - If nothing has that status, try to light up the
On Wed, 2020-06-17 at 15:40 -0700, Steve Longerbeam wrote:
> RGB32 and BGR32 formats were inadvertently removed from the switch
> statement in ipu_pixelformat_to_colorspace(). Restore them.
>
> Fixes: a59957172b0c ("gpu: ipu-v3: enable remaining 32-bit RGB V4L2 pixel
> formats")
> Signed-off-by:
On Fri, 26 Jun 2020 07:55:12 +
Simon Ser wrote:
> Right now user-space doesn't have access to connector status definitions.
> This means user-space needs to maintain a separate enum for these, and
> makes it difficult to document the uapi.
>
> Introduce defines in drm_mode.h, and copy over
tree: git://people.freedesktop.org/~agd5f/linux.git drm-next
head: 7aebbbd59a2ee62e3b75d7e8e3617171c3c6a208
commit: 956a0ff27b40732740abac49cd773574a4a81793 [462/499] drm/amd/display: add
mechanism to skip DCN init
config: i386-randconfig-a014-20200624 (attached as .config)
compiler: gcc-4.9
On 6/26/20 2:24 AM, Dmitry Osipenko wrote:
25.06.2020 12:16, Mikko Perttunen пишет:
On 6/25/20 2:11 AM, Dmitry Osipenko wrote:
23.06.2020 15:09, Mikko Perttunen пишет:
/* Command is an opcode gather from a GEM handle */
#define DRM_TEGRA_SUBMIT_COMMAND_GATHER 0
/* Command is an
On 6/26/20 1:50 AM, Dmitry Osipenko wrote:
25.06.2020 12:27, Mikko Perttunen пишет:
On 6/25/20 1:33 AM, Dmitry Osipenko wrote:
23.06.2020 15:09, Mikko Perttunen пишет:
struct drm_tegra_submit_relocation {
/* [in] Index of GATHER or GATHER_UPTR command in commands. */
__u32
On Thu, 25 Jun 2020 12:44:36 +0200
Daniel Vetter wrote:
> On Thu, Jun 25, 2020 at 12:32 PM Pekka Paalanen wrote:
> >
> > On Thu, 25 Jun 2020 09:57:44 +0200
> > Daniel Vetter wrote:
> >
> > > On Thu, Jun 25, 2020 at 9:56 AM Daniel Vetter wrote:
> > > >
> > > > On Wed, Jun 24, 2020 at
Right now user-space doesn't have access to connector status definitions.
This means user-space needs to maintain a separate enum for these, and
makes it difficult to document the uapi.
Introduce defines in drm_mode.h, and copy over the docs. Keep using the
drm_connector_status enum in drivers,
Calling sleep out and display on is a controller specific part
of the initialization process. Move it out of the panel specific
initialization function to the enable callback.
Signed-off-by: Ondrej Jirman
---
drivers/gpu/drm/panel/panel-sitronix-st7703.c | 33 ++-
1 file
It's better than having it spread around the driver.
Signed-off-by: Ondrej Jirman
---
drivers/gpu/drm/panel/panel-sitronix-st7703.c | 50 +--
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/drivers/gpu/drm/panel/panel-sitronix-st7703.c
23.06.2020 15:09, Mikko Perttunen пишет:
> ### DRM_TEGRA_CHANNEL_MAP
>
> Make memory accessible by the engine while executing work on the channel.
>
> ```
> #define DRM_TEGRA_CHANNEL_MAP_READWRITE (1<<0)
>
> struct drm_tegra_channel_map {
> /*
> * [in] ID of the channel
Pinephone has a Goodix GT917S capacitive touchscreen controller on
I2C0 bus. Add support for it.
Signed-off-by: Ondrej Jirman
---
.../dts/allwinner/sun50i-a64-pinephone.dtsi | 19 +++
1 file changed, 19 insertions(+)
diff --git
Issue still reproduces on latest 5.8.0-rc2+
(8be3a53e18e0e1a98f288f6c7f5e9da3adbe9c49).
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi!
I've been seeing this warning occasionally, not sure if it has been
reported yet. It's not a regression as I remember seeing it in, at least,
5.7.
Anyway, here it is:
[ cut here ]
sysfs group 'power' not found for kobject 'i2c-7'
WARNING: CPU: 1 PID: 17996 at
1 - 100 of 123 matches
Mail list logo
