Hi,
We would like to report the following bug which has been found by our
modified version of syzkaller.
==
description: KMSAN: uninit-value in __dma_map_sg_attrs
affected file: kernel/dma/mapping.c
kernel version: 6.2.0-rc5
kernel commit: 41c66
On 17/02/2023 22:13, Bryan O'Donoghue wrote:
> On 17/02/2023 12:24, Krzysztof Kozlowski wrote:
>> First, it would be nice to know what was the intention of Bryan's commit?
>
> Sorry I've been grazing this thread but, not responding.
>
> - qcom,dsi-ctrl-6g-qcm2290
>
> is non-compliant with qcom,s
On 07/02/2023 13:47, Pekka Paalanen wrote:
> On Fri, 13 Jan 2023 11:24:07 -0500
> Harry Wentland wrote:
>
>> This patchset enables the DP and HDMI infoframe properties
>> in amdgpu.
>>
>> The first two patches are not completely related to the rest. The
>> first patch allows for HDR_OUTPUT_METADA
Hi Maxime,
On 26/01/2023 14:46, Maxime Ripard wrote:
> container_of_const() allows to preserve the pointer constness and is
> thus more flexible than inline functions.
>
> Let's switch all our instances of container_of() to
> container_of_const().
>
> Signed-off-by: Maxime Ripard
> ---
> drive
On 17.02.2023 22:07, Dmitry Baryshkov wrote:
> On 14/02/2023 19:31, Konrad Dybcio wrote:
>> Currently we only utilize the OPP table connected to the GPU for
>> getting (available) frequencies. We do however need to scale the
>> voltage rail(s) accordingly to ensure that we aren't trying to
>> ru
This series is developed for and tested on MT8173 board, and the layout is:
/-- anx7688
-- MT8173 HDMI bridge -- GPIO mux
\-- native HDMI
v2: https://lore.kernel.org/all/20230116110820.2615650-1-treapk...@chromium.org/
v1:
https
Introduce a optional "ddc-i2c-bus" property for anx7688 bridge. This
allows the bridge to register a .get_edid callback.
Signed-off-by: Pin-yen Lin
---
Changes in v3:
- New in v3
.../bindings/display/bridge/google,cros-ec-anx7688.yaml | 5 +
1 file changed, 5 insertions(+)
diff --git
Allow the driver to read EDID when ddc-i2c-bus phandle is present in
the device node.
Signed-off-by: Pin-yen Lin
---
Changes in v3:
- New in v3
drivers/gpu/drm/bridge/cros-ec-anx7688.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/gpu/drm/bridge/cros-ec-
The original implementation peaking into the remote nodes to get the
ddc bus fwnode, which is not a good practice. Remove the callback from
this driver and rely on drm_connector helpers to read EDID.
Signed-off-by: Pin-yen Lin
---
Changes in v3:
- New in v3
drivers/gpu/drm/mediatek/mtk_hdmi.c
From: Nicolas Boichat
This driver supports single input, 2 output display mux (e.g.
HDMI mux), that provide its status via a GPIO.
Signed-off-by: Nicolas Boichat
Signed-off-by: Pin-yen Lin
---
Changes in v3:
- Added .get_edid callback in generic-gpio-mux driver
Changes in v2:
- Dropped atta
From: Nicolas Boichat
Add bindings for Generic GPIO mux driver.
Signed-off-by: Nicolas Boichat
Signed-off-by: Pin-yen Lin
---
Rob mentioned that this series can probably use the common MUX bindings.
Those bindings are designed for MUX consumers that requests a certain
MUX configuration, while
On 18.02.2023 11:14, Krzysztof Kozlowski wrote:
> On 17/02/2023 22:13, Bryan O'Donoghue wrote:
>> On 17/02/2023 12:24, Krzysztof Kozlowski wrote:
>>> First, it would be nice to know what was the intention of Bryan's commit?
>>
>> Sorry I've been grazing this thread but, not responding.
>>
>> - q
Hi Maxime, Dave,
On 26/01/2023 14:46, Maxime Ripard wrote:
> From: Dave Stevenson
>
> Copy Intel's "Broadcast RGB" property semantics to add manual override
> of the HDMI pixel range for monitors that don't abide by the content
> of the AVI Infoframe.
Do we have to copy that property as-is?
Fi
On 15/02/2023 11:09, Karol Herbst wrote:
> On Wed, Feb 15, 2023 at 11:36 AM Linux regression tracking #update
> (Thorsten Leemhuis) wrote:
>>
>> On 13.02.23 10:14, Chris Clayton wrote:
>>> On 13/02/2023 02:57, Dave Airlie wrote:
On Sun, 12 Feb 2023 at 00:43, Chris Clayton
wrote:
>>>
On Sat, Feb 18, 2023 at 1:22 PM Chris Clayton wrote:
>
>
>
> On 15/02/2023 11:09, Karol Herbst wrote:
> > On Wed, Feb 15, 2023 at 11:36 AM Linux regression tracking #update
> > (Thorsten Leemhuis) wrote:
> >>
> >> On 13.02.23 10:14, Chris Clayton wrote:
> >>> On 13/02/2023 02:57, Dave Airlie wrot
On 17/02/2023 23:21, Konrad Dybcio wrote:
On 17.02.2023 22:19, Dmitry Baryshkov wrote:
On 14/02/2023 19:31, Konrad Dybcio wrote:
A619_holi is a GMU-less variant of the already-supported A619 GPU.
It's present on at least SM4350 (holi) and SM6375 (blair). No mesa
changes are required. Add the
On 18/02/2023 12:23, Konrad Dybcio wrote:
>
>
> On 18.02.2023 11:14, Krzysztof Kozlowski wrote:
>> On 17/02/2023 22:13, Bryan O'Donoghue wrote:
>>> On 17/02/2023 12:24, Krzysztof Kozlowski wrote:
First, it would be nice to know what was the intention of Bryan's commit?
>>>
>>> Sorry I've bee
On 18/02/2023 12:25, Karol Herbst wrote:
> On Sat, Feb 18, 2023 at 1:22 PM Chris Clayton
> wrote:
>>
>>
>>
>> On 15/02/2023 11:09, Karol Herbst wrote:
>>> On Wed, Feb 15, 2023 at 11:36 AM Linux regression tracking #update
>>> (Thorsten Leemhuis) wrote:
On 13.02.23 10:14, Chris Clayt
On Tue, Feb 14, 2023 at 10:35 PM Ville Syrjälä
wrote:
[...]
> > > We should perhaps just get rid of HDMI_VENDOR_INFOFRAME_SIZE
> > > entirely.
> > My thought was to make it the correct size for
> > drm_hdmi_vendor_infoframe_from_display_mode(). Then developers using
> > this "common" vendor infofr
On 18/02/2023 13:04, Konrad Dybcio wrote:
On 17.02.2023 22:07, Dmitry Baryshkov wrote:
On 14/02/2023 19:31, Konrad Dybcio wrote:
Currently we only utilize the OPP table connected to the GPU for
getting (available) frequencies. We do however need to scale the
voltage rail(s) accordingly to ens
On Tue, 2023-02-14 at 13:38 -0800, Teres Alexis, Alan Previn wrote:
> Enable PXP with MTL-GSC-CS: add the has_pxp into device info
> and increase the timeouts for new GSC-CS + firmware specs.
>
> Signed-off-by: Alan Previn
> ---
> drivers/gpu/drm/i915/i915_pci.c | 1 +
> drivers/gpu
On 18/02/2023 15:19, Chris Clayton wrote:
>
>
> On 18/02/2023 12:25, Karol Herbst wrote:
>> On Sat, Feb 18, 2023 at 1:22 PM Chris Clayton
>> wrote:
>>>
>>>
>>>
>>> On 15/02/2023 11:09, Karol Herbst wrote:
On Wed, Feb 15, 2023 at 11:36 AM Linux regression tracking #update
(Thorsten
On Thu, Feb 16, 2023 at 16:24 PM, Oded Gabbay wrote:
>
> On Thu, Feb 16, 2023 at 12:53 PM Stanislaw Gruszka
> wrote:
> >
> > On Sun, Feb 12, 2023 at 10:44:28PM +0200, Oded Gabbay wrote:
> > > @@ -3178,11 +3181,12 @@ static int
> > > ts_buff_get_kernel_ts_record(struct hl_mmap_mem_buf *buf,
> > >
On Thu, Feb 16, 2023 at 3:00 AM Tvrtko Ursulin
wrote:
>
> From: Tvrtko Ursulin
>
> Track how many callers are explicity waiting on a fence to signal and
> allow querying that via new dma_fence_wait_count() API.
>
> This provides infrastructure on top of which generic "waitboost" concepts
> can be
On Thu, Feb 16, 2023 at 2:59 AM Tvrtko Ursulin
wrote:
>
> From: Tvrtko Ursulin
>
> Use the previously added dma-fence tracking of explicit waiters.
>
> Signed-off-by: Tvrtko Ursulin
> ---
> drivers/gpu/drm/drm_syncobj.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --gi
From: Rob Clark
This series adds deadline awareness to fences, so realtime deadlines
such as vblank can be communicated to the fence signaller for power/
frequency management decisions.
This is partially inspired by a trick i915 does, but implemented
via dma-fence for a couple of reasons:
1) To
From: Rob Clark
Propagate the deadline to all the fences in the array.
Signed-off-by: Rob Clark
Reviewed-by: Christian König
---
drivers/dma-buf/dma-fence-array.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/dma-buf/dma-fence-array.c
b/drivers/dma-buf/dma-fence-ar
From: Rob Clark
Add a way to hint to the fence signaler of an upcoming deadline, such as
vblank, which the fence waiter would prefer not to miss. This is to aid
the fence signaler in making power management decisions, like boosting
frequency as the deadline approaches and awareness of missing de
From: Rob Clark
Allow userspace to use the EPOLLPRI/POLLPRI flag to indicate an urgent
wait (as opposed to a "housekeeping" wait to know when to cleanup after
some work has completed). Usermode components of GPU driver stacks
often poll() on fence fd's to know when it is safe to do things like
f
From: Rob Clark
This consists of simply storing the most recent deadline, and adding an
ioctl to retrieve the deadline. This can be used in conjunction with
the SET_DEADLINE ioctl on a fence fd for testing. Ie. create various
sw_sync fences, merge them into a fence-array, set deadline on the
fe
From: Rob Clark
Propagate the deadline to all the fences in the chain.
Signed-off-by: Rob Clark
Reviewed-by: Christian König for this one.
---
drivers/dma-buf/dma-fence-chain.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/dma-buf/dma-fence-chain.c
b/drivers/dma-
As the finished fence is the one that is exposed to userspace, and
therefore the one that other operations, like atomic update, would
block on, we need to propagate the deadline from from the finished
fence to the actual hw fence.
v2: Split into drm_sched_fence_set_parent() (ckoenig)
v3: Ensure a
From: Rob Clark
For an atomic commit updating a single CRTC (ie. a pageflip) calculate
the next vblank time, and inform the fence(s) of that deadline.
v2: Comment typo fix (danvet)
Signed-off-by: Rob Clark
Reviewed-by: Daniel Vetter
Signed-off-by: Rob Clark
---
drivers/gpu/drm/drm_atomic_he
From: Rob Clark
Add a way to set a deadline on remaining resv fences according to the
requested usage.
Signed-off-by: Rob Clark
---
drivers/dma-buf/dma-resv.c | 19 +++
include/linux/dma-resv.h | 2 ++
2 files changed, 21 insertions(+)
diff --git a/drivers/dma-buf/dma-resv.
From: Rob Clark
Will be used in the next commit to set a deadline on fences that an
atomic update is waiting on.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/drm_vblank.c | 32
include/drm/drm_vblank.h | 1 +
2 files changed, 33 insertions(+)
diff --git a
From: Rob Clark
The initial purpose is for igt tests, but this would also be useful for
compositors that wait until close to vblank deadline to make decisions
about which frame to show.
The igt tests can be found at:
https://gitlab.freedesktop.org/robclark/igt-gpu-tools/-/commits/fence-deadline
From: Rob Clark
Track the nearest deadline on a fence timeline and set a timer to expire
shortly before to trigger boost if the fence has not yet been signaled.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/msm_drv.c | 4 +-
drivers/gpu/drm/msm/msm_fence.c | 74 ++
From: Rob Clark
Add a way for various userspace waits to signal urgency.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/msm_drv.c | 12
drivers/gpu/drm/msm/msm_gem.c | 5 +
include/uapi/drm/msm_drm.h| 14 --
3 files changed, 25 insertions(+), 6 deletions(-)
From: Rob Clark
Signed-off-by: Rob Clark
---
This should probably be re-written by someone who knows the i915
request/timeline stuff better, to deal with non-immediate deadlines.
But as-is I think this should be enough to handle the case where
we want syncobj waits to trigger boost.
drivers/g
From: Rob Clark
Add a new flag to let userspace provide a deadline as a hint for syncobj
and timeline waits. This gives a hint to the driver signaling the
backing fences about how soon userspace needs it to compete work, so it
can addjust GPU frequency accordingly. An immediate deadline can be
https://bugzilla.kernel.org/show_bug.cgi?id=217058
Bug ID: 217058
Summary: amdgpu resets
Product: Drivers
Version: 2.5
Kernel Version: 6.0.x, 6.1.x, 6.2-rcX
Hardware: AMD
OS: Linux
Tree: Mainline
S
41 matches
Mail list logo
