On 04/04/2023 12:47, AngeloGioacchino Del Regno wrote:
Since eDP panels are not removable it is safe to cache the EDID:
this will avoid a relatively long read transaction at every PM
resume that is unnecessary only in the "special" case of eDP,
hence speeding it up a little, as from now on, as
On Wed Apr 5, 2023 at 5:03 PM CEST, Maxime Ripard wrote:
> On Wed, Apr 05, 2023 at 02:34:11PM +0200, Roman Beranek wrote:
> > It turns out however that the new dclk rates can't be set exactly as
> > requested without touching pll-video0*, tcon0 now therefore gets
> > reparented from pll-mipi to pll
On 2023-04-11 16:45:34, Abhinav Kumar wrote:
[..]
> > Does this flush all DSCs programmed in CTL_DSC_FLUSH as set above? That
> > is currently still in `if (cfg->dsc)` and never overwritten if all DSCs
> > are disabled, should it be taken out of the `if` to make sure no DSCs
> > are inadvertently
On 2023-04-11 18:50:24, Abhinav Kumar wrote:
>
>
> On 4/11/2023 6:06 PM, Dmitry Baryshkov wrote:
> > On 12/04/2023 01:32, Abhinav Kumar wrote:
> >> Hi Marijn
> >>
> >> On 4/11/2023 3:24 PM, Marijn Suijten wrote:
> >>> Again, don't forget to include previous reviewers in cc, please :)
> >>>
> >>>
We may not have dsi->dsidev initialized during probe, and that can
lead into various dsi related warnings as omap_dsi_host_detach() gets
called with dsi->dsidev set to NULL.
The warnings can be "Fixed dependency cycle(s)" followed by a
WARNING: CPU: 0 PID: 787 at drivers/gpu/drm/omapdrm/dss/dsi.c:
On Tue, Apr 11, 2023 at 7:44 AM Geert Uytterhoeven
wrote:
>
> Fix a misspelling of "rendez-vouz".
>
> Signed-off-by: Geert Uytterhoeven
> ---
> include/drm/task_barrier.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/drm/task_barrier.h b/include/drm/task_barrie
On Tue, Apr 11, 2023 at 03:56:06PM -0700, Rob Clark wrote:
> From: Rob Clark
>
> Handle a bit of the boiler-plate in a single case, and make it easier to
> add some core tracked stats.
>
> Signed-off-by: Rob Clark
Thanks a lot for kicking this off. A few polish comments below, with those
addre
On Tue, Apr 11, 2023 at 03:56:08PM -0700, Rob Clark wrote:
> From: Rob Clark
>
> Signed-off-by: Rob Clark
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c| 3 ++-
> drivers/gpu/drm/amd/amdgpu/amdgpu_fdinfo.c | 16 ++--
> drivers/gpu/drm/amd/amdgpu/amdgpu_fdinfo.h | 2 +-
> 3 fi
On Tue, Apr 11, 2023 at 03:56:10PM -0700, Rob Clark wrote:
> From: Rob Clark
>
> Signed-off-by: Rob Clark
You're on an old tree, this got reverted. But I'm kinda wondering whether
another patch on top shouldn't just includ the drm_show_fdinfo in
DRM_GEM_FOPS macro ... There's really no good rea
On Tue, Apr 11, 2023 at 03:56:11PM -0700, Rob Clark wrote:
> From: Rob Clark
>
> Add support to dump GEM stats to fdinfo.
>
> v2: Fix typos, change size units to match docs, use div_u64
> v3: Do it in core
>
> Signed-off-by: Rob Clark
> Reviewed-by: Emil Velikov
> ---
> Documentation/gpu/drm
Il 12/04/23 09:08, Matthias Brugger ha scritto:
On 04/04/2023 12:47, AngeloGioacchino Del Regno wrote:
Since eDP panels are not removable it is safe to cache the EDID:
this will avoid a relatively long read transaction at every PM
resume that is unnecessary only in the "special" case of eDP,
h
Otherwise core changes don't get noticed by the right people. I
noticed this because a patch set from Jagan Teki seems to have fallen
through the cracks.
Signed-off-by: Daniel Vetter
Cc: Jagan Teki
Cc: Andrzej Hajda
Cc: Neil Armstrong
Cc: Robert Foss
Cc: Laurent Pinchart
Cc: Jonas Karlman
C
On Wed, Apr 12, 2023 at 01:36:52AM +0300, Dmitry Baryshkov wrote:
> On 11/04/2023 21:28, Rob Clark wrote:
> > On Tue, Apr 11, 2023 at 10:36 AM Dmitry Baryshkov
> > wrote:
> > >
> > > On Tue, 11 Apr 2023 at 20:13, Rob Clark wrote:
> > > >
> > > > On Tue, Apr 11, 2023 at 9:53 AM Daniel Vetter wr
On Wed, Apr 12, 2023 at 02:47:52PM +0900, Asahi Lina wrote:
> On 11/04/2023 23.07, Daniel Vetter wrote:
> > On Sat, Apr 08, 2023 at 04:05:20PM +0900, Asahi Lina wrote:
> > > On 04/04/2023 10.58, Matthew Brost wrote:
> > > > On Tue, Apr 04, 2023 at 10:07:48AM +0900, Asahi Lina wrote:
> > > > > Hi, t
Hi Daniel,
Thank you for the patch.
On Wed, Apr 12, 2023 at 10:09:20AM +0200, Daniel Vetter wrote:
> Otherwise core changes don't get noticed by the right people. I
> noticed this because a patch set from Jagan Teki seems to have fallen
> through the cracks.
>
> Signed-off-by: Daniel Vetter
> C
From: Imre Deak
commit e761cc20946a0094df71cb31a565a6a0d03bd8be upstream.
Atm, drm_dp_remove_payload() uses the same payload state to both get the
vc_start_slot required for the payload removal DPCD message and to
deduct time_slots from vc_start_slot of all payloads after the one being
removed.
On Thu, Apr 06, 2023 at 06:57:34PM +0200, Daniel Vetter wrote:
> On Fri, Mar 31, 2023 at 01:36:02PM +0200, Stanislaw Gruszka wrote:
> > From: Karol Wachowski
> >
> > Currently job->done_fence is added to every BO handle within a job. If job
> > handle (command buffer) is shared between multiple s
Hi Tony,
Thank you for the patch.
On Wed, Apr 12, 2023 at 10:39:53AM +0300, Tony Lindgren wrote:
> We may not have dsi->dsidev initialized during probe, and that can
> lead into various dsi related warnings as omap_dsi_host_detach() gets
> called with dsi->dsidev set to NULL.
>
> The warnings ca
On 12/04/2023 11:50, Laurent Pinchart wrote:
Hi Tony,
Thank you for the patch.
On Wed, Apr 12, 2023 at 10:39:53AM +0300, Tony Lindgren wrote:
We may not have dsi->dsidev initialized during probe, and that can
lead into various dsi related warnings as omap_dsi_host_detach() gets
called with dsi
On Wed, Apr 12, 2023 at 11:55:34AM +0300, Tomi Valkeinen wrote:
> On 12/04/2023 11:50, Laurent Pinchart wrote:
> > Hi Tony,
> >
> > Thank you for the patch.
> >
> > On Wed, Apr 12, 2023 at 10:39:53AM +0300, Tony Lindgren wrote:
> >> We may not have dsi->dsidev initialized during probe, and that c
> Am 12.04.2023 um 10:50 schrieb Laurent Pinchart
> :
>
> Hi Tony,
>
> Thank you for the patch.
>
> On Wed, Apr 12, 2023 at 10:39:53AM +0300, Tony Lindgren wrote:
>> We may not have dsi->dsidev initialized during probe, and that can
>> lead into various dsi related warnings as omap_dsi_host_d
On Tue, 11 Apr 2023 at 15:45, Daniel Vetter wrote:
>
> On Tue, Apr 11, 2023 at 02:11:18PM +0200, Christian König wrote:
> > Am 11.04.23 um 11:51 schrieb Daniel Vetter:
> > > On Tue, Apr 04, 2023 at 10:06:49PM +0200, Thomas Hellström wrote:
> > > > When swapping out, we will split multi-order pages
Hello Hans,
On Fri, 7 Apr 2023 15:38:32 +0200
Luca Ceresoli wrote:
> New in v5: dropped the patch that was removing lots of the logic behind
> enum_format, after discussion with Hans. The rest is unmodified except for
> rebasing and fixing a couple typos in comments.
>
> Full details follow.
>
On 12/04/2023 11:16, Luca Ceresoli wrote:
> Hello Hans,
>
> On Fri, 7 Apr 2023 15:38:32 +0200
> Luca Ceresoli wrote:
>
>> New in v5: dropped the patch that was removing lots of the logic behind
>> enum_format, after discussion with Hans. The rest is unmodified except for
>> rebasing and fixing
On Wed, 12 Apr 2023, Rui Salvaterra wrote:
> Hi, everyone,
>
> I apologise in advance if I've sent this to {too many, the wrong}
> people. For some time now, I've been getting sporadic (in about one
> out of five boots) DRM-related RCU complaints on an Ivy Bridge-based
> (Core i7-3720QM) Mac Mini.
Am 12.04.23 um 00:56 schrieb Rob Clark:
From: Rob Clark
Similar motivation to other similar recent attempt[1]. But with an
attempt to have some shared code for this. As well as documentation.
It is probably a bit UMA-centric, I guess devices with VRAM might want
some placement stats as well.
Hi Jason,
Can you give me the based git tree/branch for this series please ?
I want to do a non-regression test for mt8365-evk board.
Feedback below:
On 05/04/2023 16:51, Jason-JH.Lin wrote:
1. Move output drm connector from each ddp_path array to connector array.
2. Add dynamic select availab
On Wed, 12 Apr 2023 10:15:29 +0100 Rui Salvaterra
> Hi, everyone,
>
> I apologise in advance if I've sent this to {too many, the wrong}
> people. For some time now, I've been getting sporadic (in about one
> out of five boots) DRM-related RCU complaints on an Ivy Bridge-based
> (Core i7-3720QM) M
On Thu, Apr 6, 2023 at 8:59 PM Daniel Vetter wrote:
>
> On Thu, Apr 06, 2023 at 10:57:48AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:4b0f4525dc4f Add linux-next specific files for 20230331
> > git tree: linux-next
> > console output:
On 12/04/2023 10:06, AngeloGioacchino Del Regno wrote:
Il 12/04/23 09:08, Matthias Brugger ha scritto:
On 04/04/2023 12:47, AngeloGioacchino Del Regno wrote:
Since eDP panels are not removable it is safe to cache the EDID:
this will avoid a relatively long read transaction at every PM
resu
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any
issue:
Reported-and-tested-by: syzbot+75cc0f9f7e6324dd2...@syzkaller.appspotmail.com
Tested on:
commit: 7d8214bb Add linux-next specific files for 20230412
git tree: linux-next
console output
t trigger any
> issue:
>
> Reported-and-tested-by: syzbot+75cc0f9f7e6324dd2...@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: 7d8214bb Add linux-next specific files for 20230412
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x
Hi Rodrigo,
> > > Currently, when we perform operations such as clearing or copying
> > > large blocks of memory, we generate multiple requests that are
> > > executed in a chain.
> > >
> > > However, if one of these requests fails, we may not realize it
> > > unless it happens to be the last req
On Wed, Apr 12, 2023 at 11:17:22AM +0700, Bagas Sanjaya wrote:
> From gitlab issue above, I don't see any progress on bisection attempt.
> Ammar, have you successfully boot Ubuntu 20.04 with v5.10 kernel and
> test there?
I am still using Ubuntu 22.04. Haven't tried 20.04. I'll arrange time
for it
On 12.04.2023 10:09, Daniel Vetter wrote:
Otherwise core changes don't get noticed by the right people. I
noticed this because a patch set from Jagan Teki seems to have fallen
through the cracks.
Signed-off-by: Daniel Vetter
Cc: Jagan Teki
Cc: Andrzej Hajda
Cc: Neil Armstrong
Cc: Robert F
On 12/04/2023 08:46, Yang Li wrote:
Remove variable 'res' and convert platform_get_resource(),
devm_ioremap_resource() to a single call to
devm_platform_ioremap_resource(), as this is exactly what this function
does.
Signed-off-by: Yang Li
Reviewed-by: Matthias Brugger
---
drivers/gpu
On 12/04/2023 08:46, Yang Li wrote:
Remove variable 'res' and convert platform_get_resource(),
devm_ioremap_resource() to a single call to
devm_platform_ioremap_resource(), as this is exactly what this function
does.
Signed-off-by: Yang Li
Reviewed-by: Matthias Brugger
---
drivers/gpu
On 12/04/2023 08:46, Yang Li wrote:
Remove variable 'res' and convert platform_get_resource(),
devm_ioremap_resource() to a single call to
devm_platform_ioremap_resource(), as this is exactly what this function
does.
Signed-off-by: Yang Li
Reviewed-by: Matthias Brugger
---
drivers/gpu
"Pierre Asselin" writes:
>> Can you please share you grub config file? It seems that is set to
>> GRUB_GFXMODE=1024x768x32 but the actual mode is set to 1024x768x24 ?
>
> Okay, but you'll be sorry... The gfxmode is set to "keep" in all the
> entries. https://www.panix.com/~pa/linux-6.3-simplefb
In this series I'm adding support for the DDC (display) block found
in the MediaTek Helio X10, the MT6331 PMIC and its peripherals, and
eMMC, MicroSD slot and SDIO.
Support for the PMIC (...regulators!) is essential to get all of the
mtk-sd hardware to work, especially the eMMC where vol switching
Add a compatible string for the MediaTek Helio X10 MT6795 SoC, using
the same parameters as MT8183.
Signed-off-by: AngeloGioacchino Del Regno
---
.../display/mediatek/mediatek,dpi.yaml| 23 +++
1 file changed, 14 insertions(+), 9 deletions(-)
diff --git
a/Documentation
Add a compatible string for MediaTek Helio X10 MT6795: this SoC uses
the same DSI PHY as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/ph
Add a compatible string for MediaTek Helio X10 MT6795, using the same
DSI block as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../display/mediatek/mediatek,dsi.yaml| 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git
a/Documentation/devicetr
Add a compatible string for MediaTek Helio X10 MT6795's display PWM
block: this is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
Documentation/devicetree/bindings/pwm/mediatek,pwm-disp.yaml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/
Add a compatible string for MediaTek Helio X10 MT6795's WDMA block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,wdma.yaml| 3 +++
1 file changed, 3 insertions(+)
diff --git
a/Documentation/devicetree/bindings/
Add a compatible string for MediaTek Helio X10 MT6795: similarly to
MT8173, this SoC has the gamma LUT registers in DISP_AAL.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,aal.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
a/Docum
Add a compatible string for MediaTek Helio X10 MT6795's GAMMA block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,gamma.yaml | 4
1 file changed, 4 insertions(+)
diff --git
a/Documentation/devicetree/bindings
Add a compatible string for MediaTek Helio X10 MT6795's RDMA block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,rdma.yaml | 4
1 file changed, 4 insertions(+)
diff --git
a/Documentation/devicetree/bindings/
Add a compatible string for MediaTek Helio X10 MT6795's COLOR block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,color.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
a/Documentation/devicetree/bindings/
Add a compatible string for MediaTek Helio X10 MT6795's OVL block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,ovl.yaml| 4
1 file changed, 4 insertions(+)
diff --git
a/Documentation/devicetree/bindings/d
Add a compatible string for MediaTek Helio X10 MT6795's MERGE block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,merge.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git
a/Documentation/devicetree/bindings
Add a compatible string for MediaTek Helio X10 MT6795's SPLIT block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,split.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git
a/Documentation/devicetree/bindings
Add a compatible string for MediaTek Helio X10 MT6795's UFOE block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,ufoe.yaml| 3 +++
1 file changed, 3 insertions(+)
diff --git
a/Documentation/devicetree/bindings/
Add a compatible string for MediaTek Helio X10 MT6795's OverDrive (OD)
block: this is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,od.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git
a/Documentation/devicetree
Add a compatible string for the MT6795 Helio X10 SoC using MT8173
binding and add a header for the MT6795's GCE mailbox.
Signed-off-by: AngeloGioacchino Del Regno
Reviewed-by: Krzysztof Kozlowski
---
.../mailbox/mediatek,gce-mailbox.yaml | 20 +--
include/dt-bindings/gce/mediatek,mt67
Introduce all nodes for all of the display blocks in the MediaTek Helio
X10 MT6795 SoC, including the DSI PHY and DSI/DPI interfaces: those are
left disabled as usage is board specific.
Signed-off-by: AngeloGioacchino Del Regno
---
arch/arm64/boot/dts/mediatek/mt6795.dtsi | 249
I have added more than 800 lines to this devicetree: adding myself to
the copyright header.
Signed-off-by: AngeloGioacchino Del Regno
---
arch/arm64/boot/dts/mediatek/mt6795.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt6795.dtsi
b/arch/arm64/boot/d
Add the pwrap node: this is used to communicate with the PMIC(s).
Signed-off-by: AngeloGioacchino Del Regno
---
arch/arm64/boot/dts/mediatek/mt6795.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt6795.dtsi
b/arch/arm64/boot/dts/mediatek/mt67
The PWM at 0x11006000 is the tertiary PWM; unlike PWM0, PWM1, this is
not display specific and can be used as a generic PWM controller.
This node is left disabled as usage is board-specific.
Signed-off-by: AngeloGioacchino Del Regno
---
arch/arm64/boot/dts/mediatek/mt6795.dtsi | 19 +++
In preparation for adding multimedia blocks, add the CMDQ/GCE mailbox.
Signed-off-by: AngeloGioacchino Del Regno
---
arch/arm64/boot/dts/mediatek/mt6795.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt6795.dtsi
b/arch/arm64/boot/dts/mediatek/
Add nodes for the multimedia IOMMU and its LARBs: this includes all but
the MJC LARB, which cannot currently be used and will be added later.
Signed-off-by: AngeloGioacchino Del Regno
---
arch/arm64/boot/dts/mediatek/mt6795.dtsi | 60
1 file changed, 60 insertions(+)
d
MT6331 is the primary PMIC for the MediaTek Helio X10 MT6795 smartphone
platforms: add a devicetree describing its regulators, Real Time Clock
and PMIC-keys.
Signed-off-by: AngeloGioacchino Del Regno
---
arch/arm64/boot/dts/mediatek/mt6331.dtsi | 284 +++
1 file changed, 289
This smartphone uses the Helio X10 standard MT6331+MT6332 combo PMICs:
include the mt6331 devicetree and add the required interrupt.
Note that despite there being two interrupts, one for MT6331 and one
for MT6332, in configurations using the companion PMIC, the interrupt
of the latter fires for bo
Add the BMA255 Accelerometer on I2C3 and its pin definitions.
Signed-off-by: AngeloGioacchino Del Regno
---
.../boot/dts/mediatek/mt6795-sony-xperia-m5.dts | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt6795-sony-xperia-m5.dts
b/arch/arm64
Add the MultiMedia System node, providing clocks for the multimedia
hardware blocks and their IOMMU/SMIs.
Signed-off-by: AngeloGioacchino Del Regno
---
arch/arm64/boot/dts/mediatek/mt6795.dtsi | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt6795
This smartphone features a Bosch BMM050 Magnetometer on I2C3: enable
it with the BMM150 binding, as that driver supports BMM050 as well.
For this sensor, there is no interrupt pin;
readings were validated in sysfs.
Signed-off-by: AngeloGioacchino Del Regno
---
arch/arm64/boot/dts/mediatek/mt679
Configure and enable the MMC0/1/2 controllers, used for the eMMC chip,
MicroSD card slot and SDIO (WiFi) respectively.
Signed-off-by: AngeloGioacchino Del Regno
---
.../dts/mediatek/mt6795-sony-xperia-m5.dts| 91 +++
1 file changed, 91 insertions(+)
diff --git a/arch/arm64/
Hi,
This series of two patches fixes the issue introduced in
cf586021642d80 ("drm/i915/gt: Pipelined page migration") where,
as reported by Matt, in a chain of requests an error is reported
only if happens in the last request.
However Chris noticed that without ensuring exclusivity in the
locking
We have:
- intel_context_timeline_lock()
- intel_context_timeline_unlock()
In the next patches we will also need:
- intel_context_timeline_is_locked()
Add it.
Signed-off-by: Andi Shyti
Cc: sta...@vger.kernel.org
Reviewed-by: Nirmoy Das
---
drivers/gpu/drm/i915/gt/intel_context.h | 6
Make version of the request creation that doesn't hold any
lock.
Signed-off-by: Andi Shyti
Cc: sta...@vger.kernel.org
Reviewed-by: Nirmoy Das
---
drivers/gpu/drm/i915/i915_request.c | 38 +
drivers/gpu/drm/i915/i915_request.h | 2 ++
2 files changed, 30 insertions(+
i915_request_add() assumes that the timeline is locked whtn the
function is called. Before exiting it releases the lock. But in
the next commit we have one case where releasing the timeline
mutex is not necessary and we don't want that.
Make a new i915_request_add_locked() version of the function
From: Chris Wilson
Before taking exclusive ownership of the ring for emitting the request,
wait for space in the ring to become available. This allows others to
take the timeline->mutex to make forward progresses while userspace is
blocked.
In particular, this allows regular clients to issue req
Currently, when we perform operations such as clearing or copying
large blocks of memory, we generate multiple requests that are
executed in a chain.
However, if one of these requests fails, we may not realize it
unless it happens to be the last request in the chain. This is
because errors are not
On 12/04/2023 10:09, Daniel Vetter wrote:
Otherwise core changes don't get noticed by the right people. I
noticed this because a patch set from Jagan Teki seems to have fallen
through the cracks.
Signed-off-by: Daniel Vetter
Cc: Jagan Teki
Cc: Andrzej Hajda
Cc: Neil Armstrong
Cc: Robert Foss
This is a small cleanup of the mtk-dpi driver, switching it to devm
variants where possible and where it made sense, and reducing lines
while retaining and improving human readability.
AngeloGioacchino Del Regno (4):
drm/mediatek: mtk_dpi: Simplify with devm_drm_bridge_add()
drm/mediatek: mtk_
Use dev_err_probe() across the entire probe function of this driver
to shrink the size.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/gpu/drm/mediatek/mtk_dpi.c | 44 ++
1 file changed, 14 insertions(+), 30 deletions(-)
diff --git a/drivers/gpu/drm/mediatek/
Function drm_of_find_panel_or_bridge() is marked as deprecated: since
the usage of that in this driver exactly corresponds to the new function
devm_drm_of_get_bridge(), switch to it.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/gpu/drm/mediatek/mtk_dpi.c | 7 +++
1 file changed, 3
Change drm_bridge_add() to its devm variant to slightly simplify the
probe function.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/gpu/drm/mediatek/mtk_dpi.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/mediatek/mtk_dpi.c
b/drivers/gpu/drm/me
Instead of the open-coded platform_get_resource, devm_ioremap_resource
switch to devm_platform_get_and_ioremap_resource(), doing exactly the
same.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/gpu/drm/mediatek/mtk_dpi.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
On 12/04/2023 10:34, Christian König wrote:
Am 12.04.23 um 00:56 schrieb Rob Clark:
From: Rob Clark
Similar motivation to other similar recent attempt[1]. But with an
attempt to have some shared code for this. As well as documentation.
It is probably a bit UMA-centric, I guess devices wit
On 12.04.2023 13:33, Andi Shyti wrote:
We have:
- intel_context_timeline_lock()
- intel_context_timeline_unlock()
In the next patches we will also need:
- intel_context_timeline_is_locked()
Add it.
Signed-off-by: Andi Shyti
Cc: sta...@vger.kernel.org
Reviewed-by: Nirmoy Das
Revi
On 12/04/2023 05:30, Xiaoyong Lu wrote:
> Add mediatek av1 decoder linux driver which use the stateless API in
> MT8195.
>
> Signed-off-by: Xiaoyong Lu
> Tested-by: Nicolas Dufresne
> Reviewed-by: Nicolas Dufresne
> Tested-by: AngeloGioacchino Del Regno
>
> Reviewed-by: AngeloGioacchino Del Re
Hi,
On 12/04/2023 10:09, Daniel Vetter wrote:
Otherwise core changes don't get noticed by the right people. I
noticed this because a patch set from Jagan Teki seems to have fallen
through the cracks.
Signed-off-by: Daniel Vetter
I'm applying it but I get:
WARNING: From:/Signed-off-by: email
Am 12.04.23 um 14:10 schrieb Tvrtko Ursulin:
On 12/04/2023 10:34, Christian König wrote:
Am 12.04.23 um 00:56 schrieb Rob Clark:
From: Rob Clark
Similar motivation to other similar recent attempt[1]. But with an
attempt to have some shared code for this. As well as documentation.
It is pr
Il 12/04/23 14:22, Hans Verkuil ha scritto:
On 12/04/2023 05:30, Xiaoyong Lu wrote:
Add mediatek av1 decoder linux driver which use the stateless API in
MT8195.
Signed-off-by: Xiaoyong Lu
Tested-by: Nicolas Dufresne
Reviewed-by: Nicolas Dufresne
Tested-by: AngeloGioacchino Del Regno
Reviewed
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote:
Add a compatible string for MediaTek Helio X10 MT6795's display PWM
block: this is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
Reviewed-by: Matthias Brugger
---
Documentation/devicetree/bindings/pwm/mediatek,pwm
On 11/04/2023 23:56, Rob Clark wrote:
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/i915/i915_driver.c | 3 ++-
drivers/gpu/drm/i915/i915_drm_client.c | 18 +-
drivers/gpu/drm/i915/i915_drm_client.h | 2 +-
3 files changed, 8 insertions(+), 15 deleti
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote:
Add a compatible string for MediaTek Helio X10 MT6795: this SoC uses
the same DSI PHY as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
Documentation/devicetree/bindings/phy/mediatek,dsi-phy.yaml | 4
1 file changed, 4 in
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote:
Add a compatible string for the MediaTek Helio X10 MT6795 SoC, using
the same parameters as MT8183.
Signed-off-by: AngeloGioacchino Del Regno
---
.../display/mediatek/mediatek,dpi.yaml| 23 +++
1 file changed,
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote:
Add a compatible string for MediaTek Helio X10 MT6795: similarly to
MT8173, this SoC has the gamma LUT registers in DISP_AAL.
Signed-off-by: AngeloGioacchino Del Regno
Reviewed-by: Matthias Brugger
---
.../devicetree/bindings/dis
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote:
Add a compatible string for MediaTek Helio X10 MT6795, using the same
DSI block as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../display/mediatek/mediatek,dsi.yaml| 19 ---
1 file changed, 12 inser
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote:
Add a compatible string for MediaTek Helio X10 MT6795's WDMA block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,wdma.yaml| 3 +++
1 file changed, 3 i
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote:
Add a compatible string for MediaTek Helio X10 MT6795's COLOR block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
Reviewed-by: Matthias Brugger
---
.../devicetree/bindings/display/mediatek/mediatek,color.
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote:
Add a compatible string for MediaTek Helio X10 MT6795's MERGE block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,merge.yaml | 3 +++
1 file changed, 3
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote:
Add a compatible string for MediaTek Helio X10 MT6795's SPLIT block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,split.yaml | 3 +++
1 file changed, 3
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote:
Add a compatible string for MediaTek Helio X10 MT6795's UFOE block: this
is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,ufoe.yaml| 3 +++
1 file changed, 3 i
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote:
Add a compatible string for MediaTek Helio X10 MT6795's OverDrive (OD)
block: this is the same as MT8173.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/display/mediatek/mediatek,od.yaml | 3 +++
1 file ch
On 12/04/2023 13:27, AngeloGioacchino Del Regno wrote:
Add a compatible string for the MT6795 Helio X10 SoC using MT8173
binding and add a header for the MT6795's GCE mailbox.
Signed-off-by: AngeloGioacchino Del Regno
Reviewed-by: Krzysztof Kozlowski
Reviewed-by: Matthias Brugger
---
On 12/04/2023 14:22, Hans Verkuil wrote:
> On 12/04/2023 05:30, Xiaoyong Lu wrote:
>> Add mediatek av1 decoder linux driver which use the stateless API in
>> MT8195.
>>
>> Signed-off-by: Xiaoyong Lu
>> Tested-by: Nicolas Dufresne
>> Reviewed-by: Nicolas Dufresne
>> Tested-by: AngeloGioacchino Del
1 - 100 of 272 matches
Mail list logo
