Hi Jagan,
On 14.11.2022 18:07, Jagan Teki wrote:
> On Mon, Nov 14, 2022 at 8:10 PM Marek Szyprowski
> wrote:
>> On 14.11.2022 11:57, Marek Szyprowski wrote:
>>> On 10.11.2022 19:38, Jagan Teki wrote:
Finding the right input bus format throughout the pipeline is hard
so add atomic_get_in
On Sat, Nov 12, 2022 at 07:42:10PM +, Robert Swindells wrote:
> Contributors to these files are:
>
> Noralf Trønnes
> Liu Zixian
Acked-by: Liu Zixian
Hi
Am 12.11.22 um 20:42 schrieb Robert Swindells:
Contributors to these files are:
Noralf Trønnes
Liu Zixian
Dave Airlie
Thomas Zimmermann
Lucas De Marchi
Gerd Hoffmann
Rob Herring
Jakub Kicinski
Marcel Ziswiler
Stephen Rothwell
Daniel Vetter
Cai Huoqing
Neil Roberts
Marek Szyprows
Phy is not being initialized after suspend resume. Fix this by setting
phy_initialized flag to false in suspend callback
Signed-off-by: Rahul T R
---
drivers/gpu/drm/bridge/cdns-dsi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/bridge/cdns-dsi.c
b/drivers/gpu/drm/bridge/
On 15.11.22 09:09, Marek Szyprowski wrote:
> Hi Jagan,
>
> On 14.11.2022 18:07, Jagan Teki wrote:
>> On Mon, Nov 14, 2022 at 8:10 PM Marek Szyprowski
>> wrote:
>>> On 14.11.2022 11:57, Marek Szyprowski wrote:
On 10.11.2022 19:38, Jagan Teki wrote:
> Finding the right input bus format thr
Can you update the commit message so at least the first patch can land
for 6.1 so we can avoid regressions? E.g. something like
It caused logically active but disconnected MST display port connectors to
disappear from the drmModeGetResources() list, meaning userspace is made to
believe the co
I've already pushed both patches to drm-misc-next.
On Mon, 14 Nov 2022 14:00:20 +0100, Maxime Ripard wrote:
> KMS supports a number of named modes already, but it's never been
> documented anywhere, let's fix that.
>
>
Applied to drm/drm-misc (drm-misc-next).
Thanks!
Maxime
On Mon, 14 Nov 2022 14:00:21 +0100, Maxime Ripard wrote:
> As the number of kunit tests in KMS grows further, we start to have
> multiple test suites that, for example, need to register a mock DRM
> driver to interact with the KMS function they are supposed to test.
>
> Let's add a file meant to p
On Mon, 14 Nov 2022 14:00:27 +0100, Maxime Ripard wrote:
> drm_connector_pick_cmdline_mode() is in charge of finding a proper
> drm_display_mode from the definition we got in the video= command line
> argument.
>
> Let's add some unit tests to make sure we're not getting any regressions
> there.
>
On Mon, 14 Nov 2022 14:00:30 +0100, Maxime Ripard wrote:
> The current code to deal with named modes will only set the mode name, and
> then it's up to drivers to try to match that name to whatever mode or
> configuration they see fit.
>
> The plan is to remove that need and move the named mode ha
On Mon, 14 Nov 2022 14:00:31 +0100, Maxime Ripard wrote:
> We'll need to get the pixel clock to generate proper display modes for
> all the current named modes. Let's add it to struct drm_cmdline_mode and
> fill it when parsing the named mode.
>
>
Applied to drm/drm-misc (drm-misc-next).
Thanks
On Mon, 14 Nov 2022 14:00:28 +0100, Maxime Ripard wrote:
> The current construction of the named mode parsing doesn't allow to extend
> it easily. Let's move it to a separate function so we can add more
> parameters and modes.
>
> In order for the tests to still pass, some extra checks are needed,
On Mon, 14 Nov 2022 14:00:29 +0100, Maxime Ripard wrote:
> The current named mode parsing relies only on the mode name, and doesn't
> allow to specify any other parameter.
>
> Let's convert that string list to an array of a custom structure that will
> hold the name and some additional parameters
On Tue, Nov 15, 2022 at 08:55:12AM +, Simon Ser wrote:
> I've already pushed both patches to drm-misc-next.
It's not in any 6.1 rc yet, and apparently it needs to be pushed to
drm-misc-fixes to get into 6.1.
On Tue, Nov 15, 2022 at 2:18 PM Frieder Schrempf
wrote:
>
> On 15.11.22 09:09, Marek Szyprowski wrote:
> > Hi Jagan,
> >
> > On 14.11.2022 18:07, Jagan Teki wrote:
> >> On Mon, Nov 14, 2022 at 8:10 PM Marek Szyprowski
> >> wrote:
> >>> On 14.11.2022 11:57, Marek Szyprowski wrote:
> On 10.11.
On 13.07.2021 15:59, Daniel Vetter wrote:
Some vague evidences suggests this can go wrong. Try to prevent it by
holding the right mutex and clearing ->deferred_setup to make sure we
later on don't accidentally try to re-register the fbdev when the
driver thought it had it all cleaned up already.
On 11/15/22 08:09, shangxiaojing wrote:
On 2022/11/15 15:05, Helge Deller wrote:
On 11/15/22 07:52, shangxiaojing wrote:
On 2022/11/15 13:14, Helge Deller wrote:
On 11/15/22 03:53, Shang XiaoJing wrote:
Due to viafb_exit() with "__exit" tag, it should not be called by the
__init function vi
[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to
On 07.11.2022 09:32, Lucas De Marchi wrote:
> With a lot of sub-section it's a little bit hard to find the information
> needed in the main GPU index. Limit the maxdepth to 2 so it doesn't get
> poluted with noise from each driver and from other sections.
>
> Signed-off-by: Lucas De Marchi
> ---
Hi
Am 11.11.22 um 10:28 schrieb Daniel Vetter:
On Thu, Nov 10, 2022 at 02:55:18PM +0100, Thomas Zimmermann wrote:
Schedule the deferred-I/O worker instead of the damage worker after
writing to the fbdev framebuffer. The deferred-I/O worker then performs
the dirty-fb update. The fbdev emulation
From: Tvrtko Ursulin
Add a missing colon which I accidentally removed in the recent logging
changes.
Signed-off-by: Tvrtko Ursulin
Fixes: a10234fda466 ("drm/i915: Partial abandonment of legacy DRM logging
macros")
Cc: Andrzej Hajda
---
drivers/gpu/drm/i915/i915_vma.c | 2 +-
1 file changed,
On 10/11/2022 10:35, Michal Wajdeczko wrote:
On 10.11.2022 10:55, Tvrtko Ursulin wrote:
On 09/11/2022 19:57, Michal Wajdeczko wrote:
[snip]
Is it really a problem to merge this patch now to get the process
started? And other sub-components get updated as and when people get the
time to do
On 15.11.2022 11:17, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Add a missing colon which I accidentally removed in the recent logging
changes.
Signed-off-by: Tvrtko Ursulin
Fixes: a10234fda466 ("drm/i915: Partial abandonment of legacy DRM logging
macros")
Cc: Andrzej Hajda
Reviewed-by: A
On 13/11/2022 07:57, Niranjana Vishwanathapura wrote:
Asynchronously unbind the vma upon vm_unbind call.
Fall back to synchronous unbind if backend doesn't support
async unbind or if async unbind fails.
No need for vm_unbind out fence support as i915 will internally
handle all sequencing and use
Dependencies:
https://lore.kernel.org/all/20221102231309.583587-1-dmitry.barysh...@linaro.org/
https://lore.kernel.org/all/20221024164225.3236654-1-dmitry.barysh...@linaro.org/
https://lore.kernel.org/all/20221104130324.1024242-5-dmitry.barysh...@linaro.org/
Branch:
https://git.linaro.org/people/r
Mobile Display Subsystem (MDSS) encapsulates sub-blocks
like DPU display controller, DSI etc. Add YAML schema for DPU device
tree bindings
Signed-off-by: Robert Foss
---
.../bindings/display/msm/qcom,sm8350-dpu.yaml | 120 ++
1 file changed, 120 insertions(+)
create mode 100644
Mobile Display Subsystem (MDSS) encapsulates sub-blocks
like DPU display controller, DSI etc. Add YAML schema for MDSS device
tree bindings
Signed-off-by: Robert Foss
---
.../display/msm/qcom,sm8350-mdss.yaml | 240 ++
1 file changed, 240 insertions(+)
create mode 100644
The sc7280_pp declaration is not located by the other _pp
declarations, but rather hidden around the _merge_3d
declarations. Let's fix this to avoid confusion.
Signed-off-by: Robert Foss
Reviewed-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c | 14 +++---
1 file
Add caching when EDID is read, and invalidate the cache until the
bridge detects HPD low or sink count changes on HPD_IRQ.
It takes 1.2s for IT6505 bridge to read a 3-block EDID, and skipping
one EDID read would be a notable difference on user experience.
Signed-off-by: Pin-yen Lin
---
driver
Hi
Am 11.11.22 um 10:42 schrieb Daniel Vetter:
On Thu, Nov 10, 2022 at 02:55:19PM +0100, Thomas Zimmermann wrote:
The fbdev damage worker is unused, so remove it.
Signed-off-by: Thomas Zimmermann
I'd squash this into the previous patch, which gets rid of the
schedule_work(), if you limit th
The fbdev emulation runs a separate worker that collects all changes
to the framebuffer and runs DRM damage handling. But this can also be
performed by the worker of fbdev's deferred-I/O code. Move damage
handling there, remove the damage worker and reduce the latency.
I ran a simple benchmark wit
The helper for processing deferred I/O on pages has no dependency on
the fb_dirty damge-handling callback; so remove the test. In practice,
deferred I/O is only used with damage handling and the damage worker
already guarantees the presence of the fb_dirty callback.
Signed-off-by: Thomas Zimmerman
Schedule the deferred-I/O worker instead of the damage worker after
writing to the fbdev framebuffer. The deferred-I/O worker then performs
the dirty-fb update. The fbdev emulation will initialize deferred I/O
for all drivers that require damage updates. It is therefore a valid
assumption that the
Move the dirty-fb update from the damage-worker callback into the
new helper drm_fb_helper_fb_dirty(), so that it can run outside the
damage worker. This change will help to remove the damage worker
entirely. No functional changes.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Vetter
---
The fbdev damage worker is unused, so remove it.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/drm_fb_helper.c | 9 -
include/drm/drm_fb_helper.h | 2 --
2 files changed, 11 deletions(-)
diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/dr
Set the damage area in the new helper drm_fb_helper_add_damage_clip().
It can now be updated without scheduling the damage worker. This change
will help to remove the damage worker entirely. No functional changes.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/d
Call fb_dirty directly from drm_fb_helper_deferred_io() to avoid the
latency of running the damage worker.
The deferred-I/O helper drm_fb_helper_deferred_io() runs in a worker
thread at regular intervals as part of writing to mmaped framebuffer
memory. It used to schedule the fbdev damage worker t
On 11/14/22 08:49, Jagan Teki wrote:
On Sun, Nov 13, 2022 at 5:51 AM Marek Vasut wrote:
On 11/10/22 19:38, Jagan Teki wrote:
Finding the right input bus format throughout the pipeline is hard
so add atomic_get_input_bus_fmts callback and initialize with the
proper input format from list of su
On 09/11/2022 15:18, luca.ceres...@bootlin.com wrote:
> From: Luca Ceresoli
>
> VIP is the parallel video capture component within the video input
> subsystem of Tegra20 (and other Tegra chips, apparently).
Subject: drop second, redundant "bindings".
>
> Signed-off-by: Luca Ceresoli
> ---
>
On 09/11/2022 15:18, luca.ceres...@bootlin.com wrote:
> From: Luca Ceresoli
>
> The Tegra20 VI peripheral can receive parallel input from the VIP parallel
> input module. Add it to the allowed properties and augment the existing
> nvidia,tegra20-vi example to show a 'vip' property.
>
> Signed-of
On 09/11/2022 15:18, luca.ceres...@bootlin.com wrote:
> From: Luca Ceresoli
>
> Useful to enable it from a board DTS.
>
No, it does not make sense. Adding unused labels is not useful. This
must come with an user.
Best regards,
Krzysztof
On 09/11/2022 15:18, luca.ceres...@bootlin.com wrote:
> From: Luca Ceresoli
>
> Useful to enable it from a board DTS.
>
> Signed-off-by: Luca Ceresoli
Adding unused labels is not useful at all.
Best regards,
Krzysztof
In the PP_OD_EDIT_VDDC_CURVE case the "input_index" variable is capped at
2 but not checked for negative values so it results in an out of bounds
read. This value comes from the user via sysfs.
Fixes: d5bf26539494 ("drm/amd/powerplay: added vega20 overdrive support V3")
Signed-off-by: Dan Carpent
This code was refactored in commit 69a88d8633ec ("drm/msm/hdmi: move
resource allocation to probe function") and now the "hdmi" pointer can't
be NULL. Checking causes a Smatch warning:
drivers/gpu/drm/msm/hdmi/hdmi.c:141 msm_hdmi_init()
warn: variable dereferenced before check 'hdmi' (see
All six callers expect error pointers instead of NULL so make the
nvkm_runl_new() return error pointers as expected.
Fixes: d94470e9d150 ("drm/nouveau/fifo: add common runlist/engine topology")
Signed-off-by: Dan Carpenter
---
drivers/gpu/drm/nouveau/nvkm/engine/fifo/runl.c | 4 ++--
1 file chan
The "&chan->cgrp->mutex" and "&cgrp->mutex" variables refer to the same
thing. Use "&cgrp->mutex" consistently.
Signed-off-by: Dan Carpenter
---
drivers/gpu/drm/nouveau/nvkm/engine/fifo/chan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nvkm/engin
Drop the "gr->fecs.mutex" lock before returning on this error path.
Fixes: ca081fff6ecc ("drm/nouveau/gr/gf100-: generate golden context during
first object alloc")
Signed-off-by: Dan Carpenter
---
drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Hi Sebastian
Thanks for starting the conversation - it's stalled a number of times
previously.
On Mon, 14 Nov 2022 at 23:12, Sebastian Wick wrote:
>
> There are still regular bug reports about monitors (sinks) and sources
> disagreeing about the quantization range of the pixel data. In
> particu
On 2022/11/12, Robert Swindells wrote:
> Contributors to these files are:
>
> Noralf Trønnes
> Liu Zixian
> Dave Airlie
> Thomas Zimmermann
> Lucas De Marchi
> Gerd Hoffmann
> Rob Herring
> Jakub Kicinski
> Marcel Ziswiler
> Stephen Rothwell
> Daniel Vetter
> Cai Huoqing
> Neil Roberts
On Mon 2022-11-14 20:57:18, John Ogness wrote:
> Hi,
>
> After more detailed runtime testing I discovered that I didn't re-insert
> the console to the correct place in the list. More below...
>
> > --- a/kernel/printk/printk.c
> > +++ b/kernel/printk/printk.c
> > @@ -3461,6 +3462,48 @@ int unregi
On 08/11/2022 14:00, Sandor Yu wrote:
> Add bindings for i.MX8MQ MHDP HDMI.
>
> Signed-off-by: Sandor Yu
> ---
> .../display/bridge/cdns,mhdp-imx8mq-hdmi.yaml | 59 +++
> 1 file changed, 59 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/display/bridge/cd
On 15/11/2022 12:17, Robert Foss wrote:
Dependencies:
https://lore.kernel.org/all/20221102231309.583587-1-dmitry.barysh...@linaro.org/
https://lore.kernel.org/all/20221024164225.3236654-1-dmitry.barysh...@linaro.org/
https://lore.kernel.org/all/20221104130324.1024242-5-dmitry.barysh...@linaro.
On 08/11/2022 14:00, Sandor Yu wrote:
> Add bindings for Cadence HDP-TX DisplayPort PHY.
>
> Signed-off-by: Sandor Yu
> ---
> .../bindings/phy/cdns,hdptx-dp-phy.yaml | 66 +++
> 1 file changed, 66 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/phy/
On 08/11/2022 14:00, Sandor Yu wrote:
> Add bindings for Cadence HDP-TX HDMI PHY.
>
> Signed-off-by: Sandor Yu
> ---
> .../bindings/phy/cdns,hdptx-hdmi-phy.yaml | 50 +++
> 1 file changed, 50 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/phy/cdns,hd
On 08/11/2022 14:50, Sandor Yu wrote:
> Run get_maintainer.pl for patch 1,
> Your email address is list as follow,
> Jani Nikula (commit_signer:2/8=25%)
>
> And I add the email address that comment as "commit_signer" into Cc list.
That's not a maintainer entry, but contributor. No need to Cc oc
Dependencies:
https://lore.kernel.org/all/20221102231309.583587-1-dmitry.barysh...@linaro.org/
https://lore.kernel.org/all/20221024164225.3236654-1-dmitry.barysh...@linaro.org/
https://lore.kernel.org/all/20221104130324.1024242-5-dmitry.barysh...@linaro.org/
Branch:
https://git.linaro.org/people/r
Mobile Display Subsystem (MDSS) encapsulates sub-blocks
like DPU display controller, DSI etc. Add YAML schema for DPU device
tree bindings
Signed-off-by: Robert Foss
---
.../bindings/display/msm/qcom,sm8350-dpu.yaml | 120 ++
1 file changed, 120 insertions(+)
create mode 100644
Add compatibles string, "qcom,sm8350-mdss", for the multimedia display
subsystem unit used on Qualcomm SM8350 platform.
Signed-off-by: Robert Foss
---
drivers/gpu/drm/msm/msm_mdss.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/msm/msm_mdss.c b/drivers/gpu/drm/msm/msm_m
The sc7280_pp declaration is not located by the other _pp
declarations, but rather hidden around the _merge_3d
declarations. Let's fix this to avoid confusion.
Signed-off-by: Robert Foss
Reviewed-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c | 14 +++---
1 file
Mobile Display Subsystem (MDSS) encapsulates sub-blocks
like DPU display controller, DSI etc. Add YAML schema for MDSS device
tree bindings
Signed-off-by: Robert Foss
---
.../display/msm/qcom,sm8350-mdss.yaml | 240 ++
1 file changed, 240 insertions(+)
create mode 100644
Add compatibility for SM8350 display subsystem, including
required entries in DPU hw catalog.
Signed-off-by: Robert Foss
---
.../gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c| 196 ++
.../gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h| 1 +
2 files changed, 197 insertions(+)
diff --g
Add GPIO line names as described by the sm8350-hdk schematic.
Signed-off-by: Robert Foss
---
arch/arm64/boot/dts/qcom/sm8350-hdk.dts | 205
1 file changed, 205 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm8350-hdk.dts
b/arch/arm64/boot/dts/qcom/sm8350-hdk.dts
Add compatibles string, "qcom,sm8350-dpu", for the display processing unit
used on Qualcomm SM8350 platform.
Signed-off-by: Robert Foss
---
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
b/drivers/gpu/drm/msm/d
The mmxc power-domain-name is not required, and is not
used by either earlier or later SoC versions (sm8250 / sm8450).
Signed-off-by: Robert Foss
---
arch/arm64/boot/dts/qcom/sm8350.dtsi | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/sm8350.dtsi
b/arch/arm64/boot/dt
Add mdss, mdss_mdp, dsi0, dsi0_phy nodes. With these
nodes the display subsystem is configured to support
one DSI output.
Signed-off-by: Robert Foss
---
arch/arm64/boot/dts/qcom/sm8350.dtsi | 197 ++-
1 file changed, 193 insertions(+), 4 deletions(-)
diff --git a/arch/ar
The sm8350-hdk ships with the LT9611 UXC DSI/HDMI bridge chip.
In order to toggle the board to enable the HDMI output,
switch #7 & #8 on the rightmost multi-switch package have
to be toggled to On.
Signed-off-by: Robert Foss
---
arch/arm64/boot/dts/qcom/sm8350-hdk.dts | 105
Enable the display subsystem and the dsi0 output for
the sm8350-hdk board.
Signed-off-by: Robert Foss
---
arch/arm64/boot/dts/qcom/sm8350-hdk.dts | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm8350-hdk.dts
b/arch/arm64/boot/dts/qcom/sm8350
Use two interconnect cells in order to optionally
support a path tag.
Signed-off-by: Robert Foss
---
arch/arm64/boot/dts/qcom/sm8350.dtsi | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sm8350.dtsi
b/arch/arm64/boot/dts
On 15/11/2022 14:30, Robert Foss wrote:
The sc7280_pp declaration is not located by the other _pp
declarations, but rather hidden around the _merge_3d
declarations. Let's fix this to avoid confusion.
Signed-off-by: Robert Foss
Reviewed-by: Dmitry Baryshkov
---
This is already merged.
http
On 15/11/2022 14:30, Robert Foss wrote:
Add compatibility for SM8350 display subsystem, including
required entries in DPU hw catalog.
Signed-off-by: Robert Foss
---
.../gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c| 196 ++
.../gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h| 1
This series includes code change to enable idle messaging for GSC CS.
v2:
- Dropped dependency patch and rebased
- Fixed review comments
Cc: Vinay Belgaumkar
Vinay Belgaumkar (1):
drm/i915/mtl: Enable Idle Messaging for GSC CS
drivers/gpu/drm/i915/gt/intel_engine_pm.c | 18 +++
From: Vinay Belgaumkar
By defaut idle mesaging is disabled for GSC CS so to unblock RC6
entry on media tile idle messaging need to be enabled.
v2:
- Fix review comments (Vinay)
- Set GSC idle hysterisis to 5 us (Badal)
Bspec: 71496
Cc: Daniele Ceraolo Spurio
Signed-off-by: Vinay Belgaumkar
On 15/11/2022 14:30, Robert Foss wrote:
Add compatibles string, "qcom,sm8350-mdss", for the multimedia display
subsystem unit used on Qualcomm SM8350 platform.
Signed-off-by: Robert Foss
---
drivers/gpu/drm/msm/msm_mdss.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu
On 15/11/2022 14:31, Robert Foss wrote:
The mmxc power-domain-name is not required, and is not
used by either earlier or later SoC versions (sm8250 / sm8450).
Signed-off-by: Robert Foss
---
Reviewed-by: Konrad Dybcio
Konrad
arch/arm64/boot/dts/qcom/sm8350.dtsi | 1 -
1 file changed, 1
On 15/11/2022 14:31, Robert Foss wrote:
Use two interconnect cells in order to optionally
support a path tag.
Signed-off-by: Robert Foss
---
Reviewed-by: Konrad Dybcio
Konrad
arch/arm64/boot/dts/qcom/sm8350.dtsi | 28 ++--
1 file changed, 14 insertions(+), 14 d
On 15/11/2022 14:31, Robert Foss wrote:
Add mdss, mdss_mdp, dsi0, dsi0_phy nodes. With these
nodes the display subsystem is configured to support
one DSI output.
Signed-off-by: Robert Foss
---
arch/arm64/boot/dts/qcom/sm8350.dtsi | 197 ++-
1 file changed, 193 inse
On Tue, 15 Nov 2022 12:17:10 +0100, Robert Foss wrote:
> Mobile Display Subsystem (MDSS) encapsulates sub-blocks
> like DPU display controller, DSI etc. Add YAML schema for DPU device
> tree bindings
>
> Signed-off-by: Robert Foss
> ---
> .../bindings/display/msm/qcom,sm8350-dpu.yaml | 120 +++
On Tue, 15 Nov 2022 12:17:11 +0100, Robert Foss wrote:
> Mobile Display Subsystem (MDSS) encapsulates sub-blocks
> like DPU display controller, DSI etc. Add YAML schema for MDSS device
> tree bindings
>
> Signed-off-by: Robert Foss
> ---
> .../display/msm/qcom,sm8350-mdss.yaml | 240 ++
Hi Dmitry
On Sun, 13 Nov 2022 at 13:06, Dmitry Baryshkov
wrote:
>
> Hi Dave,
>
> On 19/07/2022 16:45, Dave Stevenson wrote:
> > Hi Sam
> >
> > On Mon, 18 Jul 2022 at 21:52, Sam Ravnborg wrote:
> >>
> >> Hi Dave,
> >>
> >> a long overdue reply on this series.
> >>
> >> On Fri, Mar 04, 2022 at 03:
On 15/11/2022 17:14, Dave Stevenson wrote:
Hi Dmitry
On Sun, 13 Nov 2022 at 13:06, Dmitry Baryshkov
wrote:
Hi Dave,
On 19/07/2022 16:45, Dave Stevenson wrote:
Hi Sam
On Mon, 18 Jul 2022 at 21:52, Sam Ravnborg wrote:
Hi Dave,
a long overdue reply on this series.
On Fri, Mar 04, 2022 at
Applied. Thanks.
Alex
On Sun, Nov 13, 2022 at 2:44 AM Paulo Miguel Almeida
wrote:
>
> One-element arrays are deprecated, and we are replacing them with
> flexible array members instead. So, replace one-element array with
> flexible-array member in structs ATOM_I2C_VOLTAGE_OBJECT_V3,
> ATOM_ASIC
Hi Dmitry
On Tue, 15 Nov 2022 at 14:21, Dmitry Baryshkov
wrote:
>
> On 15/11/2022 17:14, Dave Stevenson wrote:
> > Hi Dmitry
> >
> > On Sun, 13 Nov 2022 at 13:06, Dmitry Baryshkov
> > wrote:
> >>
> >> Hi Dave,
> >>
> >> On 19/07/2022 16:45, Dave Stevenson wrote:
> >>> Hi Sam
> >>>
> >>> On Mon,
A comma is missing, fix it.
Signed-off-by: Janusz Krzysztofik
---
drivers/gpu/drm/i915/i915_vma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_vma.c b/drivers/gpu/drm/i915/i915_vma.c
index 3b969d679c1e2..947fde68e5f53 100644
--- a/drivers/gpu/drm/
Applied. Thanks!
Alex
On Tue, Nov 15, 2022 at 7:57 AM Dan Carpenter wrote:
>
> In the PP_OD_EDIT_VDDC_CURVE case the "input_index" variable is capped at
> 2 but not checked for negative values so it results in an out of bounds
> read. This value comes from the user via sysfs.
>
> Fixes: d5bf26
On 15/11/2022 14:39, Janusz Krzysztofik wrote:
A comma is missing, fix it.
Signed-off-by: Janusz Krzysztofik
---
drivers/gpu/drm/i915/i915_vma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_vma.c b/drivers/gpu/drm/i915/i915_vma.c
index 3b969
On XE_LPM+ platforms the media engines are carved out into a separate
GT but have a common GGTMMADR address range which essentially makes
the GGTT address space to be shared between media and render GT. As a
result any updates in GGTT shall invalidate TLB of GTs sharing it and
similarly any operati
On 15/11/2022 14:30, Robert Foss wrote:
> Dependencies:
> https://lore.kernel.org/all/20221102231309.583587-1-dmitry.barysh...@linaro.org/
> https://lore.kernel.org/all/20221024164225.3236654-1-dmitry.barysh...@linaro.org/
> https://lore.kernel.org/all/20221104130324.1024242-5-dmitry.barysh...@lina
On Tue, Nov 15, 2022 at 07:14:40PM +0530, Badal Nilawar wrote:
> From: Vinay Belgaumkar
>
> By defaut idle mesaging is disabled for GSC CS so to unblock RC6
> entry on media tile idle messaging need to be enabled.
>
> v2:
> - Fix review comments (Vinay)
> - Set GSC idle hysterisis to 5 us (Bad
On Tue, 15 Nov 2022, "Jiri Slaby (SUSE)" wrote:
> The last user of macros from that include was removed in 2018 by the
> commit below.
>
> Fixes: 6cc42152b02b ("drm/i915: Remove support for legacy debugfs crc
> interface")
> Cc: Jani Nikula
> Cc: Joonas Lahtinen
> Cc: Rodrigo Vivi
> Cc: Tvrtko
From: Rob Clark
If we get an error (other than -ENOENT) we need to propagate that up the
stack. Otherwise if the nvmem driver hasn't probed yet, we'll end up
end up claiming that we support all the OPPs which is not likely to be
true (and on some generations impossible to be true, ie. if there a
On Mon, 14 Nov 2022, Andy Shevchenko wrote:
> Some of the existing users, and definitely will be new ones, want to
> count existing nodes in the list. Provide a generic API for that by
> moving code from i915 to list.h.
I think I'd find list_length() a much more natural name for this.
*shrug*
A
From: Rob Clark
This was overlooked.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/msm/adreno/a6xx_gpu.c
b/drivers/gpu/drm/msm/adreno/a6xx_gpu.c
index ebe9599a8316..e495d8e1
Hi Niranjana,
On Sat, Nov 12, 2022 at 11:57:32PM -0800, Niranjana Vishwanathapura wrote:
> Asynchronously unbind the vma upon vm_unbind call.
> Fall back to synchronous unbind if backend doesn't support
> async unbind or if async unbind fails.
>
> No need for vm_unbind out fence support as i915 w
Hi,
On Tue, Nov 15, 2022 at 7:55 AM Rob Clark wrote:
>
> From: Rob Clark
>
> This was overlooked.
>
> Signed-off-by: Rob Clark
> ---
> drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 14 +++---
> 1 file changed, 7 insertions(+), 7 deletions(-)
Reviewed-by: Douglas Anderson
On Tue, Nov 15, 2022 at 11:05:21AM +, Matthew Auld wrote:
On 13/11/2022 07:57, Niranjana Vishwanathapura wrote:
Asynchronously unbind the vma upon vm_unbind call.
Fall back to synchronous unbind if backend doesn't support
async unbind or if async unbind fails.
No need for vm_unbind out fenc
On Tue, Nov 15, 2022 at 04:58:42PM +0100, Andi Shyti wrote:
Hi Niranjana,
On Sat, Nov 12, 2022 at 11:57:32PM -0800, Niranjana Vishwanathapura wrote:
Asynchronously unbind the vma upon vm_unbind call.
Fall back to synchronous unbind if backend doesn't support
async unbind or if async unbind fail
On 15/11/2022 16:15, Niranjana Vishwanathapura wrote:
On Tue, Nov 15, 2022 at 11:05:21AM +, Matthew Auld wrote:
On 13/11/2022 07:57, Niranjana Vishwanathapura wrote:
Asynchronously unbind the vma upon vm_unbind call.
Fall back to synchronous unbind if backend doesn't support
async unbind or
Hello Sebastian,
I've previously done some work on this topic [1]. My efforts were mostly about
fixing the situation regarding overrides and providing proper means for
userspace. I am affected by the issue myself as I own several DELL U2414H
screens that declare a CE mode as their preferred one
On 15/11/2022 10:46, Andrzej Hajda wrote:
On 15.11.2022 11:17, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Add a missing colon which I accidentally removed in the recent logging
changes.
Signed-off-by: Tvrtko Ursulin
Fixes: a10234fda466 ("drm/i915: Partial abandonment of legacy DRM
logging
1 - 100 of 137 matches
Mail list logo
