https://bugzilla.kernel.org/show_bug.cgi?id=206987
Jan Kokemüller (jan.kokemuel...@gmail.com) changed:
What|Removed |Added
CC||jan.kokemuel.
On 08/02/2021 19:55, Tony Lindgren wrote:
> Hi,
>
> * Tomi Valkeinen [201124 12:47]:
>> From: Sebastian Reichel
>>
>> In preparation for removing custom DSS calls from the DSI
>> panel driver, this moves support for external tearing event
>> GPIOs into the DSI host driver. This way tearing event
On 2/6/2021 1:30 AM, Ville Syrjälä wrote:
On Thu, Feb 04, 2021 at 12:18:41PM +0530, Ankit Nautiyal wrote:
Currently the FRL training mode (Concurrent, Sequential) and
training type (Normal, Extended) are not defined properly and
are passed as bool values in drm_helpers for pcon
configuration fo
On Wed, 2021-02-10 at 13:03 -0500, Lyude Paul wrote:
> On Wed, 2021-02-10 at 00:33 -0800, Khaled Almahallawy wrote:
> > The number of AUX retries specified in the DP specs is 7.
> > Currently, to make
> > Dell 4k monitors happier, the number of retries are 32.
> > i915 also retries 5 times (intel_d
Currently the FRL training mode (Concurrent, Sequential) and
training type (Normal, Extended) are not defined properly and
are passed as bool values in drm_helpers for pcon
configuration for FRL training.
This patch:
-Add register masks for Sequential and Normal FRL training options.
-Fixes the dr
On 11/02/2021, Chema Casanova wrote:
>
> On 5/2/21 13:28, Yukimasa Sugizaki wrote:
>> On 05/02/2021, Eric Anholt wrote:
>>> On Thu, Feb 4, 2021 at 10:09 AM Chema Casanova
>>> wrote:
On 3/9/20 18:48, Yukimasa Sugizaki wrote:
> From: Yukimasa Sugizaki
>
> The default timeout is 5
Dne četrtek, 11. februar 2021 ob 03:28:00 CET je Stephen Boyd napisal(a):
> Quoting Maxime Ripard (2021-02-10 02:29:04)
>
> > Hi Mike, Stephen,
> >
> > On Tue, Feb 09, 2021 at 06:58:56PM +0100, Jernej Skrabec wrote:
> > > CLK_SET_RATE_PARENT flag is checked on parent clock instead of current
> >
Hi Aditya,
Thanks for your review comments.
-Original Message-
From: Aditya Swarup
Sent: Wednesday, February 10, 2021 9:54 PM
To: Ram Moon, AnandX ;
intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; Roper,
Matthew D ; Auld, Matthew ;
Surendrakumar Upadhyay, Tejaskumar
To complement panel-simple.yaml, create panel-simple-lvds-dual-ports.yaml.
panel-simple-lvds-dual-ports.yaml is for all simple LVDS panels that
have dual LVDS ports and require only a single power-supply.
The first port receives odd pixels, and the second port receives even pixels.
Optionally, a ba
On Mon, Feb 08, 2021 at 06:39:00PM -0500, Lyude Paul wrote:
> Since we're about to implement eDP backlight support in nouveau using the
> standard protocol from VESA, we might as well just take the code that's
> already written for this and move it into a set of shared DRM helpers.
>
> Note that t
On Mon, Feb 08, 2021 at 06:38:55PM -0500, Lyude Paul wrote:
> Get rid of the extraneous switch case in here, and just open code
> edp_backlight_mode as we only ever use it once.
>
> v4:
> * Check that backlight mode is DP_EDP_BACKLIGHT_CONTROL_MODE_DPCD, not
> DP_EDP_BACKLIGHT_CONTROL_MODE_MASK
On Mon, Feb 08, 2021 at 06:38:58PM -0500, Lyude Paul wrote:
> If we can't read DP_EDP_PWMGEN_BIT_COUNT in
> intel_dp_aux_vesa_calc_max_backlight() but do have a valid PWM frequency
> defined in the VBT, we'll keep going in the function until we inevitably
> fail on reading DP_EDP_PWMGEN_BIT_COUNT_C
On Mon, Feb 08, 2021 at 06:38:59PM -0500, Lyude Paul wrote:
> Also, stop printing the DPCD register that failed, and just describe it
> instead. Saves us from having to look up each register offset when reading
> through kernel logs (plus, DPCD dumping with drm.debug |= 0x100 will give
> us that an
Hi Omar,
On Wed 2021-02-10 @ 02:31:11 PM, Omar Emara wrote:
> If applying to GSoC will not take much time from you, I think you should apply
> regardless and leave the acceptance decision on a per-project basis.
GSoC works, literally, the other way around. Unfortunately GSoC doesn't start
with st
Many of the DSI flags have names opposite to their actual effects,
e.g. MIPI_DSI_MODE_EOT_PACKET means that EoT packets will actually
be disabled. Fix this by including _NO_ in the flag names, e.g.
MIPI_DSI_MODE_NO_EOT_PACKET.
Signed-off-by: Nicolas Boichat
---
I considered adding _DISABLE_ inste
On Tue, Feb 09, 2021 at 04:28:29PM -0500, Lyude Paul wrote:
> With the introduction of gen9_bc, where Intel combines Cometlake CPUs with
> a Tigerpoint PCH, we'll need to introduce new DDC pin mappings for this
> platform in order to make all of the display connectors work. So, let's do
> that.
>
On Wed, 2021-02-10 at 12:33 -0600, Rob Herring wrote:
> On Tue, Feb 09, 2021 at 10:13:12PM +0800, Liu Ying wrote:
> > To complement panel-simple.yaml, create panel-simple-lvds-dual-
> > ports.yaml.
> > panel-simple-lvds-dual-ports.yaml is for all simple LVDS panels
> > that
> > have dual LVDS ports
On Tue, Feb 09, 2021 at 04:28:31PM -0500, Lyude Paul wrote:
> Apparently the new gen9_bc platforms that Intel has introduced don't
> provide us with a STRAP config register to read from for initializing DDI
> B, C, and D detection. So, workaround this by hard-coding our strap config
> in intel_setu
On Tue, Feb 09, 2021 at 04:28:30PM -0500, Lyude Paul wrote:
> Next, let's start introducing the HPD pin mappings for Intel's new gen9_bc
> platform in order to make hotplugging display connectors work. Since
> gen9_bc is just a TGP PCH along with a CML CPU, except with the same HPD
> mappings as IC
On Tue, Feb 09, 2021 at 04:28:28PM -0500, Lyude Paul wrote:
> Since Intel has introduced the gen9_bc platform, a combination of
> Tigerpoint PCHs and CML CPUs, let's recognize such platforms as valid and
> avoid WARNing on them.
>
> Changes since v4:
> * Split this into it's own patch - vsyrjala
>
Quoting Maxime Ripard (2021-02-10 02:29:04)
> Hi Mike, Stephen,
>
> On Tue, Feb 09, 2021 at 06:58:56PM +0100, Jernej Skrabec wrote:
> > CLK_SET_RATE_PARENT flag is checked on parent clock instead of current
> > one. Fix that.
> >
> > Fixes: 3f790433c3cb ("clk: sunxi-ng: Adjust MP clock parent rat
On 2/10/21 4:59 AM, Daniel Vetter wrote:
...
GPU atomic operations to sysmem are hard to categorize, because because
application
programmers could easily write programs that do a long series of atomic
operations.
Such a program would be a little weird, but it's hard to rule out.
Yeah, but we
Hey,
This is super late in the cycle, but after talking it over with Dave,
it's probably best to get this in sooner rather than later. The vast
majority of the changes are simple and repetitive, but invasive in
that the constructor function signature of every sub-device module for
every chipset i
There is a regular need in the kernel to provide a way to declare having
a dynamically sized set of trailing elements in a structure. Kernel code
should always use “flexible array members”[1] for these cases. The older
style of one-element or zero-length arrays should no longer be used[2].
Use fle
On Tue, Feb 9, 2021 at 5:24 PM Jordan Crouse wrote:
>
> On Mon, Feb 08, 2021 at 01:55:54PM -0500, Jonathan Marek wrote:
> > The cleanup patch broke a6xx_gmu_clear_oob, fix it by adding the missing
> > bitshift operation.
> >
> > Fixes: 555c50a4a19b ("drm/msm: Clean up GMU OOB set/clear handling")
On 2/10/21 7:49 AM, Dave Stevenson wrote:
> Hi Marc.
>
> On Wed, 10 Feb 2021 at 15:30, Marc Zyngier wrote:
>>
>> Hi Maxime,
>>
>> On 2021-02-10 14:40, Maxime Ripard wrote:
>>> Hi Dave,
>>>
>>> On Tue, Feb 09, 2021 at 09:49:05AM +, Dave Stevenson wrote:
On Mon, 11 Jan 2021 at 14:23, Maxim
There is a regular need in the kernel to provide a way to declare having
a dynamically sized set of trailing elements in a structure. Kernel code
should always use “flexible array members”[1] for these cases. The older
style of one-element or zero-length arrays should no longer be used[2].
Use fle
On Wed, Feb 10, 2021 at 05:07:03PM +0200, Ville Syrjälä wrote:
> On Wed, Feb 10, 2021 at 01:38:45PM +, Simon Ser wrote:
> > On Wednesday, February 10th, 2021 at 2:16 PM, Daniel Vetter
> > wrote:
> >
> > > On Tue, Feb 09, 2021 at 04:14:01PM -0800, Manasi Navare wrote:
> > >
> > > > These addi
On Wed, Feb 10, 2021 at 10:32 AM Christian König
wrote:
>
>
>
> Am 10.02.21 um 17:39 schrieb Suren Baghdasaryan:
> > On Wed, Feb 10, 2021 at 5:06 AM Daniel Vetter wrote:
> >> On Tue, Feb 09, 2021 at 12:16:51PM -0800, Suren Baghdasaryan wrote:
> >>> On Tue, Feb 9, 2021 at 12:03 PM Daniel Vetter w
On Tue, 09 Feb 2021 13:59:07 +0100, Nicolas Saenz Julienne wrote:
> BCM2711, Raspberry Pi 4's SoC, contains a V3D core. So add its specific
> compatible to the bindings.
>
> Signed-off-by: Nicolas Saenz Julienne
> ---
> Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml | 1 +
> 1 file chan
There is a regular need in the kernel to provide a way to declare having
a dynamically sized set of trailing elements in a structure. Kernel code
should always use “flexible array members”[1] for these cases. The older
style of one-element or zero-length arrays should no longer be used[2].
Refacto
Hi Dave, Daniel,
Just a single revert to fix a blank screen.
The following changes since commit 92bf22614b21a2706f4993b278017e437f7785b3:
Linux 5.11-rc7 (2021-02-07 13:57:38 -0800)
are available in the Git repository at:
https://gitlab.freedesktop.org/agd5f/linux.git
tags/amd-drm-fixes-5.
I see I already acked this, but if you haven't merged it yet there are
a few typos in the commit log:
On Thu, Feb 04, 2021 at 05:58:31PM +0100, Daniel Vetter wrote:
> Since 3234ac664a87 ("/dev/mem: Revoke mappings when a driver claims
> the region") /dev/kmem zaps ptes when the kernel requests exc
https://bugzilla.kernel.org/show_bug.cgi?id=211651
Artem S. Tashkinov (a...@gmx.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
On Wed, Feb 10, 2021 at 10:14 PM Simon Ser wrote:
> On Wednesday, February 10th, 2021 at 10:04 PM, Mario Kleiner <
> mario.kleiner...@gmail.com> wrote:
>
> > Ping!
>
> I now understand the problem better.
>
> Reviewed-by: Simon Ser
>
> I'll push to drm-misc-next in a few days if no-one complains
On 2/9/21 10:40 AM, Christian König wrote:
Am 09.02.21 um 15:30 schrieb Andrey Grodzovsky:
[SNIP]
Question - Why can't we just set those PTEs to point to system memory
(another RO dummy page)
filled with 1s ?
Then writes are not discarded. E.g. the 1s would change to something else.
Chris
On 2/9/2021 2:54 AM, Daniel Vetter wrote:
> On Tue, Jan 26, 2021 at 01:46:25PM -0800, Brian Welty wrote:
>> 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 t
On Fri, Feb 05, 2021 at 02:36:32PM +0100, Daniel Vetter wrote:
> We are already doing this for all the regular sysfs files on PCI
> devices, but not yet on the legacy io files on the PCI buses. Thus far
> no problem, but in the next patch I want to wire up iomem revoke
> support. That needs the vfs
On Wed, Feb 10, 2021 at 9:21 AM Daniel Vetter wrote:
>
> On Wed, Feb 10, 2021 at 5:39 PM Suren Baghdasaryan wrote:
> >
> > On Wed, Feb 10, 2021 at 5:06 AM Daniel Vetter wrote:
> > >
> > > On Tue, Feb 09, 2021 at 12:16:51PM -0800, Suren Baghdasaryan wrote:
> > > > On Tue, Feb 9, 2021 at 12:03 PM
Fix potential integer overflow by casting actual_calculated_clock_100hz
to u64, in order to give the compiler complete information about the
proper arithmetic to use.
Notice that such variable is used in a context that expects
an expression of type u64 (64 bits, unsigned) and the following
express
On Wednesday, February 10th, 2021 at 10:04 PM, Mario Kleiner
wrote:
> Ping!
I now understand the problem better.
Reviewed-by: Simon Ser
I'll push to drm-misc-next in a few days if no-one complains. Ping me
again if I forget.
___
dri-devel mailing l
Ping. Any bit of info appreciated wrt. the DCE-11.2+ situation.
-mario
On Mon, Jan 25, 2021 at 8:24 PM Mario Kleiner
wrote:
> Thanks Alex and Nicholas! Brings quite a bit of extra shiny to those older
> asics :)
>
> Nicholas, any thoughts on my cover-letter wrt. why a similar patch (that I
> wro
Ping! Anybody wanna review the most trivial, obviously correct, and
non-intrusive patch ever to fix a real bug? The Kodi devs changed their
broken constant and as if by magic, some LG TV now has working HDR support,
so we now know the constant is actually expected to be correct by at least
some rea
On Wed, Feb 10, 2021 at 5:06 AM Daniel Vetter wrote:
>
> On Tue, Feb 09, 2021 at 12:16:51PM -0800, Suren Baghdasaryan wrote:
> > On Tue, Feb 9, 2021 at 12:03 PM Daniel Vetter wrote:
> > >
> > > On Tue, Feb 9, 2021 at 6:46 PM Christian König
> > > wrote:
> > > >
> > > >
> > > >
> > > > Am 09.02.
Am 10.02.21 um 19:15 schrieb Daniel Vetter:
On Wed, Feb 10, 2021 at 5:05 PM Christian König
wrote:
The old implementation wasn't consistend on this.
But it looks like we depend on this so better bring it back.
Signed-off-by: Christian König
Reported-and-tested-by: Mike Galbraith
Fixes: d0
On Wed, Feb 10, 2021 at 3:41 AM wrote:
>
> On 2021-02-01 00:46, Rob Clark wrote:
> > On Fri, Dec 18, 2020 at 2:27 AM Kalyan Thota
> > wrote:
> >>
> >> Set the flag vblank_disable_immediate = true to turn off vblank irqs
> >> immediately as soon as drm_vblank_put is requested so that there are
> >
On Mon, 08 Feb 2021 09:42:21 +0800, Jitao Shi wrote:
> Add compatible "mediatek,mt8192-dpi" for the mt8192 dpi.
>
> Signed-off-by: Jitao Shi
> ---
> .../devicetree/bindings/display/mediatek/mediatek,dpi.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring
___
https://bugzilla.kernel.org/show_bug.cgi?id=211649
--- Comment #12 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
Thanks, this was what I'm looking for.
--
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=211649
--- Comment #11 from youling...@gmail.com ---
Created attachment 295201
--> https://bugzilla.kernel.org/attachment.cgi?id=295201&action=edit
trace.txt
cat /sys/kernel/debug/tracing/trace
--
You may reply to this email to add a comment.
You a
https://bugzilla.kernel.org/show_bug.cgi?id=211649
--- Comment #10 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
I don't expect the trace log to be completely empty.
You'll need to leave the trace log running after enabling it as well (with
tracing on/trace).
You'll also need variou
https://bugzilla.kernel.org/show_bug.cgi?id=211649
--- Comment #9 from youling...@gmail.com ---
Created attachment 295197
--> https://bugzilla.kernel.org/attachment.cgi?id=295197&action=edit
dmesg.txt
I delete "read -n 1", can output dmesg.txt and trace.txt.
trace.txt,
# tracer: function
#
# en
https://bugzilla.kernel.org/show_bug.cgi?id=211649
--- Comment #8 from youling...@gmail.com ---
(In reply to Nicholas Kazlauskas from comment #7)
> That makes more sense then, that's the behavior I'd expect on CrOS/Android.
>
> Also explains why we haven't seen this on X/Wayland based compositors
Am 10.02.21 um 20:12 schrieb Suren Baghdasaryan:
On Wed, Feb 10, 2021 at 10:32 AM Christian König
wrote:
Am 10.02.21 um 17:39 schrieb Suren Baghdasaryan:
On Wed, Feb 10, 2021 at 5:06 AM Daniel Vetter wrote:
On Tue, Feb 09, 2021 at 12:16:51PM -0800, Suren Baghdasaryan wrote:
On Tue, Feb
On Tue, Feb 09, 2021 at 10:13:12PM +0800, Liu Ying wrote:
> To complement panel-simple.yaml, create panel-simple-lvds-dual-ports.yaml.
> panel-simple-lvds-dual-ports.yaml is for all simple LVDS panels that
> have dual LVDS ports and require only a single power-supply.
> The first port receives odd
Am 10.02.21 um 17:39 schrieb Suren Baghdasaryan:
On Wed, Feb 10, 2021 at 5:06 AM Daniel Vetter wrote:
On Tue, Feb 09, 2021 at 12:16:51PM -0800, Suren Baghdasaryan wrote:
On Tue, Feb 9, 2021 at 12:03 PM Daniel Vetter wrote:
On Tue, Feb 9, 2021 at 6:46 PM Christian König wrote:
Am 09.02.
https://bugzilla.kernel.org/show_bug.cgi?id=211649
--- Comment #7 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
That makes more sense then, that's the behavior I'd expect on CrOS/Android.
Also explains why we haven't seen this on X/Wayland based compositors like
GNOME on Ubuntu.
One
On 5/2/21 13:28, Yukimasa Sugizaki wrote:
On 05/02/2021, Eric Anholt wrote:
On Thu, Feb 4, 2021 at 10:09 AM Chema Casanova
wrote:
On 3/9/20 18:48, Yukimasa Sugizaki wrote:
From: Yukimasa Sugizaki
The default timeout is 500 ms which is too short for some workloads
including Piglit. Adding
On Wed, Feb 10, 2021 at 5:05 PM Christian König
wrote:
>
> The old implementation wasn't consistend on this.
>
> But it looks like we depend on this so better bring it back.
>
> Signed-off-by: Christian König
> Reported-and-tested-by: Mike Galbraith
> Fixes: d099fc8f540a ("drm/ttm: new TT backen
On Wed, 2021-02-10 at 00:33 -0800, Khaled Almahallawy wrote:
> The number of AUX retries specified in the DP specs is 7. Currently, to make
> Dell 4k monitors happier, the number of retries are 32.
> i915 also retries 5 times (intel_dp_aux_xfer) which means in the case of AUX
> timeout we actually
On Tue, Feb 09, 2021 at 12:53:27PM -0800, John Hubbard wrote:
> This direction sounds at least...possible. Using MMU notifiers instead of pins
> is definitely appealing. I'm not quite clear on the callback idea above, but
> overall it seems like taking advantage of the ZONE_DEVICE tracking of page
On Tue, Feb 09, 2021 at 04:17:38PM -0500, Jerome Glisse wrote:
> > > Yes, I would like to avoid the long term pin constraints as well if
> > > possible I
> > > just haven't found a solution yet. Are you suggesting it might be
> > > possible to
> > > add a callback in the page migration logic to
Hi Bjorn,
Can you ack this for merging through my topic branch with the other
follow_pfn/iomem revoke fixes for 5.12?
If not, what's the plan for getting this (or equivalent functionality)
in for 5.13? I have more of these follow_pfn/iomem revoke patches on
top, so I'd like to get the first cut m
https://bugzilla.kernel.org/show_bug.cgi?id=211649
--- Comment #6 from youling...@gmail.com ---
Created attachment 295193
--> https://bugzilla.kernel.org/attachment.cgi?id=295193&action=edit
amdgpu_dm_dtn_log
I using amd 3400g running on androidx86 7 with mesa21.0
cat /sys/kernel/debug/dri/0/a
On Wed, Feb 10, 2021 at 5:39 PM Suren Baghdasaryan wrote:
>
> On Wed, Feb 10, 2021 at 5:06 AM Daniel Vetter wrote:
> >
> > On Tue, Feb 09, 2021 at 12:16:51PM -0800, Suren Baghdasaryan wrote:
> > > On Tue, Feb 9, 2021 at 12:03 PM Daniel Vetter wrote:
> > > >
> > > > On Tue, Feb 9, 2021 at 6:46 PM
https://bugzilla.kernel.org/show_bug.cgi?id=211649
--- Comment #5 from Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) ---
It would be good to know what OS/Userspace this is, I don't think I've seen
anything that has atomic check failures on nearly every flip, eg:
[ 179.142898] [drm:amdgpu_dm_
https://bugzilla.kernel.org/show_bug.cgi?id=211649
--- Comment #4 from youling...@gmail.com ---
Created attachment 295189
--> https://bugzilla.kernel.org/attachment.cgi?id=295189&action=edit
dmesg.txt
echo 6 > /sys/module/drm/parameters/debug
replug hdmi dmesg.
--
You may reply to this email
On Allwinner SoC interrupt debounce can be controlled by two oscillator
(32KHz and 24MHz) and a prescale divider.
Oscillator and prescale divider are set through
device tree property "input-debounce" which have 1uS accuracy.
For acheive nS precision a new device tree poperty is made
named "input-d
On 2/10/21 3:54 AM, Anand Moon wrote:
> Add table to map the GMBUS pin pairs to GPIO registers and port to DDC
> mapping for ADL_S as per below Bspec.
Has this patch been tested on an ADLS system? Upstream CI AFAIK doesn't have
support for ADL-S. Also comments below..
>
> Bspec:20124, 53597.
>
Hi
Am 29.06.20 um 11:06 schrieb Daniel Vetter:
+ ARRAY_SIZE(simplekms_formats),
+ simplekms_format_modifiers,
+ connector);
+ if (ret)
+ return ret;
+
https://bugzilla.kernel.org/show_bug.cgi?id=211649
--- Comment #3 from youling...@gmail.com ---
replug hdmi, [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR* [CRTC:67:crtc-0] flip_done timed out
[ 252.377374] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR*
On Wed, 10 Feb 2021, Daniel Vetter wrote:
> On Wed, Feb 10, 2021 at 08:23:41AM +, Lee Jones wrote:
> > On Tue, 09 Feb 2021, Julia Lawall wrote:
> >
> > > Use getter and setter functions, for platform_device structures and a
> > > spi_device structure.
> > >
> > > Signed-off-by: Julia Lawall
https://bugzilla.kernel.org/show_bug.cgi?id=210263
--- Comment #3 from Fabian (plusf...@gmail.com) ---
(In reply to ninelore from comment #2)
> I just found out that this Issue does NOT occur when you additionally add
> the fbcon=nodefer kernel parameter.
This workaround works for me too.
--
Yo
The old implementation wasn't consistend on this.
But it looks like we depend on this so better bring it back.
Signed-off-by: Christian König
Reported-and-tested-by: Mike Galbraith
Fixes: d099fc8f540a ("drm/ttm: new TT backend allocation pool v3")
---
drivers/gpu/drm/ttm/ttm_pool.c | 10 ++
Hi Marc.
On Wed, 10 Feb 2021 at 15:30, Marc Zyngier wrote:
>
> Hi Maxime,
>
> On 2021-02-10 14:40, Maxime Ripard wrote:
> > Hi Dave,
> >
> > On Tue, Feb 09, 2021 at 09:49:05AM +, Dave Stevenson wrote:
> >> On Mon, 11 Jan 2021 at 14:23, Maxime Ripard wrote:
> >> >
> >> > The BSC controllers u
Hi Maxime,
On 2021-02-10 14:40, Maxime Ripard wrote:
Hi Dave,
On Tue, Feb 09, 2021 at 09:49:05AM +, Dave Stevenson wrote:
On Mon, 11 Jan 2021 at 14:23, Maxime Ripard wrote:
>
> The BSC controllers used for the HDMI DDC have an interrupt controller
> shared between both instances. Let's ad
Instead evict round robin from each devices SYSTEM and TT domain.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c| 31 ++-
drivers/gpu/drm/ttm/ttm_bo_util.c | 1 -
drivers/gpu/drm/ttm/ttm_device.c| 59 +
drivers/gpu/drm/vmwgf
Instead of having a global lock.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 8 ++---
drivers/gpu/drm/qxl/qxl_release.c | 5 +--
drivers/gpu/drm/ttm/ttm_bo.c | 49 --
drivers/gpu/drm/ttm/ttm_device.c | 12 +++
dri
Move the iteration of the global lru into the new function
ttm_global_swapout() and use that instead in drivers.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c| 57 -
drivers/gpu/drm/ttm/ttm_device.c| 29 +++
drivers/gpu/drm/tt
On Wed, Feb 10, 2021 at 01:38:45PM +, Simon Ser wrote:
> On Wednesday, February 10th, 2021 at 2:16 PM, Daniel Vetter
> wrote:
>
> > On Tue, Feb 09, 2021 at 04:14:01PM -0800, Manasi Navare wrote:
> >
> > > These additional checks added to avoid EBUSY give unnecessary WARN_ON
> > > in case of
https://bugzilla.kernel.org/show_bug.cgi?id=211649
Nicholas Kazlauskas (nicholas.kazlaus...@amd.com) changed:
What|Removed |Added
CC||nichol
Hi Dave,
On Tue, Feb 09, 2021 at 09:49:05AM +, Dave Stevenson wrote:
> On Mon, 11 Jan 2021 at 14:23, Maxime Ripard wrote:
> >
> > The BSC controllers used for the HDMI DDC have an interrupt controller
> > shared between both instances. Let's add it to avoid polling.
>
> This seems to have un
https://bugzilla.kernel.org/show_bug.cgi?id=211649
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
Op 2021-02-10 om 04:11 schreef Stephen Rothwell:
> Hi all,
>
> After merging the drm-misc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/gpu/drm/v3d/v3d_sched.c:263:1: error: return type is an incomplete
> type
> 263 | v3d_gpu_reset_for_timeout(struct v3d_de
Hi
Am 10.02.21 um 14:10 schrieb Daniel Vetter:
On Tue, Feb 09, 2021 at 11:29:13AM +0100, Thomas Zimmermann wrote:
The function drm_gem_fb_prepare_fb() is a helper for atomic modesetting,
but currently located next to framebuffer helpers. Move it to GEM atomic
helpers, rename it slightly and ado
Hi Dave and Daniel,
here's this week's PR for drm-misc-fixes. There's a buffer overflow in vc4
and a memory leak in xlnx. The rest appear to be mere bug fixes.
Best regards
Thomas
drm-misc-fixes-2021-02-10:
* dp_mst: Don't report un-attached ports as connected
* sun4i: tcon1 sync polarity fix;
On Wednesday, February 10th, 2021 at 2:16 PM, Daniel Vetter
wrote:
> On Tue, Feb 09, 2021 at 04:14:01PM -0800, Manasi Navare wrote:
>
> > These additional checks added to avoid EBUSY give unnecessary WARN_ON
> > in case of big joiner used in i915 in which case even if the modeset
> > is requeste
On Tue, Feb 09, 2021 at 04:14:01PM -0800, Manasi Navare wrote:
> This reverts commit fb6473a48b635c55d04eb94e579eede52ef39550.
>
> These additional checks added to avoid EBUSY give unnecessary WARN_ON
> in case of big joiner used in i915 in which case even if the modeset
> is requested on a single
On Wed, 10 Feb 2021, Daniel Vetter wrote:
> On Wed, Feb 10, 2021 at 08:23:41AM +, Lee Jones wrote:
> > On Tue, 09 Feb 2021, Julia Lawall wrote:
> >
> > > Use getter and setter functions, for platform_device structures and a
> > > spi_device structure.
> > >
> > > Signed-off-by: Julia Lawall
On Wed, Feb 10, 2021 at 08:45:56AM +0100, Christian König wrote:
> Reviewed-by: Christian König for the series.
Smash it into -misc?
-Daniel
>
> Am 10.02.21 um 00:48 schrieb Rikard Falkeborn:
> > Constify a few static vm_operations_struct that are never modified. Their
> > only usage is to assi
On Wed, Feb 10, 2021 at 08:23:41AM +, Lee Jones wrote:
> On Tue, 09 Feb 2021, Julia Lawall wrote:
>
> > Use getter and setter functions, for platform_device structures and a
> > spi_device structure.
> >
> > Signed-off-by: Julia Lawall
> >
> > ---
> > drivers/video/backlight/qcom-wled.c
On Tue, Feb 09, 2021 at 10:13:04PM +0100, Julia Lawall wrote:
> Use getter and setter functions, for platform_device structures and a
> mipi_dsi_device structure.
>
> Signed-off-by: Julia Lawall
Applied to drm-misc-next, thanks for the patch.
-Daniel
>
> ---
> drivers/gpu/drm/aspeed/aspeed_gfx
On Tue, Feb 09, 2021 at 11:29:13AM +0100, Thomas Zimmermann wrote:
> The function drm_gem_fb_prepare_fb() is a helper for atomic modesetting,
> but currently located next to framebuffer helpers. Move it to GEM atomic
> helpers, rename it slightly and adopt the drivers. Same for the rsp
> simple-pip
On Tue, Feb 09, 2021 at 12:16:51PM -0800, Suren Baghdasaryan wrote:
> On Tue, Feb 9, 2021 at 12:03 PM Daniel Vetter wrote:
> >
> > On Tue, Feb 9, 2021 at 6:46 PM Christian König
> > wrote:
> > >
> > >
> > >
> > > Am 09.02.21 um 18:33 schrieb Suren Baghdasaryan:
> > > > On Tue, Feb 9, 2021 at 4:5
On Tue, Feb 09, 2021 at 12:53:27PM -0800, John Hubbard wrote:
> On 2/9/21 5:37 AM, Daniel Vetter wrote:
> > On Tue, Feb 9, 2021 at 1:57 PM Alistair Popple wrote:
> > >
> > > On Tuesday, 9 February 2021 9:27:05 PM AEDT Daniel Vetter wrote:
> > > > >
> > > > > Recent changes to pin_user_pages() pr
On Wed, Feb 10, 2021 at 02:40:10PM +1100, Alistair Popple wrote:
> On Wednesday, 10 February 2021 12:39:32 AM AEDT Jason Gunthorpe wrote:
> > On Tue, Feb 09, 2021 at 12:07:14PM +1100, Alistair Popple wrote:
> > > Device private pages are used to represent device memory that is not
> > > directly ac
Hi,
On Wed, Feb 10, 2021 at 01:25:17PM +0100, Pavel Machek wrote:
> Hi!
>
> > commit 83404d581471775f37f85e5261ec0d09407d8bed upstream.
> >
> > This function will be needed by the next patch where the driver
> > calculates the BW based on driver specific parameters, so export it.
> >
> > At the
On Wed, Feb 10, 2021 at 08:52:29AM +0100, Thomas Zimmermann wrote:
> Hi
>
> Am 09.02.21 um 11:54 schrieb Daniel Vetter:
> > *: vmwgfx is the only non-gem driver, but there's plans to move at least
> > vmwgfx internals (maybe not the uapi, we'll see) over to gem. Once that's
> > done it's truly all
Hi!
> commit 83404d581471775f37f85e5261ec0d09407d8bed upstream.
>
> This function will be needed by the next patch where the driver
> calculates the BW based on driver specific parameters, so export it.
>
> At the same time sanitize the function params, passing the more natural
> link rate inste
On 2021-02-01 00:46, Rob Clark wrote:
On Fri, Dec 18, 2020 at 2:27 AM Kalyan Thota
wrote:
Set the flag vblank_disable_immediate = true to turn off vblank irqs
immediately as soon as drm_vblank_put is requested so that there are
no irqs triggered during idle state. This will reduce cpu wakeups
On 09/02/2021 15:48, Enric Balletbo Serra wrote:
> Hi Hsin-Yi,
>
> Thank you for your patch.
>
> Missatge de Hsin-Yi Wang del dia dv., 29 de gen.
> 2021 a les 10:23:
>>
>> From: Yongqiang Niu
>>
>> Add mtk mutex support for MT8183 SoC.
>>
>> Signed-off-by: Yongqiang Niu
>> Signed-off-by: Hs
1 - 100 of 126 matches
Mail list logo