Re: [PULL] drm-misc-next

2024-02-26 Thread Daniel Vetter
On Thu, Feb 22, 2024 at 02:58:41PM +0100, Thomas Zimmermann wrote:
> Hi Dave, Sima,
> 
> this is the weekly PR for drm-misc-next. It's the usual set of
> fixes and driver updates. Statistics computation for shared GEM BOs
> has been updated to take imported DMA bufs into account. This can
> result in different output from fdinfo files, which could be seen
> as a UAPI change.
> 
> Best regards
> Thomas
> 
> drm-misc-next-2024-02-22:
> drm-misc-next for v6.9:
> 
> UAPI Changes:
> 
> - changes to fdinfo stats
> 
> Cross-subsystem Changes:
> 
> agp:
> - remove unused type field from struct agp_bridge_data
> 
> Core Changes:
> 
> ci:
> - update test names
> - cleanups
> 
> gem:
> - add stats for shared buffers plus updates to amdgpu, i915, xe
> 
> Documentation:
> - fixes
> 
> syncobj:
> - fixes to waiting and sleeping
> 
> Driver Changes:
> 
> bridge:
> - adv7511: fix crash on irq during probe
> - dw_hdmi: set bridge type
> 
> host1x:
> - cleanups
> 
> ivpu:
> - updates to firmware API
> - refactor BO allocation
> 
> meson:
> - fix error handling in probe
> 
> panel:
> - revert "drm/panel-edp: Add auo_b116xa3_mode"
> - add Himax HX83112A plus DT bindings
> - ltk500hd1829: add support for ltk101b4029w and admatec 9904370
> - simple: add BOE BP082WX1-100 8.2" panel plus DT bindungs
> 
> renesas:
> - add RZ/G2L DU support plus DT bindings
> The following changes since commit aa1267e673fe5307cf00d02add4017d2878598b6:
> 
>   drm: ci: use clk_ignore_unused for apq8016 (2024-02-14 11:23:56 -0300)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2024-02-22

Merged into drm-next, thanks a lot!
-Sima

> 
> for you to fetch changes up to a3baaca4a8766e9386e472d97315e5c131beb87d:
> 
>   drm: renesas: rz-du: Fix redefinition errors related to rzg2l_du_vsp_*() 
> (2024-02-22 14:46:41 +0100)
> 
> 
> drm-misc-next for v6.9:
> 
> UAPI Changes:
> 
> - changes to fdinfo stats
> 
> Cross-subsystem Changes:
> 
> agp:
> - remove unused type field from struct agp_bridge_data
> 
> Core Changes:
> 
> ci:
> - update test names
> - cleanups
> 
> gem:
> - add stats for shared buffers plus updates to amdgpu, i915, xe
> 
> Documentation:
> - fixes
> 
> syncobj:
> - fixes to waiting and sleeping
> 
> Driver Changes:
> 
> bridge:
> - adv7511: fix crash on irq during probe
> - dw_hdmi: set bridge type
> 
> host1x:
> - cleanups
> 
> ivpu:
> - updates to firmware API
> - refactor BO allocation
> 
> meson:
> - fix error handling in probe
> 
> panel:
> - revert "drm/panel-edp: Add auo_b116xa3_mode"
> - add Himax HX83112A plus DT bindings
> - ltk500hd1829: add support for ltk101b4029w and admatec 9904370
> - simple: add BOE BP082WX1-100 8.2" panel plus DT bindungs
> 
> renesas:
> - add RZ/G2L DU support plus DT bindings
> 
> 
> Alex Deucher (6):
>   Documentation/gpu: Update documentation on drm-shared-*
>   drm: add drm_gem_object_is_shared_for_memory_stats() helper
>   drm: update drm_show_memory_stats() for dma-bufs
>   drm/amdgpu: add shared fdinfo stats
>   drm/i915: Update shared stats to use the new gem helper
>   drm/xe: Update shared stats to use the new gem helper
> 
> Alexander Stein (1):
>   drm: bridge: dw_hdmi: Set DRM bridge type
> 
> Biju Das (6):
>   dt-bindings: display: Document Renesas RZ/G2L DU bindings
>   dt-bindings: display: renesas,rzg2l-du: Document RZ/V2L DU bindings
>   drm: renesas: Add RZ/G2L DU Support
>   MAINTAINERS: Update entries for Renesas DRM drivers
>   MAINTAINERS: Create entry for Renesas RZ DRM drivers
>   drm: renesas: rz-du: Fix redefinition errors related to rzg2l_du_vsp_*()
> 
> Colin Ian King (1):
>   gpu: host1x: remove redundant assignment to variable space
> 
> Devarsh Thakkar (1):
>   dt-bindings: display: ti,am65x-dss: Add support for common1 region
> 
> Dmitry Baryshkov (4):
>   drm/ci: skip suspend tests for both msm-sc7180 machines
>   drm/ci: update IGT test names
>   drm/ci: update msm-apq8096-fails list
>   drm/ci: mark universal-plane-sanity as failing on SC7180
> 
> Douglas Anderson (1):
>   drm/panel: boe-tv101wum-nl6: make use of prepare_prev_first
> 
> Erik Kurzinger (3):
>   drm/syncobj: call drm_syncobj_fence_add_wait when WAIT_AVAILABLE flag 
> is set
>   drm/syncobj: reject invalid flags in drm_syncobj_find_fence
>   drm/syncobj: call might_sleep before waiting for fence submission
> 
> Geert Uytterhoeven (1):
>   drm: Spelling s/hardward/hardware/g
> 
> Heiko Stuebner (5):
>   dt-bindings: vendor-prefixes: add prefix for admatec GmbH
>   dt-bindings: display: panel-lvds: Add compatible for admatec 9904370 
> panel
>   drm/panel: ltk500hd1829: make room for more similar panels
>   dt-bindings: display: ltk500hd1829: add variant compatible for 
> ltk101b4029w
>   drm/panel: 

Re: [PULL] drm-misc-next

2023-11-23 Thread Daniel Vetter
On Thu, Nov 23, 2023 at 01:58:50PM +0100, Maxime Ripard wrote:
> Hi,
> 
> Here's this week drm-misc-next PR.
> 
> It's been fairly calm, but there's one big change: the IMG GPU driver is
> now merged!
> 
> Maxime
> 
> drm-misc-next-2023-11-23:
> drm-misc-next for 6.8:
> 
> UAPI Changes:
> 
> Cross-subsystem Changes:
> 
> Core Changes:
>   - Drop deprecated drm_kms_helper.edid_firmware module parameter
> 
> Driver Changes:
>   - Convert platform drivers remove callback to return void
>   - imagination: Introduction of the Imagination GPU Support
>   - rockchip:
> - rk3066_hdmi: Convert to atomic
> - vop2: Support NV20 and NV30
>   - panel:
> - elida-kd35t133: PM reworks
> - New panels: Powkiddy RK2023
> The following changes since commit 3b434a3445fff3149128db0169da864d67057325:
> 
>   accel/ivpu: Use threaded IRQ to handle JOB done messages (2023-11-16 
> 13:41:49 +0100)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2023-11-23

Merged to drm-next, thanks.
-Sima

> 
> for you to fetch changes up to 815d8b0425ad1164e45953ac3d56a9f6f63792cc:
> 
>   drm/imagination: Add driver documentation (2023-11-23 09:01:47 +0100)
> 
> 
> drm-misc-next for 6.8:
> 
> UAPI Changes:
> 
> Cross-subsystem Changes:
> 
> Core Changes:
>   - Drop deprecated drm_kms_helper.edid_firmware module parameter
> 
> Driver Changes:
>   - Convert platform drivers remove callback to return void
>   - imagination: Introduction of the Imagination GPU Support
>   - rockchip:
> - rk3066_hdmi: Convert to atomic
> - vop2: Support NV20 and NV30
>   - panel:
> - elida-kd35t133: PM reworks
> - New panels: Powkiddy RK2023
> 
> 
> Abhinav Singh (1):
>   drm/nouveau/fence:: fix warning directly dereferencing a rcu pointer
> 
> Arnd Bergmann (1):
>   drm/rockchip: rk3066_hdmi: include drm/drm_atomic.h
> 
> Chris Morgan (8):
>   dt-bindings: display: nv3051d: Update NewVision NV3051D compatibles
>   drm/panel: nv3051d: Hold panel in reset for unprepare
>   drm/panel: nv3051d: Add Powkiddy RK2023 Panel Support
>   drm/panel-elida-kd35t133: trival: update panel size from 5.5 to 3.5
>   drm/panel-elida-kd35t133: hold panel in reset for unprepare
>   drm/panel-elida-kd35t133: drop drm_connector_set_orientation_from_panel
>   drm/panel-elida-kd35t133: Drop shutdown logic
>   drm/panel-elida-kd35t133: Drop prepare/unprepare logic
> 
> Donald Robson (2):
>   drm/gpuvm: Helper to get range of unmap from a remap op.
>   drm/imagination: Add GEM and VM related code
> 
> Jani Nikula (1):
>   drm/edid/firmware: drop drm_kms_helper.edid_firmware backward compat
> 
> Jeffrey Hugo (1):
>   accel/qaic: Update MAX_ORDER use to be inclusive
> 
> Johan Jonker (2):
>   drm/rockchip: rk3066_hdmi: Remove useless mode_fixup
>   drm/rockchip: rk3066_hdmi: Switch encoder hooks to atomic
> 
> Jonas Karlman (1):
>   drm/rockchip: vop2: Add NV20 and NV30 support
> 
> Kees Cook (1):
>   dma-buf: Replace strlcpy() with strscpy()
> 
> Luben Tuikov (1):
>   drm/print: Handle NULL drm device in __drm_printk()
> 
> Matt Coster (1):
>   sizes.h: Add entries between SZ_32G and SZ_64T
> 
> Richard Acayan (1):
>   fbdev/simplefb: Suppress error on missing power domains
> 
> Sarah Walker (17):
>   dt-bindings: gpu: Add Imagination Technologies PowerVR/IMG GPU
>   drm/imagination/uapi: Add PowerVR driver UAPI
>   drm/imagination: Add skeleton PowerVR driver
>   drm/imagination: Get GPU resources
>   drm/imagination: Add GPU register headers
>   drm/imagination: Add firmware and MMU related headers
>   drm/imagination: Add FWIF headers
>   drm/imagination: Add GPU ID parsing and firmware loading
>   drm/imagination: Implement power management
>   drm/imagination: Implement firmware infrastructure and META FW support
>   drm/imagination: Implement MIPS firmware processor and MMU support
>   drm/imagination: Implement free list and HWRT create and destroy ioctls
>   drm/imagination: Implement context creation/destruction ioctls
>   drm/imagination: Implement job submission and scheduling
>   drm/imagination: Add firmware trace header
>   drm/imagination: Add firmware trace to debugfs
>   drm/imagination: Add driver documentation
> 
> Tomi Valkeinen (1):
>   drm/tilcdc: Fix irq free on unload
> 
> Uwe Kleine-König (14):
>   drm/bridge: tpd12s015: Drop buggy __exit annotation for remove function
>   drm/arcpgu: Convert to platform remove callback returning void
>   drm/armada: Convert to platform remove callback returning void
>   drm/bridge: cdns-mhdp8546: Improve error reporting in remove callback
>   drm/bridge: cdns-mhdp8546: Convert to platform remove callback 
> returning void
>   drm/bridge: 

Re: [PULL] drm-misc-next

2023-11-20 Thread Daniel Vetter
On Fri, Nov 17, 2023 at 10:41:34AM +0100, Maxime Ripard wrote:
> Hi,
> 
> Here's the first drm-misc-next PR for what will become 6.8.
> 
> There's one missing SoB on the commit 0da611a87021 ("dma-buf: add
> dma_fence_timestamp helper") from the committer. They provided their SoB
> on the ML here after the facts:
> https://lore.kernel.org/dri-devel/ce94020e-a7d4-4799-b87d-fbea7b14a...@gmail.com/

I added this to the merge commit so it's recorded.

> 
> Maxime
> 
> drm-misc-next-2023-11-17:
> drm-misc-next for 6.8:
> 
> UAPI Changes:
>   - drm: Introduce CLOSE_FB ioctl
>   - drm/dp-mst: Documentation for the PATH property
>   - fdinfo: Do not align to a MB if the size is larger than 1MiB
>   - virtio-gpu: add explicit virtgpu context debug name
> 
> Cross-subsystem Changes:
>   - dma-buf: Add dma_fence_timestamp helper
> 
> Core Changes:
>   - client: Do not acquire module reference
>   - edid: split out drm_eld, add SAD helpers
>   - format-helper: Cache format conversion buffers
>   - sched: Move from a kthread to a workqueue, rename some internal
> functions to make it clearer, implement dynamic job-flow control
>   - gpuvm: Provide more features to handle GEM objects
>   - tests: Remove slow kunit tests
> 
> Driver Changes:
>   - ivpu: Update FW API, new debugfs file, a new NOP job submission test
> mode, improve suspend/resume, PM improvements, MMU PT optimizations,
> firmware profiling frequency support, support for uncached buffers,
> switch to gem shmem helpers, replace kthread with threaded
> interrupts
>   - panfrost: PM improvements
>   - qaic: Allow to run with a single MSI, support host/device time
> synchronization, misc improvements
>   - simplefb: Support memory-regions, support power-domains
>   - ssd130x: Unitialized variable fixes
>   - omapdrm: dma-fence lockdep annotation fix
>   - tidss: dma-fence lockdep annotation fix
>   - v3d: Support BCM2712 (RaspberryPi5), Support fdinfo and gputop
>   - panel:
> - edp: Support AUO B116XTN02, BOE NT116WHM-N21,836X2, NV116WHM-N49
>   V8.0, plus a whole bunch of panels used on Mediatek chromebooks.
> The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
> 
>   Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2023-11-17

Pulled into drm-next, thanks.
-Sima

> 
> for you to fetch changes up to 3b434a3445fff3149128db0169da864d67057325:
> 
>   accel/ivpu: Use threaded IRQ to handle JOB done messages (2023-11-16 
> 13:41:49 +0100)
> 
> 
> drm-misc-next for 6.8:
> 
> UAPI Changes:
>   - drm: Introduce CLOSE_FB ioctl
>   - drm/dp-mst: Documentation for the PATH property
>   - fdinfo: Do not align to a MB if the size is larger than 1MiB
>   - virtio-gpu: add explicit virtgpu context debug name
> 
> Cross-subsystem Changes:
>   - dma-buf: Add dma_fence_timestamp helper
> 
> Core Changes:
>   - client: Do not acquire module reference
>   - edid: split out drm_eld, add SAD helpers
>   - format-helper: Cache format conversion buffers
>   - sched: Move from a kthread to a workqueue, rename some internal
> functions to make it clearer, implement dynamic job-flow control
>   - gpuvm: Provide more features to handle GEM objects
>   - tests: Remove slow kunit tests
> 
> Driver Changes:
>   - ivpu: Update FW API, new debugfs file, a new NOP job submission test
> mode, improve suspend/resume, PM improvements, MMU PT optimizations,
> firmware profiling frequency support, support for uncached buffers,
> switch to gem shmem helpers, replace kthread with threaded
> interrupts
>   - panfrost: PM improvements
>   - qaic: Allow to run with a single MSI, support host/device time
> synchronization, misc improvements
>   - simplefb: Support memory-regions, support power-domains
>   - ssd130x: Unitialized variable fixes
>   - omapdrm: dma-fence lockdep annotation fix
>   - tidss: dma-fence lockdep annotation fix
>   - v3d: Support BCM2712 (RaspberryPi5), Support fdinfo and gputop
>   - panel:
> - edp: Support AUO B116XTN02, BOE NT116WHM-N21,836X2, NV116WHM-N49
>   V8.0, plus a whole bunch of panels used on Mediatek chromebooks.
> 
> 
> Ajit Pal Singh (1):
>   accel/qaic: Add support for periodic timesync
> 
> Andrzej Kacprowski (4):
>   accel/ivpu: Add support for VPU_JOB_FLAGS_NULL_SUBMISSION_MASK
>   accel/ivpu/40xx: Capture D0i3 entry host and device timestamps
>   accel/ivpu: Pass D0i3 residency time to the VPU firmware
>   accel/ivpu: Add support for delayed D0i3 entry message
> 
> AngeloGioacchino Del Regno (7):
>   drm/panfrost: Really power off GPU cores in panfrost_gpu_power_off()
>   drm/panfrost: Perform hard reset to recover GPU if soft reset fails
>   drm/panfrost: Tighten polling for soft reset and power on
>   

Re: [PULL] drm-misc-next

2023-11-06 Thread David Edelsohn
On Mon, Nov 6, 2023 at 5:55 AM Maxime Ripard  wrote:

> On Mon, Nov 06, 2023 at 11:37:34AM +0100, Thomas Hellström wrote:
> > On 11/6/23 11:20, Maxime Ripard wrote:
> > > On Mon, Nov 06, 2023 at 11:01:51AM +0100, Thomas Hellström wrote:
> > > > Hi, David.
> > > >
> > > > On 11/3/23 17:37, David Edelsohn wrote:
> > > > > Dual-license drm_gpuvm to GPL-2.0 OR MIT.
> > > > > diff --git a/drivers/gpu/drm/drm_gpuvm.c
> b/drivers/gpu/drm/drm_gpuvm.c
> > > > > index 02ce6baacdad..08c088319652 100644 ---
> > > > > a/drivers/gpu/drm/drm_gpuvm.c <
> https://cgit.freedesktop.org/drm/drm-misc/tree/drivers/gpu/drm/drm_gpuvm.c?id=6f2eeef4a0aa9791bbba9d353641a6e067bb86c1
> >
> > > > > +++ b/drivers/gpu/drm/drm_gpuvm.c <
> https://cgit.freedesktop.org/drm/drm-misc/tree/drivers/gpu/drm/drm_gpuvm.c?id=f7749a549b4f4db0c02e6b3d3800ea400dd76c12
> >
> > > > > @@ -1,4 +1,4 @@
> > > > > -// SPDX-License-Identifier: GPL-2.0-only
> > > > > +// SPDX-License-Identifier: GPL-2.0 OR MIT
> > > > > /*
> > > > > * Copyright (c) 2022 Red Hat.
> > > > > *
> > > > > The above SPDX License Identifier change is incorrect and no longer
> > > > > valid. The change misunderstood the syntax of SPDX license
> identifiers
> > > > > and boolean operations. GPL-2.0-only is the name of the license
> and means
> > > > > GPL 2.0 only, as opposed to GPL 2.0 or later. The "only" does not
> > > > > refer to restrictions on other licenses in the identifier and
> should not
> > > > > have been
> > > > > removed. The hyphens designated that the name was a single unit.
> > > > > The SPDX License Identifier boolean operators, such as OR, are a
> > > > > separate layer
> > > > > of syntax.
> > > > > The SPDX License Identifier should be
> > > > > GPL-2.0-only OR MIT
> > > > > Thanks, David
> > > > The author has acked the change / relicensing, which is also
> described in
> > > > the commit title so could you please elaborate why you think it is
> not
> > > > valid?
> > > I think their point isn't so much about the license itself but rather
> > > the SPDX syntax to express it.
> > >
> > > Maxime
> >
> > Hm. There are a pretty large number of these in drm with the same syntax:
> >
> > SPDX-License-Identifier: GPL-2.0 OR MIT
> >
> > So I read it as whe shouldn't have change "Licence A" to "Licence B OR
> > C" but instead should have changed it to "Licence A OR C", hence the
> > *change* (rather than the syntax) would no longer be valid.
> >
> > Perhaps I have had too little coffee this morning.
> >
> > I'd appreciate if David could clarify.
>
> Either way, one of the issue is that GPL-2.0 was deprecated in favour of
> GPL-2.0-only
>
> https://spdx.org/licenses/GPL-2.0.html
>
> So you effectively changed the preferred syntax to the deprecated one in
> the process of adding the new license.
>
> I think that's what David was saying, but there might be something else :)
>

Yes, that is what I was trying to express.

And thanks for posting the patch to correct the name of the identifier.
I'm not requesting that all uses of the deprecated identifier be changed in
the Linux kernel, but it would be good to not regress.

Thanks, David


Re: [PULL] drm-misc-next

2023-11-06 Thread Maxime Ripard
On Mon, Nov 06, 2023 at 11:37:34AM +0100, Thomas Hellström wrote:
> On 11/6/23 11:20, Maxime Ripard wrote:
> > On Mon, Nov 06, 2023 at 11:01:51AM +0100, Thomas Hellström wrote:
> > > Hi, David.
> > > 
> > > On 11/3/23 17:37, David Edelsohn wrote:
> > > > Dual-license drm_gpuvm to GPL-2.0 OR MIT.
> > > > diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c
> > > > index 02ce6baacdad..08c088319652 100644 ---
> > > > a/drivers/gpu/drm/drm_gpuvm.c 
> > > > 
> > > > +++ b/drivers/gpu/drm/drm_gpuvm.c 
> > > > 
> > > > @@ -1,4 +1,4 @@
> > > > -// SPDX-License-Identifier: GPL-2.0-only
> > > > +// SPDX-License-Identifier: GPL-2.0 OR MIT
> > > > /*
> > > > * Copyright (c) 2022 Red Hat.
> > > > *
> > > > The above SPDX License Identifier change is incorrect and no longer
> > > > valid. The change misunderstood the syntax of SPDX license identifiers
> > > > and boolean operations. GPL-2.0-only is the name of the license and 
> > > > means
> > > > GPL 2.0 only, as opposed to GPL 2.0 or later. The "only" does not
> > > > refer to restrictions on other licenses in the identifier and should not
> > > > have been
> > > > removed. The hyphens designated that the name was a single unit.
> > > > The SPDX License Identifier boolean operators, such as OR, are a
> > > > separate layer
> > > > of syntax.
> > > > The SPDX License Identifier should be
> > > > GPL-2.0-only OR MIT
> > > > Thanks, David
> > > The author has acked the change / relicensing, which is also described in
> > > the commit title so could you please elaborate why you think it is not
> > > valid?
> > I think their point isn't so much about the license itself but rather
> > the SPDX syntax to express it.
> > 
> > Maxime
> 
> Hm. There are a pretty large number of these in drm with the same syntax:
> 
> SPDX-License-Identifier: GPL-2.0 OR MIT
> 
> So I read it as whe shouldn't have change "Licence A" to "Licence B OR
> C" but instead should have changed it to "Licence A OR C", hence the
> *change* (rather than the syntax) would no longer be valid.
> 
> Perhaps I have had too little coffee this morning.
> 
> I'd appreciate if David could clarify.

Either way, one of the issue is that GPL-2.0 was deprecated in favour of
GPL-2.0-only

https://spdx.org/licenses/GPL-2.0.html

So you effectively changed the preferred syntax to the deprecated one in
the process of adding the new license.

I think that's what David was saying, but there might be something else :)

Maxime


signature.asc
Description: PGP signature


Re: [PULL] drm-misc-next

2023-11-06 Thread Thomas Hellström



On 11/6/23 11:37, Thomas Hellström wrote:

Hi,

On 11/6/23 11:20, Maxime Ripard wrote:

On Mon, Nov 06, 2023 at 11:01:51AM +0100, Thomas Hellström wrote:

Hi, David.

On 11/3/23 17:37, David Edelsohn wrote:

Dual-license drm_gpuvm to GPL-2.0 OR MIT.
diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c
index 02ce6baacdad..08c088319652 100644 ---
a/drivers/gpu/drm/drm_gpuvm.c 

+++ b/drivers/gpu/drm/drm_gpuvm.c 


@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL-2.0-only
+// SPDX-License-Identifier: GPL-2.0 OR MIT
/*
* Copyright (c) 2022 Red Hat.
*
The above SPDX License Identifier change is incorrect and no longer
valid. The change misunderstood the syntax of SPDX license identifiers
and boolean operations. GPL-2.0-only is the name of the license and 
means

GPL 2.0 only, as opposed to GPL 2.0 or later. The "only" does not
refer to restrictions on other licenses in the identifier and 
should not

have been
removed. The hyphens designated that the name was a single unit.
The SPDX License Identifier boolean operators, such as OR, are a
separate layer
of syntax.
The SPDX License Identifier should be
GPL-2.0-only OR MIT
Thanks, David
The author has acked the change / relicensing, which is also 
described in

the commit title so could you please elaborate why you think it is not
valid?

I think their point isn't so much about the license itself but rather
the SPDX syntax to express it.

Maxime


Hm. There are a pretty large number of these in drm with the same syntax:

SPDX-License-Identifier: GPL-2.0 OR MIT

So I read it as whe shouldn't have change "Licence A" to "Licence B OR 
C" but instead should have changed it to "Licence A OR C", hence the 
*change* (rather than the syntax) would no longer be valid.


Perhaps I have had too little coffee this morning.

Ah, so a quick read-up on SPDX identifiers helped. "GPL-2.0" is 
deprecated and should not be used in new licensing. I'll put together a 
patch to fix that up.


/Thomas




Re: [PULL] drm-misc-next

2023-11-06 Thread Thomas Hellström

Hi,

On 11/6/23 11:20, Maxime Ripard wrote:

On Mon, Nov 06, 2023 at 11:01:51AM +0100, Thomas Hellström wrote:

Hi, David.

On 11/3/23 17:37, David Edelsohn wrote:

Dual-license drm_gpuvm to GPL-2.0 OR MIT.
diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c
index 02ce6baacdad..08c088319652 100644 ---
a/drivers/gpu/drm/drm_gpuvm.c 

+++ b/drivers/gpu/drm/drm_gpuvm.c 

@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL-2.0-only
+// SPDX-License-Identifier: GPL-2.0 OR MIT
/*
* Copyright (c) 2022 Red Hat.
*
The above SPDX License Identifier change is incorrect and no longer
valid. The change misunderstood the syntax of SPDX license identifiers
and boolean operations. GPL-2.0-only is the name of the license and means
GPL 2.0 only, as opposed to GPL 2.0 or later. The "only" does not
refer to restrictions on other licenses in the identifier and should not
have been
removed. The hyphens designated that the name was a single unit.
The SPDX License Identifier boolean operators, such as OR, are a
separate layer
of syntax.
The SPDX License Identifier should be
GPL-2.0-only OR MIT
Thanks, David

The author has acked the change / relicensing, which is also described in
the commit title so could you please elaborate why you think it is not
valid?

I think their point isn't so much about the license itself but rather
the SPDX syntax to express it.

Maxime


Hm. There are a pretty large number of these in drm with the same syntax:

SPDX-License-Identifier: GPL-2.0 OR MIT

So I read it as whe shouldn't have change "Licence A" to "Licence B OR C" but instead 
should have changed it to "Licence A OR C", hence the *change* (rather than the syntax) would no 
longer be valid.

Perhaps I have had too little coffee this morning.

I'd appreciate if David could clarify.

Thanks,
Thomas









Re: [PULL] drm-misc-next

2023-11-06 Thread Maxime Ripard
On Mon, Nov 06, 2023 at 11:01:51AM +0100, Thomas Hellström wrote:
> Hi, David.
> 
> On 11/3/23 17:37, David Edelsohn wrote:
> > Dual-license drm_gpuvm to GPL-2.0 OR MIT.
> > diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c
> > index 02ce6baacdad..08c088319652 100644 ---
> > a/drivers/gpu/drm/drm_gpuvm.c 
> > 
> > +++ b/drivers/gpu/drm/drm_gpuvm.c 
> > 
> > @@ -1,4 +1,4 @@
> > -// SPDX-License-Identifier: GPL-2.0-only
> > +// SPDX-License-Identifier: GPL-2.0 OR MIT
> > /*
> > * Copyright (c) 2022 Red Hat.
> > *
> > The above SPDX License Identifier change is incorrect and no longer
> > valid. The change misunderstood the syntax of SPDX license identifiers
> > and boolean operations. GPL-2.0-only is the name of the license and means
> > GPL 2.0 only, as opposed to GPL 2.0 or later. The "only" does not
> > refer to restrictions on other licenses in the identifier and should not
> > have been
> > removed. The hyphens designated that the name was a single unit.
> > The SPDX License Identifier boolean operators, such as OR, are a
> > separate layer
> > of syntax.
> > The SPDX License Identifier should be
> > GPL-2.0-only OR MIT
> > Thanks, David
> 
> The author has acked the change / relicensing, which is also described in
> the commit title so could you please elaborate why you think it is not
> valid?

I think their point isn't so much about the license itself but rather
the SPDX syntax to express it.

Maxime


signature.asc
Description: PGP signature


Re: [PULL] drm-misc-next

2023-11-06 Thread Thomas Hellström

Hi, David.

On 11/3/23 17:37, David Edelsohn wrote:

Dual-license drm_gpuvm to GPL-2.0 OR MIT.
diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c 
index 02ce6baacdad..08c088319652 100644 --- 
a/drivers/gpu/drm/drm_gpuvm.c 
 
+++ b/drivers/gpu/drm/drm_gpuvm.c 


@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL-2.0-only
+// SPDX-License-Identifier: GPL-2.0 OR MIT
/*
* Copyright (c) 2022 Red Hat.
*
The above SPDX License Identifier change is incorrect and no longer
valid. The change misunderstood the syntax of SPDX license identifiers
and boolean operations. GPL-2.0-only is the name of the license and means
GPL 2.0 only, as opposed to GPL 2.0 or later. The "only" does not
refer to restrictions on other licenses in the identifier and should 
not have been

removed. The hyphens designated that the name was a single unit.
The SPDX License Identifier boolean operators, such as OR, are a 
separate layer

of syntax.
The SPDX License Identifier should be
GPL-2.0-only OR MIT
Thanks, David


The author has acked the change / relicensing, which is also described 
in the commit title so could you please elaborate why you think it is 
not valid?


Thanks,

Thomas




Re: [PULL] drm-misc-next

2023-11-03 Thread David Edelsohn
Dual-license drm_gpuvm to GPL-2.0 OR MIT.

diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c
index 02ce6baacdad..08c088319652 100644
--- a/drivers/gpu/drm/drm_gpuvm.c

+++ b/drivers/gpu/drm/drm_gpuvm.c

@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL-2.0-only
+// SPDX-License-Identifier: GPL-2.0 OR MIT
 /*
  * Copyright (c) 2022 Red Hat.
  *

The above SPDX License Identifier change is incorrect and no longer
valid.  The change misunderstood the syntax of SPDX license identifiers
and boolean operations.  GPL-2.0-only is the name of the license and means
GPL 2.0 only, as opposed to GPL 2.0 or later.  The "only" does not
refer to restrictions on other licenses in the identifier and should
not have been
removed.  The hyphens designated that the name was a single unit.
The SPDX License Identifier boolean operators, such as OR, are a separate layer
of syntax.

The SPDX License Identifier should be

GPL-2.0-only OR MIT

Thanks, David


Re: [PULL] drm-misc-next

2023-08-14 Thread Helen Mae Koike Fornazier
On Monday, August 14, 2023 19:17 -03, Helen Koike  
wrote:

> The following changes since commit f5d8f9c0d8b4bc8ad7e7b23a9f4d116e99202dd3:
> 
>   drm/panel: JDI LT070ME05000 simplify with dev_err_probe() (2023-08-14 
> 14:44:30 +0200)
> 
> are available in the Git repository at:
> 
>   g...@gitlab.freedesktop.org:helen.fornazier/linux.git 
> tags/drm-ci-v12-drm-misc
> 
> for you to fetch changes up to cf50bc174149379c712a396ae556e2e908ee88e0:
> 
>   drm: Add initial ci/ subdirectory (2023-08-14 18:36:14 -0300)
> 
> 
> drm-ci for drm-misc-next
> 
> Here is the patch that adds a ci/ subdirectory to drm and allows
> developers to easily execute tests.
> 
> Developers can easily execute several tests on different devices
> by just pushing their branch to their fork in a repository hosted
> on gitlab.freedesktop.org which has an infrastructure to run jobs
> in several runners and farms with different devices.
> 
> The patch was acked and tested by others.
> 
> Signed-off-by: Helen Koike 
> 
> 
> Tomeu Vizoso (1):
>   drm: Add initial ci/ subdirectory
> 
>  Documentation/gpu/automated_testing.rst|  144 +
>  Documentation/gpu/index.rst|1 +
>  MAINTAINERS|8 +
>  drivers/gpu/drm/ci/arm.config  |   69 +
>  drivers/gpu/drm/ci/arm64.config|  199 ++
>  drivers/gpu/drm/ci/build-igt.sh|   35 +
>  drivers/gpu/drm/ci/build.sh|  157 ++
>  drivers/gpu/drm/ci/build.yml   |  110 +
>  drivers/gpu/drm/ci/check-patch.py  |   57 +
>  drivers/gpu/drm/ci/container.yml   |   65 +
>  drivers/gpu/drm/ci/gitlab-ci.yml   |  251 ++
>  drivers/gpu/drm/ci/igt_runner.sh   |   77 +
>  drivers/gpu/drm/ci/image-tags.yml  |   15 +
>  drivers/gpu/drm/ci/lava-submit.sh  |   57 +
>  drivers/gpu/drm/ci/static-checks.yml   |   12 +
>  drivers/gpu/drm/ci/test.yml|  335 +++
>  drivers/gpu/drm/ci/testlist.txt| 2912 
> 
>  drivers/gpu/drm/ci/x86_64.config   |  111 +
>  drivers/gpu/drm/ci/xfails/amdgpu-stoney-fails.txt  |   19 +
>  drivers/gpu/drm/ci/xfails/amdgpu-stoney-flakes.txt |   21 +
>  drivers/gpu/drm/ci/xfails/amdgpu-stoney-skips.txt  |2 +
>  drivers/gpu/drm/ci/xfails/i915-amly-fails.txt  |   17 +
>  drivers/gpu/drm/ci/xfails/i915-amly-flakes.txt |   32 +
>  drivers/gpu/drm/ci/xfails/i915-amly-skips.txt  |4 +
>  drivers/gpu/drm/ci/xfails/i915-apl-fails.txt   |   58 +
>  drivers/gpu/drm/ci/xfails/i915-apl-flakes.txt  |1 +
>  drivers/gpu/drm/ci/xfails/i915-apl-skips.txt   |6 +
>  drivers/gpu/drm/ci/xfails/i915-cml-fails.txt   |   18 +
>  drivers/gpu/drm/ci/xfails/i915-cml-flakes.txt  |   38 +
>  drivers/gpu/drm/ci/xfails/i915-cml-skips.txt   |2 +
>  drivers/gpu/drm/ci/xfails/i915-glk-fails.txt   |   19 +
>  drivers/gpu/drm/ci/xfails/i915-glk-flakes.txt  |   41 +
>  drivers/gpu/drm/ci/xfails/i915-glk-skips.txt   |5 +
>  drivers/gpu/drm/ci/xfails/i915-kbl-fails.txt   |   25 +
>  drivers/gpu/drm/ci/xfails/i915-kbl-flakes.txt  |   26 +
>  drivers/gpu/drm/ci/xfails/i915-kbl-skips.txt   |5 +
>  drivers/gpu/drm/ci/xfails/i915-tgl-fails.txt   |   37 +
>  drivers/gpu/drm/ci/xfails/i915-tgl-flakes.txt  |5 +
>  drivers/gpu/drm/ci/xfails/i915-tgl-skips.txt   |   11 +
>  drivers/gpu/drm/ci/xfails/i915-whl-fails.txt   |   48 +
>  drivers/gpu/drm/ci/xfails/i915-whl-flakes.txt  |1 +
>  drivers/gpu/drm/ci/xfails/i915-whl-skips.txt   |2 +
>  .../gpu/drm/ci/xfails/mediatek-mt8173-fails.txt|   29 +
>  .../gpu/drm/ci/xfails/mediatek-mt8173-flakes.txt   |0
>  .../gpu/drm/ci/xfails/mediatek-mt8183-fails.txt|   10 +
>  .../gpu/drm/ci/xfails/mediatek-mt8183-flakes.txt   |   14 +
>  drivers/gpu/drm/ci/xfails/meson-g12b-fails.txt |   12 +
>  drivers/gpu/drm/ci/xfails/meson-g12b-flakes.txt|4 +
>  drivers/gpu/drm/ci/xfails/msm-apq8016-fails.txt|   15 +
>  drivers/gpu/drm/ci/xfails/msm-apq8016-flakes.txt   |4 +
>  drivers/gpu/drm/ci/xfails/msm-apq8096-fails.txt|2 +
>  drivers/gpu/drm/ci/xfails/msm-apq8096-flakes.txt   |4 +
>  drivers/gpu/drm/ci/xfails/msm-apq8096-skips.txt|2 +
>  drivers/gpu/drm/ci/xfails/msm-sc7180-fails.txt |   25 +
>  drivers/gpu/drm/ci/xfails/msm-sc7180-flakes.txt|7 +
>  drivers/gpu/drm/ci/xfails/msm-sc7180-skips.txt |   23 +
>  drivers/gpu/drm/ci/xfails/msm-sdm845-fails.txt |   68 +
>  drivers/gpu/drm/ci/xfails/msm-sdm845-flakes.txt|   11 +
>  drivers/gpu/drm/ci/xfails/msm-sdm845-skips.txt |2 +
>  .../gpu/drm/ci/xfails/rockchip-rk3288-fails.txt|   

Re: [PULL] drm-misc-next

2023-07-27 Thread Daniel Vetter
On Fri, Jul 21, 2023 at 04:50:44PM +0200, Maxime Ripard wrote:
> Hi,
> 
> Here's this week drm-misc-next PR
> 
> Thanks!
> Maxime
> 
> The following changes since commit 36672dda2eb715af99e9abbcdc400d46598b691c:
> 
>   drm/loongson: Remove a useless check in cursor_plane_atomic_async_check() 
> (2023-07-13 01:24:42 +0800)
> 
> are available in the Git repository at:
> 
>   ssh://git.freedesktop.org/git/drm/drm-misc tags/drm-misc-next-2023-07-21
> 
> for you to fetch changes up to d281eeaa4de2636ff0c8e6ae387bb07b50e5fcbb:
> 
>   drm: adv7511: Fix low refresh rate register for ADV7533/5 (2023-07-21 
> 13:37:18 +0200)

Pulled, thanks.
-Sima

> 
> 
> drm-misc-next for 6.6:
> 
> UAPI Changes:
>   - syncobj: New DRM_IOCTL_SYNCOBJ_EVENTFD ioctl
> 
> Cross-subsystem Changes:
>   - Converge to use of_device_uevent()
> 
> Core Changes:
>   - GPU VA Manager
>   - improvements to make it clearer that drm_minor_type is uAPI
> 
> Driver Changes:
>   - ssd130x: Improve intermediate buffer size computation
>   - bridges:
> - adv7511: Fix low refresh rate
> - anx7625: Switch to macros instead of hardcoded values
>   - panel:
> - ld9040: Backlight support, magic improved
> 
> 
> Bogdan Togorean (1):
>   drm: adv7511: Fix low refresh rate register for ADV7533/5
> 
> Chen-Yu Tsai (2):
>   drm/bridge: anx7625: Use common macros for DP power sequencing commands
>   drm/bridge: anx7625: Use common macros for HDCP capabilities
> 
> Danilo Krummrich (2):
>   drm: manager to keep track of GPUs VA mappings
>   drm: debugfs: provide infrastructure to dump a DRM GPU VA space
> 
> Javier Martinez Canillas (1):
>   drm/ssd130x: Change pixel format used to compute the buffer size
> 
> Marek Vasut (1):
>   drm/panel: simple: Drop prepared_time
> 
> Miquel Raynal (2):
>   of: module: Export of_device_uevent()
>   gpu: host1x: Stop open-coding of_device_uevent()
> 
> Paul Cercueil (2):
>   drm/panel: ld9040: Use better magic values
>   drm/panel: ld9040: Register a backlight device
> 
> Rob Herring (2):
>   gpu/host1x: Explicitly include correct DT includes
>   drm: Explicitly include correct DT includes
> 
> Simon Ser (3):
>   drm/drv: use enum drm_minor_type when appropriate
>   drm/file: use explicit values for enum drm_minor_type
>   drm/syncobj: add IOCTL to register an eventfd
> 
> Steven Price (2):
>   drm: manager: Fix printk format for size_t
>   drm: debugfs: Silence warning from cast
> 
>  Documentation/gpu/drm-mm.rst   |   36 +
>  drivers/gpu/drm/Makefile   |1 +
>  drivers/gpu/drm/arm/display/komeda/komeda_dev.c|2 +-
>  drivers/gpu/drm/arm/malidp_drv.c   |1 +
>  drivers/gpu/drm/bridge/adv7511/adv7511_cec.c   |1 -
>  drivers/gpu/drm/bridge/adv7511/adv7511_drv.c   |   11 +-
>  drivers/gpu/drm/bridge/analogix/anx7625.c  |   12 +-
>  drivers/gpu/drm/bridge/cadence/cdns-dsi-core.c |3 +-
>  .../gpu/drm/bridge/cadence/cdns-mhdp8546-core.c|1 -
>  drivers/gpu/drm/bridge/chipone-icn6211.c   |2 +-
>  drivers/gpu/drm/bridge/display-connector.c |1 -
>  drivers/gpu/drm/bridge/fsl-ldb.c   |1 -
>  drivers/gpu/drm/bridge/imx/imx8qm-ldb.c|2 +-
>  drivers/gpu/drm/bridge/imx/imx8qxp-ldb.c   |1 +
>  drivers/gpu/drm/bridge/lontium-lt9211.c|1 -
>  drivers/gpu/drm/bridge/lvds-codec.c|1 -
>  drivers/gpu/drm/bridge/nwl-dsi.c   |2 +-
>  drivers/gpu/drm/bridge/parade-ps8622.c |1 -
>  drivers/gpu/drm/bridge/samsung-dsim.c  |3 +-
>  drivers/gpu/drm/bridge/simple-bridge.c |3 +-
>  drivers/gpu/drm/bridge/synopsys/dw-hdmi.c  |2 +-
>  drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c  |2 +-
>  drivers/gpu/drm/bridge/ti-sn65dsi83.c  |2 +-
>  drivers/gpu/drm/drm_debugfs.c  |   40 +
>  drivers/gpu/drm/drm_drv.c  |8 +-
>  drivers/gpu/drm/drm_gem.c  |3 +
>  drivers/gpu/drm/drm_gpuva_mgr.c| 1725 
> 
>  drivers/gpu/drm/drm_internal.h |2 +
>  drivers/gpu/drm/drm_ioctl.c|2 +
>  drivers/gpu/drm/drm_mipi_dsi.c |1 +
>  drivers/gpu/drm/drm_syncobj.c  |  148 +-
>  drivers/gpu/drm/etnaviv/etnaviv_gpu.c  |2 +-
>  drivers/gpu/drm/exynos/exynos5433_drm_decon.c  |2 +-
>  drivers/gpu/drm/exynos/exynos7_drm_decon.c |1 -
>  drivers/gpu/drm/exynos/exynos_drm_dsi.c|3 +-
>  drivers/gpu/drm/exynos/exynos_drm_fimd.c   |1 -
>  drivers/gpu/drm/exynos/exynos_drm_rotator.c|2 +-
>  

Re: [PULL] drm-misc-next

2023-07-18 Thread Daniel Vetter
On Thu, 13 Jul 2023 at 11:08, Thomas Zimmermann  wrote:
>
> Hi Dave and Daniel,
>
> this is the main pull request for drm-misc-next for what will become
> Linux v6.6. Some noteworthy changes are:
>
>  * GEM got execution contexts that help with locking multiple GEM
>objects at once.
>
>  * All DRM drivers can now self-import their own dma-bufs by default.
>This enables wlroots-based Wayland compositors to run on drivers
>that do not implement full PRIME support.
>
>  * Fbdev userspace interfaces are fully optional. Hopefully distros
>will switch them off by default.
>
>  * There's a new driver for Loongson display controllers.
>
> And of course, there's the usual number of updates, fixes and smaller
> improvements throughout the DRM subsystem.
>
> Best regards
> Thomas
>
> drm-misc-next-2023-07-13:
> drm-misc-next for v6.6:
>
> UAPI Changes:
>
>  * fbdev:
>* Make fbdev userspace interfaces optional; only leaves the
>  framebuffer console active
>
>  * prime:
>* Support dma-buf self-import for all drivers automatically: improves
>  support for many userspace compositors
>
> Cross-subsystem Changes:
>
>  * backlight:
>* Fix interaction with fbdev in several drivers
>
>  * base: Convert struct platform.remove to return void; part of a larger,
>tree-wide effort
>
>  * dma-buf: Acquire reservation lock for mmap() in exporters; part
>of an on-going effort to simplify locking around dma-bufs
>
>  * fbdev:
>* Use Linux device instead of fbdev device in many places
>* Use deferred-I/O helper macros in various drivers
>
>  * i2c: Convert struct i2c from .probe_new to .probe; part of a larger,
>tree-wide effort
>
>  * video:
>* Avoid including 
>
> Core Changes:
>
>  * atomic:
>* Improve logging
>
>  * prime:
>* Remove struct drm_driver.gem_prime_mmap plus driver updates: all
>  drivers now implement this callback with drm_gem_prime_mmap()
>
>  * gem:
>* Support execution contexts: provides locking over multiple GEM
>  objects
>
>  * ttm:
>* Support init_on_free
>* Swapout fixes
>
> Driver Changes:
>
>  * accel:
>* ivpu: MMU updates; Support debugfs
>
>  * ast:
>* Improve device-model detection
>* Cleanups
>
>  * bridge:
>* dw-hdmi: Improve support for YUV420 bus format
>* dw-mipi-dsi: Fix enable/disable of DSI controller
>* lt9611uxc: Use MODULE_FIRMWARE()
>* ps8640: Remove broken EDID code
>* samsung-dsim: Fix command transfer
>* tc358764: Handle HS/VS polarity; Use BIT() macro; Various cleanups
>* Cleanups
>
>  * ingenic:
>* Kconfig REGMAP fixes
>
>  * loongson:
>* Support display controller
>
>  * mgag200:
>* Minor fixes
>
>  * mxsfb:
>* Support disabling overlay planes
>
>  * nouveau:
>* Improve VRAM detection
>* Various fixes and cleanups
>
>  * panel:
>* panel-edp: Support AUO B116XAB01.4
>* Support Visionox R66451 plus DT bindings
>* Cleanups
>
>  * ssd130x:
>* Support per-controller default resolution plus DT bindings
>* Reduce memory-allocation overhead
>* Cleanups
>
>  * tidss:
>* Support TI AM625 plus DT bindings
>* Implement new connector model plus driver updates
>
>  * vkms
>* Improve write-back support
>* Documentation fixes
> The following changes since commit dcb0775d36de28992f56455ab3967b30d380:
>
>   Merge tag 'drm-msm-next-2023-06-18' of 
> https://gitlab.freedesktop.org/drm/msm into drm-next (2023-06-19 16:01:46 
> +1000)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2023-07-13

... forgot to reply. Pulled, thanks a lot!


>
> for you to fetch changes up to 36672dda2eb715af99e9abbcdc400d46598b691c:
>
>   drm/loongson: Remove a useless check in cursor_plane_atomic_async_check() 
> (2023-07-13 01:24:42 +0800)
>
> 
> drm-misc-next for v6.6:
>
> UAPI Changes:
>
>  * fbdev:
>* Make fbdev userspace interfaces optional; only leaves the
>  framebuffer console active
>
>  * prime:
>* Support dma-buf self-import for all drivers automatically: improves
>  support for many userspace compositors
>
> Cross-subsystem Changes:
>
>  * backlight:
>* Fix interaction with fbdev in several drivers
>
>  * base: Convert struct platform.remove to return void; part of a larger,
>tree-wide effort
>
>  * dma-buf: Acquire reservation lock for mmap() in exporters; part
>of an on-going effort to simplify locking around dma-bufs
>
>  * fbdev:
>* Use Linux device instead of fbdev device in many places
>* Use deferred-I/O helper macros in various drivers
>
>  * i2c: Convert struct i2c from .probe_new to .probe; part of a larger,
>tree-wide effort
>
>  * video:
>* Avoid including 
>
> Core Changes:
>
>  * atomic:
>* Improve logging
>
>  * prime:
>* Remove struct drm_driver.gem_prime_mmap plus driver updates: all
>  drivers now implement this callback 

Re: [PULL] drm-misc-next

2023-05-17 Thread Thomas Zimmermann
Ping! This appears to be unmerged. Let me know if there's anything wrong 
with the PR.


Am 11.05.23 um 09:28 schrieb Maxime Ripard:

Hi,

Here's the first drm-misc-next PR for 6.5

Please note that I'll be off for about a month starting next week, and
Thomas has kindly agreed to fill in.

Thanks!
Maxime

drm-misc-next-2023-05-11:
drm-misc-next for 6.5:

UAPI Changes:

Cross-subsystem Changes:
  - arch: Consolidate 

Core Changes:
  - aperture: Ignore firmware framebuffers with non-primary devices
  - fbdev: Use fbdev's I/O helpers
  - sysfs: Expose DRM connector ID
  - tests: More tests for drm_rect

Driver Changes:
  - armada: Implement fbdev emulation as a client
  - bridge:
- fsl-ldb: Support i.MX6SX
- lt9211: Remove blanking packets
- lt9611: Remove blanking packets
- tc358768: Implement input bus formats reporting, fix various
  timings and clocks settings
- ti-sn65dsi86: Implement wait_hpd_asserted
  - nouveau: Improve NULL pointer checks before dereference
  - panel:
- nt36523: Support Lenovo J606F
- st7703: Support Anbernic RG353V-V2
- new panels: InnoLux G070ACE-L01
  - sun4i: Fix MIPI-DSI dotclock
  - vc4: RGB Range toggle property, BT601 and BT2020 support for HDMI
  - vkms: Convert to drmm helpers, Add reflection and rotation support
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:

   Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)

are available in the Git repository at:

   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2023-05-11

for you to fetch changes up to 4795c78768bcbd58d4ffab650674d314dc6dd772:

   drm: sun4i: calculate proper DCLK rate for DSI (2023-05-10 16:03:19 +0200)


drm-misc-next for 6.5:

UAPI Changes:

Cross-subsystem Changes:
  - arch: Consolidate 

Core Changes:
  - aperture: Ignore firmware framebuffers with non-primary devices
  - fbdev: Use fbdev's I/O helpers
  - sysfs: Expose DRM connector ID
  - tests: More tests for drm_rect

Driver Changes:
  - armada: Implement fbdev emulation as a client
  - bridge:
- fsl-ldb: Support i.MX6SX
- lt9211: Remove blanking packets
- lt9611: Remove blanking packets
- tc358768: Implement input bus formats reporting, fix various
  timings and clocks settings
- ti-sn65dsi86: Implement wait_hpd_asserted
  - nouveau: Improve NULL pointer checks before dereference
  - panel:
- nt36523: Support Lenovo J606F
- st7703: Support Anbernic RG353V-V2
- new panels: InnoLux G070ACE-L01
  - sun4i: Fix MIPI-DSI dotclock
  - vc4: RGB Range toggle property, BT601 and BT2020 support for HDMI
  - vkms: Convert to drmm helpers, Add reflection and rotation support


Alexander Stein (1):
   drm/bridge: ti-sn65dsi83: Fix enable error path

Arthur Grillo (5):
   drm/tests: Add test cases for drm_rect_intersect()
   drm/tests: Add test cases for drm_rect_calc_hscale()
   drm/tests: Add test cases for drm_rect_calc_vscale()
   drm/tests: Add test cases for drm_rect_rotate()
   drm/test: Add test cases for drm_rect_rotate_inv()

Brandon Pollack (1):
   Documentation: vkms: clarify devres managed reference cleanup

Brian Norris (2):
   drm/atomic: Allow vblank-enabled + self-refresh "disable"
   drm/rockchip: vop: Leave vblank enabled in self-refresh

Chris Morgan (3):
   dt-bindings: panel: Add Anbernic RG353V-V2 panel compatible
   drm/panel: st7703: Rename CMD_UNKNOWN_C6 to CMD_SETECO
   drm/panel: st7703: Add Anbernic RG353V-V2 Panel Support

Christian König (3):
   drm/scheduler: properly forward fence errors
   drm/scheduler: add drm_sched_entity_error and use rcu for last_scheduled
   drm/scheduler: mark jobs without fence as canceled

Dan Carpenter (2):
   drm/imx/lcdc: fix a NULL vs IS_ERR() bug in probe
   drm/udl: delete dead code

Daniel Vetter (9):
   MAINTAINERS: add drm_bridge for drm bridge maintainers
   drm/gma500: Use drm_aperture_remove_conflicting_pci_framebuffers
   video/aperture: use generic code to figure out the vga default device
   drm/aperture: Remove primary argument
   video/aperture: Only kick vgacon when the pdev is decoding vga
   video/aperture: Move vga handling to pci function
   video/aperture: Drop primary argument
   video/aperture: Only remove sysfb on the default vga pci device
   fbdev: Simplify fb_is_primary_device for x86

Danilo Krummrich (1):
   drm/scheduler: set entity to NULL in drm_sched_entity_pop_job()

Dave Stevenson (7):
   drm/vc4: hdmi: Add Broadcast RGB property to allow override of RGB range
   drm/vc4: hdmi: Rename full range helper
   drm/vc4: hdmi: Swap CSC matrix channels for YUV444
   drm/vc4: hdmi: Rework the CSC matrices organization
   drm/vc4: hdmi: Add a function to retrieve the CSC matrix
   drm/vc4: hdmi: Add BT.601 Support
   

Re: [PULL] drm-misc-next

2023-04-12 Thread Daniel Vetter
On Wed, Apr 12, 2023 at 03:32:30PM +0200, Maarten Lankhorst wrote:
> 
> Good afternoon Daniel, Dave,
> 
> One last pull request for drm-misc-next.
> 
> Small one, so easy to merge. As a result also more likely to eat your
> computer alive. ;)
> 
> Cheers,
> 
> ~Maarten
> 
> drm-misc-next-2023-04-12:
> 
> drm-misc-next for v6.4-rc1:
> 
> Cross-subsystem Changes:
> - Convert MIPI DSIM bridge to yaml.
> 
> Core Changes:
> - Fix UAF race in drm scheduler.
> 
> Driver Changes:
> - Add primary plane positioning support to VKMS.
> - Convert omapdrm fbdev emulation to in-kernel client.
> - Assorted small fixes to vkms, vc4, nouveau, vmwgfx.
> The following changes since commit e44f18c6ff8beef7b2b10592287f0a9766376d9b:
> 
>   drm/ttm: Make the call to ttm_tt_populate() interruptible when faulting
> (2023-04-06 10:01:42 +0200)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2023-04-12

There's non-breakable space in this line, which broke dim and it took me a
while to figure out wtf is going on. Please copypaste more carefully :-)

> for you to fetch changes up to fd35174e13f98f9232c4aa66689816731d34ca28:
> 
>   drm/vmwgfx: remove unused vmw_overlay function (2023-04-11 13:48:55 -0400)

Pulled, thanks

> 
> 
> drm-misc-next for v6.4-rc1:
> 
> Cross-subsystem Changes:
> - Convert MIPI DSIM bridge to yaml.
> 
> Core Changes:
> - Fix UAF race in drm scheduler.
> 
> Driver Changes:
> - Add primary plane positioning support to VKMS.
> - Convert omapdrm fbdev emulation to in-kernel client.
> - Assorted small fixes to vkms, vc4, nouveau, vmwgfx.
> 
> 
> Asahi Lina (1):
>   drm/scheduler: Fix UAF race in drm_sched_entity_push_job()
> 
> Ben Dooks (1):
>   drm/nouveau/mc/ga100: make ga100_mc_device static
> 
> Jagan Teki (1):
>   dt-bindings: bridge: Convert Samsung MIPI DSIM bridge to yaml
> 
> Javier Martinez Canillas (2):
>   drm/vkms: Drop vkms_connector_destroy() wrapper
>   drm/vkms: Remove  include
> 
> Martin Krastev (2):
>   drm/vmwgfx: Drop mksstat_init_record fn as currently unused
>   drm/vmwgfx: Fix Legacy Display Unit atomic drm support
> 
> Maíra Canal (2):
>   drm/vkms: remove the need for the primary plane to be visible
>   drm/vkms: allow the primary plane to be positioned
> 
> Thomas Zimmermann (5):
>   drm/omapdrm: Include 
>   drm/omapdrm: Remove fb from struct omap_fbdev
>   drm/omapdrm: Remove bo from struct omap_fbdev
>   drm/omapdrm: Remove fbdev from struct omap_drm_private
>   drm/omapdrm: Implement fbdev emulation as in-kernel client
> 
> Tom Rix (2):
>   drm/vc4: remove unused render_wait variable
>   drm/vmwgfx: remove unused vmw_overlay function
> 
> Zack Rusin (1):
>   drm/vmwgfx: Print errors when running on broken/unsupported configs
> 
> ruanjinjie (1):
>   drm/nouveau/disp: make gv100_disp_core_mthd_base static
> 
>  .../bindings/display/bridge/samsung,mipi-dsim.yaml | 255
> +
>  .../bindings/display/exynos/exynos_dsim.txt    |  92 
>  MAINTAINERS    |   1 +
>  drivers/gpu/drm/nouveau/nvkm/engine/disp/gv100.c   |   2 +-
>  drivers/gpu/drm/nouveau/nvkm/subdev/mc/ga100.c |   2 +-
>  drivers/gpu/drm/omapdrm/omap_debugfs.c |   6 +-
>  drivers/gpu/drm/omapdrm/omap_drv.c |  13 +-
>  drivers/gpu/drm/omapdrm/omap_drv.h |   3 -
>  drivers/gpu/drm/omapdrm/omap_fbdev.c   | 163 -
>  drivers/gpu/drm/omapdrm/omap_fbdev.h   |   9 +-
>  drivers/gpu/drm/scheduler/sched_entity.c   |  11 +-
>  drivers/gpu/drm/vc4/vc4_irq.c  |   2 -
>  drivers/gpu/drm/vkms/vkms_output.c |  15 +-
>  drivers/gpu/drm/vkms/vkms_plane.c  |  10 +-
>  drivers/gpu/drm/vmwgfx/vmwgfx_drv.c    |  29 +++
>  drivers/gpu/drm/vmwgfx/vmwgfx_drv.h    |   2 +
>  drivers/gpu/drm/vmwgfx/vmwgfx_kms.c    |  62 +
>  drivers/gpu/drm/vmwgfx/vmwgfx_kms.h    |   5 -
>  drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c    |  45 +++-
>  drivers/gpu/drm/vmwgfx/vmwgfx_msg.c    |  35 +--
>  drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c    |   6 -
>  21 files changed, 465 insertions(+), 303 deletions(-)
>  create mode 100644
> Documentation/devicetree/bindings/display/bridge/samsung,mipi-dsim.yaml
>  delete mode 100644
> Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch


Re: [PULL] drm-misc-next

2023-04-03 Thread Daniel Vetter
On Fri, Mar 31, 2023 at 05:42:25PM +0200, Maarten Lankhorst wrote:
> Hi Dave, Daniel,
> 
> Small update. Slow week. Felt like sending a pull request regardless.
> 
> drm-misc-next-2023-03-31:
> drm-misc-next for v6.4-rc1:
> 
> Cross-subsystem Changes:
> - DT bindings update for adding Mali MT81xx devices.
> - Assorted DT binding updates.
> 
> Core Changes:
> - Documentation update to scheduler.
> 
> Driver Changes:
> - Add support for the same mali devices.
> - Add support for speed binning to panfrost.
> - Add B133UAN01.0 eDP panel.
> - Assorted small fixes to bridge/ps8640, bridge/it6505, panel/magnachip.
> - Use of_property_read_bool in ps8622 and ofdrm.
> The following changes since commit 82bbec189ab34873688484cd14189a5392946fbb:
> 
>   Merge v6.3-rc4 into drm-next (2023-03-29 16:00:23 +0200)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2023-03-31
> 
> for you to fetch changes up to 7d690f936e9bc9fbd6394fb3d4ad181af03ee393:
> 
>   drm/panfrost: Add basic support for speed binning (2023-03-31 11:44:11 
> +0200)

Pulled, thanks.
> 
> 
> drm-misc-next for v6.4-rc1:
> 
> Cross-subsystem Changes:
> - DT bindings update for adding Mali MT81xx devices.
> - Assorted DT binding updates.
> 
> Core Changes:
> - Documentation update to scheduler.
> 
> Driver Changes:
> - Add support for the same mali devices.
> - Add support for speed binning to panfrost.
> - Add B133UAN01.0 eDP panel.
> - Assorted small fixes to bridge/ps8640, bridge/it6505, panel/magnachip.
> - Use of_property_read_bool in ps8622 and ofdrm.
> 
> 
> Alyssa Rosenzweig (3):
>   drm/panfrost: Increase MAX_PM_DOMAINS to 5
>   drm/panfrost: Add the MT8192 GPU ID
>   drm/panfrost: Add mediatek,mt8192-mali compatible
> 
> AngeloGioacchino Del Regno (11):
>   dt-bindings: gpu: mali-bifrost: Split out MediaTek power-domains 
> variation
>   dt-bindings: gpu: mali-bifrost: Set power-domains maxItems to 5
>   dt-bindings: gpu: mali-bifrost: Fix power-domain-names validation
>   dt-bindings: gpu: mali-bifrost: Add sub-schema for MT8192's power 
> domains
>   dt-bindings: gpu: mali-bifrost: Add new MT8183 compatible
>   dt-bindings: gpu: mali-bifrost: Add support for MediaTek MT8186
>   dt-bindings: gpu: mali-bifrost: Add compatible for MT8195 SoC
>   drm/panfrost: Add new compatible for Mali on the MT8183 SoC
>   drm/panfrost: Add support for Mali on the MT8186 SoC
>   dt-bindings: gpu: mali-bifrost: Document nvmem for speedbin support
>   drm/panfrost: Add basic support for speed binning
> 
> Bjorn Andersson (1):
>   drm/panel-edp: Add B133UAN01.0 edp panel entry
> 
> Caio Novais (1):
>   drm/scheduler: Fix variable name in function description
> 
> Dan Carpenter (1):
>   drm/panel: magnachip: Prevent error pointer dereference in probe
> 
> Fabio Estevam (1):
>   dt-bindings: display: seiko,43wvf1g: Change the maintainer's contact
> 
> Hsin-Yi Wang (1):
>   drm/bridge: it6505: Add range and selector_reg
> 
> Krzysztof Kozlowski (6):
>   dt-bindings: display: panel-simple: merge Innolux p120zdg-bf1
>   dt-bindings: display: novatek,nt36672a: correct VDDIO supply
>   dt-bindings: display: panel-simple-dsi: allow vddio variant
>   dt-bindings: display: panel-simple-dsi: document port
>   dt-bindings: display: visionox,rm69299: document reg
>   dt-bindings: display: boe,tv101wum-nl6: document rotation
> 
> Maarten Lankhorst (1):
>   Merge remote-tracking branch 'drm/drm-next' into drm-misc-next
> 
> Pin-yen Lin (3):
>   drm/bridge: ps8640: Skip redundant bridge enable
>   drm/bridge: ps8640: Add a cache for EDID
>   drm/bridge: ps8640: Return NULL immediately when EDID read fail
> 
> Rob Herring (3):
>   dt-bindings: display: Drop unneeded quotes
>   drm: Use of_property_present() for testing DT property presence
>   drm: Use of_property_read_bool() for boolean properties
> 
>  .../bindings/auxdisplay/holtek,ht16k33.yaml|  2 +-
>  .../bindings/display/amlogic,meson-dw-hdmi.yaml|  4 +-
>  .../bindings/display/amlogic,meson-vpu.yaml|  4 +-
>  .../bindings/display/bridge/analogix,anx7625.yaml  |  4 +-
>  .../bindings/display/bridge/cdns,mhdp8546.yaml |  4 +-
>  .../bindings/display/bridge/nxp,ptn3460.yaml   |  2 +-
>  .../bindings/display/bridge/toshiba,tc358767.yaml  |  2 +-
>  .../devicetree/bindings/display/dp-aux-bus.yaml|  2 +-
>  .../bindings/display/imx/nxp,imx8mq-dcss.yaml  |  4 +-
>  .../bindings/display/mediatek/mediatek,hdmi.yaml   |  2 +-
>  .../bindings/display/msm/dsi-controller-main.yaml  |  8 +-
>  .../bindings/display/msm/dsi-phy-10nm.yaml |  2 +-
>  .../devicetree/bindings/display/msm/gmu.yaml   |  4 +-
>  .../devicetree/bindings/display/msm/gpu.yaml   |  4 +-
>  

Re: [PULL] drm-misc-next

2023-03-24 Thread Daniel Vetter
On Thu, Mar 23, 2023 at 12:08:57PM +0100, Maarten Lankhorst wrote:
> Hi Dave, Daniel,
> 
> Lots of small commits with cleanup and fixes this time around, nothing major 
> otherwise.
> 
> Cheers,
> ~Maarten
> 
> drm-misc-next-2023-03-23:
> drm-misc-next for v6.4-rc1:
> 
> Core Changes:
> - Add unit test for xrgb to mono.
> - Assorted small fixes to format helper selftests.
> - Assorted documentation updates.
> - Drop drm_dev_set_unique.
> - Always use shadow buffer in generic fbdev emulation helpers, and
>   improve error handling.
> 
> Driver Changes:
> - Assorted small fixes to malidp, hdlcd, gma500, lima, bridge, rockchip.
> - Move fbdev in gma500 to use drm_client.
> - Convert bridge platform callbacks to void return.
> - Drop leftover from vgem to shmem helper conversion.
> 
> The following changes since commit b24343eaceedb902c1625854f85a193b0549d85f:
> 
>   drm/nouveau/nvfw/acr: set wpr_generic_header_dump storage-class-specifier 
> to static (2023-03-16 14:53:15 +0100)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2023-03-23

Pulled, thanks

> 
> for you to fetch changes up to 4ab9157c7e02019fa8d8ab98d4f9e67e6a7cfad1:
> 
>   drm/rockchip: vop2: Add error check to devm_regmap_init_mmio (2023-03-23 
> 00:18:58 +0100)
> 
> 
> drm-misc-next for v6.4-rc1:
> 
> Core Changes:
> - Add unit test for xrgb to mono.
> - Assorted small fixes to format helper selftests.
> - Assorted documentation updates.
> - Drop drm_dev_set_unique.
> - Always use shadow buffer in generic fbdev emulation helpers, and
>   improve error handling.
> 
> Driver Changes:
> - Assorted small fixes to malidp, hdlcd, gma500, lima, bridge, rockchip.
> - Move fbdev in gma500 to use drm_client.
> - Convert bridge platform callbacks to void return.
> - Drop leftover from vgem to shmem helper conversion.
> 
> 
> Adam Ford (1):
>   drm/bridge: adv7533: Fix adv7533_mode_valid for adv7533 and adv7535
> 
> Alfredo Cruz (1):
>   drm/rockchip: vop2: Add error check to devm_regmap_init_mmio
> 
> Arthur Grillo (2):
>   drm/format-helper: Add Kunit tests for drm_fb_xrgb_to_mono()
>   drm/format-helper: Make "destination_pitch" test usable for mono
> 
> Christian König (1):
>   drm: remove drm_dev_set_unique
> 
> Javier Martinez Canillas (1):
>   drm/format-helper: Use drm_format_info_min_pitch() in tests helper
> 
> Lee Jones (1):
>   drm/ttm/ttm_bo: Provide a missing 'bulk' description and correct 
> misnaming of 'placement'
> 
> Maíra Canal (2):
>   drm/vgem: Drop struct drm_vgem_gem_object
>   drm/lima: Use drm_sched_job_add_syncobj_dependency()
> 
> Petr Tesarik (1):
>   drm/prime: Fix documentation of drm_gem_prime_fd_to_handle()
> 
> Simon Ser (1):
>   drm: fix typo in margin connector properties docs
> 
> Thomas Zimmermann (15):
>   drm/gma500: Remove unnecessary include statements
>   drm/gma500: Move fbdev code into separate source file
>   drm/gma500: Remove fbdev vma open and close callbacks
>   drm/gma500: Fix naming in fb_ops
>   drm/gma500: Inline psbfb_create() into psbfb_probe()
>   drm/gma500: Implement client-based fbdev emulation
>   drm/gma500: Pass fb_info to psb_fbdev_vm_fault()
>   drm/fbdev-generic: Always use shadow buffering
>   drm/fbdev-generic: Remove unused prefer_shadow_fbdev flag
>   drm/fb-helper: Export drm_fb_helper_release_info()
>   drm/fb-helper: Support smem_len in deferred I/O
>   drm/fbdev-generic: Set screen size to size of GEM buffer
>   drm/fbdev-generic: Clean up after failed probing
>   drm/fb-helper: Consolidate CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM
>   drm/fbdev-generic: Rename symbols
> 
> Toby Chen (1):
>   drm/rockchip: dw_hdmi: cleanup drm encoder during unbind
> 
> Tom Rix (3):
>   gpu: drm: bridge: sii9234: remove unused bridge_to_sii9234 function
>   drm/gma500: remove unused gma_pipe_event function
>   drm/rockchip: vop2: fix uninitialized variable possible_crtcs
> 
> Uwe Kleine-König (17):
>   drm/bridge: cdns-dsi: Convert to platform remove callback returning void
>   drm/bridge: display-connector: Convert to platform remove callback 
> returning void
>   drm/bridge: fsl-ldb: Convert to platform remove callback returning void
>   drm/bridge: imx8qm-ldb: Convert to platform remove callback returning 
> void
>   drm/bridge: imx8qxp-ldb: Convert to platform remove callback returning 
> void
>   drm/bridge: imx8qxp-pixel-combiner: Convert to platform remove callback 
> returning void
>   drm/bridge: imx8qxp-pixel-link: Convert to platform remove callback 
> returning void
>   drm/bridge: imx8qxp-pxl2dpi: Convert to platform remove callback 
> returning void
>   drm/bridge: lvds-codec: Convert to platform remove callback returning 
> void
>   

Re: [PULL] drm-misc-next-fixes

2023-02-23 Thread Maxime Ripard
Hi Maarten,

On Thu, Feb 23, 2023 at 07:25:23PM +0100, Maarten Lankhorst wrote:
> Hi Dave and Daniel,
> 
> Here's the first pull request for v6.4-rc1.
> 
> Enjoy!
> 
> ~Maarten
> 
> drm-misc-next-2023-02-23:
> drm-misc-next for v6.4-rc1:
> 
> First pull request to keep the delta from growing too big.

This isn't drm-misc-next-fixes but drm-misc-next?

Maxime


signature.asc
Description: PGP signature


RE: [PULL] drm-misc-next

2023-02-02 Thread Deucher, Alexander
[Public]

> -Original Message-
> From: dim-tools  On Behalf Of
> John Paul Adrian Glaubitz
> Sent: Monday, January 23, 2023 10:01 AM
> To: tzimmerm...@suse.de
> Cc: tvrtko.ursu...@linux.intel.com; dim-to...@lists.freedesktop.org;
> daniel.vet...@ffwll.ch; intel-...@lists.freedesktop.org; dri-
> de...@lists.freedesktop.org; rodrigo.v...@intel.com; airl...@gmail.com
> Subject: Re: [PULL] drm-misc-next
> 
> Hi Thomas!
> 
> > Driver Changes:
> >
> >  * Remove obsolete drivers for userspace modesetting i810, mga, r128,
> >savage, sis, tdfx, via
> 
> Is the Rage 128 GPU still supported via the generic modesetting driver?
> 
> I'm asking because, we're still supporting PowerMacs in Debian Ports of
> which some of those are sporting a Rage 128 GPU. Similar question applies to
> the
> i810 GPU used in some old ThinkPads, for example.

These are not KMS drivers.  They are just the kernel component needed for 3D 
rendering.  These drivers have nothing to do with driving the displays on these 
cards.  For display support you need to use the old Xorg DDXs for these cards 
or the relevant non-DRM fbdev drivers.

Alex

> 
> Thanks,
> Adrian
> 
> --
>   .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer
> `. `'   Physicist
>`-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


Re: [PULL] drm-misc-next

2023-01-24 Thread Daniel Vetter
On Thu, Jan 19, 2023 at 09:47:15AM +0100, Thomas Zimmermann wrote:
> Hi Dave and Daniel,
> 
> this is the weekly PR for drm-misc-next. This big change is that the
> old drivers for userspace modesetting have been removed. Nouveau has
> also lost support for these old ioctls and is therefore now requiring
> libdrm 2.4.33.
> 
> Best regards
> Thomas
> 
> drm-misc-next-2023-01-19:
> drm-misc-next for v6.3:
> 
> UAPI Changes:
> 
> Cross-subsystem Changes:
> 
> Core Changes:
> 
>  * Cleanup unneeded include statements wrt , 
>and 
> 
>  * Remove unused helper DRM_DEBUG_KMS_RATELIMITED()
> 
>  * fbdev: Remove obsolete aperture field from struct fb_device, plus
>driver cleanups; Remove unused flag FBINFO_MISC_FIRMWARE
> 
>  * MIPI-DSI: Fix brightness, plus rsp. driver updates
> 
>  * scheduler: Deprecate drm_sched_resubmit_jobs()
> 
>  * ttm: Fix MIPS build; Remove ttm_bo_wait(); Documentation fixes
> 
> Driver Changes:
> 
>  * Remove obsolete drivers for userspace modesetting i810, mga, r128,
>savage, sis, tdfx, via
> 
>  * bridge: Support CDNS DSI J721E, plus DT bindings; lt9611: Various
>fixes and improvements; sil902x: Various fixes; Fixes
> 
>  * nouveau: Removed support for legacy ioctls; Replace zero-size array;
>Cleanups
> 
>  * panel: Fixes
> 
>  * radeon: Use new DRM logging helpers
> The following changes since commit 6e41acd2e5353c5362e0d5c2f5ba495c54ff555e:
> 
>   drm/vkms: reintroduce prepare_fb and cleanup_fb functions (2023-01-12 
> 09:46:19 -0100)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2023-01-19

Pulled, thanks a lot.
-Daniel

> 
> for you to fetch changes up to bd43a9844bc6f78e00fdc91db47f6969d10c5ac5:
> 
>   drm: bridge: ldb: Warn if LDB clock does not match requested link frequency 
> (2023-01-19 08:50:50 +0100)
> 
> 
> drm-misc-next for $kernel-version:
> 
> UAPI Changes:
> 
> Cross-subsystem Changes:
> 
> Core Changes:
> 
>  * Cleanup unneeded include statements wrt , 
>and 
> 
>  * Remove unused helper DRM_DEBUG_KMS_RATELIMITED()
> 
>  * fbdev: Remove obsolete aperture field from struct fb_device, plus
>driver cleanups; Remove unused flag FBINFO_MISC_FIRMWARE
> 
>  * MIPI-DSI: Fix brightness, plus rsp. driver updates
> 
>  * scheduler: Deprecate drm_sched_resubmit_jobs()
> 
>  * ttm: Fix MIPS build; Remove ttm_bo_wait(); Documentation fixes
> 
> Driver Changes:
> 
>  * Remove obsolete drivers for userspace modesetting i810, mga, r128,
>savage, sis, tdfx, via
> 
>  * bridge: Support CDNS DSI J721E, plus DT bindings; lt9611: Various
>fixes and improvements; sil902x: Various fixes; Fixes
> 
>  * nouveau: Removed support for legacy ioctls; Replace zero-size array;
>Cleanups
> 
>  * panel: Fixes
> 
>  * radeon: Use new DRM logging helpers
> 
> 
> Alexander Stein (2):
>   drm/bridge: sii902x: Use dev_err_probe
>   drm: bridge: ldb: Warn if LDB clock does not match requested link 
> frequency
> 
> Arnd Bergmann (1):
>   drm: panel: visionox: add backlight dependency
> 
> Biju Das (1):
>   dt-bindings: display: bridge: renesas,rzg2l-mipi-dsi: Document RZ/V2L 
> support
> 
> Cai Huoqing (10):
>   drm: Remove the obsolete driver-i810
>   drm: Remove the obsolete driver-mga
>   drm: Remove the obsolete driver-r128
>   drm: Remove the obsolete driver-savage
>   drm: Remove the obsolete driver-sis
>   drm: Remove the obsolete driver-tdfx
>   drm: Remove the obsolete driver-via
>   drm: Add comments to Kconfig
>   drm: Remove some obsolete drm pciids(tdfx, mga, i810, savage, r128, 
> sis, via)
>   MAINTAINERS: Remove some obsolete drivers info(tdfx, mga, i810, savage, 
> r128, sis)
> 
> Christian König (5):
>   drm/ttm: fix some minor kerneldoc issues
>   drm/scheduler: cleanup define
>   drm/scheduler: deprecate drm_sched_resubmit_jobs
>   drm/nouveau: stop using ttm_bo_wait
>   drm/ttm/vmwgfx: move ttm_bo_wait into VMWGFX
> 
> Daniel Mentz (1):
>   drm/mipi-dsi: Fix byte order of 16-bit DCS set/get brightness
> 
> Dmitry Baryshkov (13):
>   drm/bridge: lt9611: fix sleep mode setup
>   drm/bridge: lt9611: fix HPD reenablement
>   drm/bridge: lt9611: fix polarity programming
>   drm/bridge: lt9611: fix programming of video modes
>   drm/bridge: lt9611: fix clock calculation
>   drm/bridge: lt9611: pass a pointer to the of node
>   drm/bridge: lt9611: rework the mode_set function
>   drm/bridge: lt9611: attach to the next bridge
>   drm/bridge: lt9611: fix sync polarity for DVI output
>   drm/bridge: lt9611: simplify video timings programming
>   drm/bridge: lt9611: rework infoframes handling
>   drm/bridge: lt9611: stop filtering modes via the table
>   drm/bridge: lt9611: properly program the dual host mode
> 
> Kees Cook (1):
>  

Re: [PULL] drm-misc-next

2023-01-23 Thread John Paul Adrian Glaubitz

Hi Thomas!

On 1/23/23 16:35, Thomas Zimmermann wrote:

The only thing that is not supported any longer is hardware-accelerated 3d 
rendering.
However, this has not worked anyway, as Mesa has dropped support for those 
chips a long
time ago.


Correct me if I'm wrong, but I thought that's what Mesa Classic was forked off 
for?


AFAIK Mesa classic is for old radeon, i915 and old nouveau code. The so-called 
amber branch:

  https://docs.mesa3d.org/amber.html

But the removed code is for even older hardware.

  https://docs.mesa3d.org/systems.html#deprecated-systems-and-drivers


OK, thanks a lot for the clarification!

I'm glad the 2D drivers will still work and it seems that news article on 
Phoronix [1] is
a little misleading as from reading the it, it seems that driver support for 
the afore-
mentioned hardware is dropped completely which is it not the case.

Thanks,
Adrian


[1] https://www.phoronix.com/news/Linux-6.3-Dropping-Old-DRM


--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Re: [PULL] drm-misc-next

2023-01-23 Thread Thomas Zimmermann

Hi

Am 23.01.23 um 16:23 schrieb John Paul Adrian Glaubitz:

Hi Thomas!

On 1/23/23 16:13, Thomas Zimmermann wrote:

Driver Changes:

 * Remove obsolete drivers for userspace modesetting i810, mga, r128,
   savage, sis, tdfx, via


Is the Rage 128 GPU still supported via the generic modesetting driver?

I'm asking because, we're still supporting PowerMacs in Debian Ports 
of which
some of those are sporting a Rage 128 GPU. Similar question applies 
to the

i810 GPU used in some old ThinkPads, for example.


Yes, all of those chips are still supported by the generic modesetting 
drivers

and even the old userspace Xorg drivers.


OK, good to know.

The only thing that is not supported any longer is 
hardware-accelerated 3d rendering.
However, this has not worked anyway, as Mesa has dropped support for 
those chips a long

time ago.


Correct me if I'm wrong, but I thought that's what Mesa Classic was 
forked off for?


AFAIK Mesa classic is for old radeon, i915 and old nouveau code. The 
so-called amber branch:


 https://docs.mesa3d.org/amber.html

But the removed code is for even older hardware.

 https://docs.mesa3d.org/systems.html#deprecated-systems-and-drivers

Best regards
Thomas




Thanks,
Adrian



--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev


OpenPGP_signature
Description: OpenPGP digital signature


Re: [PULL] drm-misc-next

2023-01-23 Thread John Paul Adrian Glaubitz

Hi Thomas!

On 1/23/23 16:13, Thomas Zimmermann wrote:

Driver Changes:

 * Remove obsolete drivers for userspace modesetting i810, mga, r128,
   savage, sis, tdfx, via


Is the Rage 128 GPU still supported via the generic modesetting driver?

I'm asking because, we're still supporting PowerMacs in Debian Ports of which
some of those are sporting a Rage 128 GPU. Similar question applies to the
i810 GPU used in some old ThinkPads, for example.


Yes, all of those chips are still supported by the generic modesetting drivers
and even the old userspace Xorg drivers.


OK, good to know.


The only thing that is not supported any longer is hardware-accelerated 3d 
rendering.
However, this has not worked anyway, as Mesa has dropped support for those 
chips a long
time ago.


Correct me if I'm wrong, but I thought that's what Mesa Classic was forked off 
for?

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Re: [PULL] drm-misc-next

2023-01-23 Thread Thomas Zimmermann

Hi

Am 23.01.23 um 16:00 schrieb John Paul Adrian Glaubitz:

Hi Thomas!


Driver Changes:

 * Remove obsolete drivers for userspace modesetting i810, mga, r128,
   savage, sis, tdfx, via


Is the Rage 128 GPU still supported via the generic modesetting driver?

I'm asking because, we're still supporting PowerMacs in Debian Ports of 
which

some of those are sporting a Rage 128 GPU. Similar question applies to the
i810 GPU used in some old ThinkPads, for example.


Yes, all of those chips are still supported by the generic modesetting 
drivers and even the old userspace Xorg drivers. The only thing that is 
not supported any longer is hardware-accelerated 3d rendering. However, 
this has not worked anyway, as Mesa has dropped support for those chips 
a long time ago.


Best regards
Thomas



Thanks,
Adrian



--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev


OpenPGP_signature
Description: OpenPGP digital signature


Re: [PULL] drm-misc-next

2023-01-23 Thread John Paul Adrian Glaubitz

Hi Thomas!


Driver Changes:

 * Remove obsolete drivers for userspace modesetting i810, mga, r128,
   savage, sis, tdfx, via


Is the Rage 128 GPU still supported via the generic modesetting driver?

I'm asking because, we're still supporting PowerMacs in Debian Ports of which
some of those are sporting a Rage 128 GPU. Similar question applies to the
i810 GPU used in some old ThinkPads, for example.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Re: [PULL] drm-misc-next

2023-01-04 Thread Daniel Vetter
On Tue, Jan 03, 2023 at 11:51:46AM +0100, Thomas Zimmermann wrote:
> Hi Dave and Daniel,
> 
> here's the first PR for drm-misc-next for the upcomming version v6.3
> of the Linux kernel. Overall, it's fairly small; due to holidays, I
> guess. Noteworthy changes are in connector TV-mode handling, KUnit tests
> and MIPI helpers.
> 
> Best regards
> Thomas
> 
> drm-misc-next-2023-01-03:
> drm-misc-next for v6.3:
> 
> UAPI Changes:
> 
>  * connector: Support analog-TV mode property
> 
>  * media: Add MEDIA_BUS_FMT_RGB565_1X24_CPADHI,
>MEDIA_BUS_FMT_RGB666_1X18 and MEDIA_BUS_FMT_RGB666_1X24_CPADHI
> 
> Cross-subsystem Changes:
> 
>  * dma-buf: Documentation fixes
> 
>  * i2c: Introduce i2c_client_get_device_id() helper
> 
> Core Changes:
> 
>  * Improve support for analog TV output
> 
>  * bridge: Remove unused drm_bridge_chain functions
> 
>  * debugfs: Add per-device helpers and convert various DRM drivers
> 
>  * dp-mst: Various fixes
> 
>  * fbdev emulation: Always pick 32 bpp as default
> 
>  * KUnit: Add tests for managed helpers; Various cleanups
> 
>  * panel-orientation: Add quirks for Lenovo Yoga Tab 3 X90F and DynaBook K50
> 
>  * TTM: Open-code ttm_bo_wait() and remove the helper
> 
> Driver Changes:
> 
>  * Fix preferred depth and bpp values throughout DRM drivers
> 
>  * Remove #CONFIG_PM guards throughout DRM drivers
> 
>  * ast: Various fixes
> 
>  * bridge: Implement i2c's probe_new in various drivers; Fixes; ite-it6505:
>Locking fixes, Cache EDID data; ite-it66121: Support IT6610 chip,
>Cleanups; lontium-tl9611: Fix HDMI on DragonBoard 845c; parade-ps8640:
>Use atomic bridge functions
> 
>  * gud: Convert to DRM shadow-plane helpers; Perform flushing synchronously
>during atomic update
> 
>  * ili9486: Support 16-bit pixel data
> 
>  * imx: Split off IPUv3 driver; Various fixes
> 
>  * mipi-dbi: Convert to DRM shadow-plane helpers plus rsp driver changes;
>Support separate I/O-voltage supply
> 
>  * mxsfb: Depend on ARCH_MXS or ARCH_MXC
> 
>  * omapdrm: Various fixes
> 
>  * panel: Use ktime_get_boottime() to measure power-down delay in various
>drivers; Fix auto-suspend delay in various drivers; orisetech-ota5601a:
>Add support
> 
>  * sprd: Cleanups
> 
>  * sun4i: Convert to new TV-mode property
> 
>  * tidss: Various fixes
> 
>  * v3d: Various fixes
> 
>  * vc4: Convert to new TV-mode property; Support Kunit tests; Cleanups;
>dpi: Support RGB565 and RGB666 formats; dsi: Convert DSI driver to
>bridge
> 
>  * virtio: Improve tracing
> 
>  * vkms: Support small cursors in IGT tests; Various fixes
> The following changes since commit d47f9580839eb6fe568e38b2084d94887fbf5ce0:
> 
>   Backmerge tag 'v6.1-rc6' into drm-next (2022-11-24 11:05:43 +1000)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2023-01-03

Pulled to drm-next, thanks
-Daniel

> 
> for you to fetch changes up to 2591939e881cf728b6ac45971eeec2f58051c101:
> 
>   drm/virtio: Spiff out cmd queue/response traces (2023-01-02 17:51:27 +0300)
> 
> 
> drm-misc-next for v6.3:
> 
> UAPI Changes:
> 
>  * connector: Support analog-TV mode property
> 
>  * media: Add MEDIA_BUS_FMT_RGB565_1X24_CPADHI,
>MEDIA_BUS_FMT_RGB666_1X18 and MEDIA_BUS_FMT_RGB666_1X24_CPADHI
> 
> Cross-subsystem Changes:
> 
>  * dma-buf: Documentation fixes
> 
>  * i2c: Introduce i2c_client_get_device_id() helper
> 
> Core Changes:
> 
>  * Improve support for analog TV output
> 
>  * bridge: Remove unused drm_bridge_chain functions
> 
>  * debugfs: Add per-device helpers and convert various DRM drivers
> 
>  * dp-mst: Various fixes
> 
>  * fbdev emulation: Always pick 32 bpp as default
> 
>  * KUnit: Add tests for managed helpers; Various cleanups
> 
>  * panel-orientation: Add quirks for Lenovo Yoga Tab 3 X90F and DynaBook K50
> 
>  * TTM: Open-code ttm_bo_wait() and remove the helper
> 
> Driver Changes:
> 
>  * Fix preferred depth and bpp values throughout DRM drivers
> 
>  * Remove #CONFIG_PM guards throughout DRM drivers
> 
>  * ast: Various fixes
> 
>  * bridge: Implement i2c's probe_new in various drivers; Fixes; ite-it6505:
>Locking fixes, Cache EDID data; ite-it66121: Support IT6610 chip,
>Cleanups; lontium-tl9611: Fix HDMI on DragonBoard 845c; parade-ps8640:
>Use atomic bridge functions
> 
>  * gud: Convert to DRM shadow-plane helpers; Perform flushing synchronously
>during atomic update
> 
>  * ili9486: Support 16-bit pixel data
> 
>  * imx: Split off IPUv3 driver; Various fixes
> 
>  * mipi-dbi: Convert to DRM shadow-plane helpers plus rsp driver changes;i
>Support separate I/O-voltage supply
> 
>  * mxsfb: Depend on ARCH_MXS or ARCH_MXC
> 
>  * omapdrm: Various fixes
> 
>  * panel: Use ktime_get_boottime() to measure power-down delay in various
>drivers; Fix auto-suspend delay in various drivers; orisetech-ota5601a:
>Add support
> 
>  * sprd: Cleanups
> 
>  * 

Re: [PULL] drm-misc-next-fixes

2023-01-03 Thread Daniel Vetter
On Tue, Jan 03, 2023 at 03:49:26PM +0100, Maxime Ripard wrote:
> Hi Daniel, Dave,
> 
> Here's the drm-misc-next-fixes leftovers.
> 
> Maxime
> 
> drm-misc-next-fixes-2023-01-03:
> The drm-misc-next-fixes leftovers. It addresses a bug in drm/scheduler
> ending up causing a lockup, and reduces the stack usage of some drm/mm
> kunit tests.
> The following changes since commit b02897e56b4e1fa6445be695ce5d605bb098435c:
> 
>   Revert "drm/fb-helper: Perform damage handling in deferred-I/O helper" 
> (2022-11-23 09:11:32 +0100)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc 
> tags/drm-misc-next-fixes-2023-01-03

Thanks, pulled.
-Daniel

> 
> for you to fetch changes up to 03dec92c4f788c54a7c01b40a018f601eb8a6c52:
> 
>   drm/scheduler: Fix lockup in drm_sched_entity_kill() (2023-01-02 17:45:18 
> +0300)
> 
> 
> The drm-misc-next-fixes leftovers. It addresses a bug in drm/scheduler
> ending up causing a lockup, and reduces the stack usage of some drm/mm
> kunit tests.
> 
> 
> Arnd Bergmann (1):
>   drm/tests: reduce drm_mm_test stack usage
> 
> Dmitry Osipenko (1):
>   drm/scheduler: Fix lockup in drm_sched_entity_kill()
> 
>  drivers/gpu/drm/scheduler/sched_entity.c | 2 +-
>  drivers/gpu/drm/scheduler/sched_main.c   | 4 ++--
>  drivers/gpu/drm/tests/Makefile   | 2 ++
>  drivers/gpu/drm/tests/drm_mm_test.c  | 6 +++---
>  4 files changed, 8 insertions(+), 6 deletions(-)



-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch


Re: [PULL] drm-misc-next

2022-09-06 Thread Daniel Vetter
On Tue, Sep 06, 2022 at 08:53:25AM +0200, Maarten Lankhorst wrote:
> Hi Dave, Daniel,
> 
> A pull request prepared in Germany and Denmark, but sent from Sweden after 
> fighting with gpg on an infamous bridge.
> 
> My computer's somewhere in my trunk so I just copied someone else's pull 
> request and pretend my laptop is a dev machine that sends pull requests every 
> day works..
> 
> Tag is still correctly signed, hope I didn't mess up anything!

[Dave should be back to handling pulls for everything this Fri]

Applied to drm-next, thanks.
-Daniel

> 
> drm-misc-next-2022-08-20-1:
> drm-misc-next for v6.1:
> 
> UAPI Changes:
> 
> Cross-subsystem Changes:
> - DMA-buf: documentation updates.
> - Assorted small fixes to vga16fb
> - Fix fbdev drivers to use the aperture helpers.
> - Make removal of conflicting drivers work correctly without fbdev enabled.
> 
> Core Changes:
> - bridge, scheduler, dp-mst: Assorted small fixes.
> - Add more format helpers to fourcc, and use it to replace the cpp usage.
> - Add DRM_FORMAT_Cxx, DRM_FORMAT_Rxx (single channel), and DRM_FORMAT_Dxx
>   ("darkness", inverted single channel)
> - Add packed AYUV and XYUV formats.
> - Assorted documentation updates.
> - Rename ttm_bo_init to ttm_bo_init_validate.
> - Allow TTM bo's to exist without backing store.
> - Convert drm selftests to kunit.
> - Add managed init functions for (panel) bridge, crtc, encoder and connector.
> - Fix endianness handling in various format conversion helpers.
> - Make tests pass on big-endian platforms, and add test for rgb888 -> rgb565
> - Move DRM_PLANE_HELPER_NO_SCALING to atomic helpers and rename, so
>   drm_plane_helper is no longer needed in most drivers.
> - Use idr_init_base instead of idr_init.
> - Rename FB and GEM CMA helpers to DMA helpers.
> - Rework XRGB related conversion helpers, and add drm_fb_blit() that
>   takes a iosys_map. Make drm_fb_memcpy take an iosys_map too.
> - Move edid luminance calculation to core, and use it in i915.
> 
> Driver Changes:
> - bridge/{adv7511,ti-sn65dsi86,parade-ps8640}, 
> panel/{simple,nt35510,tc358767},
>   nouveau, sun4i, mipi-dsi, mgag200, bochs, arm, komeda, vmwgfx, pl111:
>   Assorted small fixes and doc updates.
> - vc4: Rework hdmi power up, and depend on PM.
> - panel/simple: Add Samsung LTL101AL01.
> - ingenic: Add JZ4760(B) support, avoid a modeset when sharpness property
>   is unchanged, and use the new PM ops.
> - Revert some amdgpu commits that cause garbaged graphics when starting
>   X, and reapply them with the real problem fixed.
> - Completely rework vc4 init to use managed helpers.
> - Rename via_drv to via_dri1, and move all stuff there only used by the
>   dri1 implementation in preperation for atomic modeset.
> - Use regmap bulk write in ssd130x.
> - Power sequence and clock updates to it6505.
> - Split panel-sitrox-st7701  init sequence and rework mode programming code.
> - virtio: Improve error and edge conditions handling, and convert to use 
> managed
>   helpers.
> - Add Samsung LTL101AL01, B120XAN01.0, R140NWF5 RH, DMT028VGHMCMI-1A T, 
> panels.
> - Add generic fbdev support to komeda.
> - Split mgag200 modeset handling to make it more model-specific.
> - Convert simpledrm to use atomic helpers.
> - Improve udl suspend/disconnect handling.
> The following changes since commit 2bc7ea71a73747a77e7f83bc085b0d2393235410:
> 
>   Merge tag 'topic/nouveau-misc-2022-07-27' of 
> git://anongit.freedesktop.org/drm/drm into drm-next (2022-07-27 11:34:07 
> +1000)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2022-08-20-1
> 
> for you to fetch changes up to 8869fa666a9e6782c3c896c1fa57d65adca23249:
> 
>   drm/virtio: remove drm_plane_cleanup() destroy hook (2022-08-19 16:00:15 
> +0200)
> 
> 
> drm-misc-next for v6.1:
> 
> UAPI Changes:
> 
> Cross-subsystem Changes:
> - DMA-buf: documentation updates.
> - Assorted small fixes to vga16fb
> - Fix fbdev drivers to use the aperture helpers.
> - Make removal of conflicting drivers work correctly without fbdev enabled.
> 
> Core Changes:
> - bridge, scheduler, dp-mst: Assorted small fixes.
> - Add more format helpers to fourcc, and use it to replace the cpp usage.
> - Add DRM_FORMAT_Cxx, DRM_FORMAT_Rxx (single channel), and DRM_FORMAT_Dxx
>   ("darkness", inverted single channel)
> - Add packed AYUV and XYUV formats.
> - Assorted documentation updates.
> - Rename ttm_bo_init to ttm_bo_init_validate.
> - Allow TTM bo's to exist without backing store.
> - Convert drm selftests to kunit.
> - Add managed init functions for (panel) bridge, crtc, encoder and connector.
> - Fix endianness handling in various format conversion helpers.
> - Make tests pass on big-endian platforms, and add test for rgb888 -> rgb565
> - Move DRM_PLANE_HELPER_NO_SCALING to atomic helpers and rename, so
>   drm_plane_helper is no longer needed in most drivers.
> - Use 

Re: [PULL] drm-misc-next

2022-06-24 Thread Daniel Vetter
On Thu, Jun 23, 2022 at 11:56:56AM +0300, Jani Nikula wrote:
> On Thu, 23 Jun 2022, Thomas Zimmermann  wrote:
> > Hi
> >
> > Am 23.06.22 um 10:26 schrieb Jani Nikula:
> >> On Thu, 23 Jun 2022, Thomas Zimmermann  wrote:
> >>> I forgot to mention that we backmerged v5.19-rc2. That's why the list of
> >>> changed files is so long.
> >> 
> >> I thought we should only backmerge Linus' tree via backmerging drm-next,
> >> which avoids this problem altogether.
> >
> > I did backmerge via drm-next.
> 
> Then I'm confused how it all shows up the the diffstat. If you backmerge
> drm-next to drm-misc-next, and then generate your drm-misc-next pull
> request against drm-next (dim pull-request drm-misc-next drm/drm-next),
> I don't think it should show up.

git is shit (tm)

The git commit list will look reasonable, but the diff will make a
complete mess out of non-linear history. I think it's this case here too.

I think the way to fix it is to do a manual test merge and then to a diff
against the first parent (assuming you did the test merge forward, not
backwards). Without the test merge git tries to do some kind of multi-way
diffstat.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch


Re: [PULL] drm-misc-next

2022-06-23 Thread Jani Nikula
On Thu, 23 Jun 2022, Thomas Zimmermann  wrote:
> Hi
>
> Am 23.06.22 um 10:26 schrieb Jani Nikula:
>> On Thu, 23 Jun 2022, Thomas Zimmermann  wrote:
>>> I forgot to mention that we backmerged v5.19-rc2. That's why the list of
>>> changed files is so long.
>> 
>> I thought we should only backmerge Linus' tree via backmerging drm-next,
>> which avoids this problem altogether.
>
> I did backmerge via drm-next.

Then I'm confused how it all shows up the the diffstat. If you backmerge
drm-next to drm-misc-next, and then generate your drm-misc-next pull
request against drm-next (dim pull-request drm-misc-next drm/drm-next),
I don't think it should show up.

BR,
Jani.


>
> Best regards
> Thomas
>
>> 
>> BR,
>> Jani.
>> 
>> 

-- 
Jani Nikula, Intel Open Source Graphics Center


Re: [PULL] drm-misc-next

2022-06-23 Thread Thomas Zimmermann

Hi

Am 23.06.22 um 10:26 schrieb Jani Nikula:

On Thu, 23 Jun 2022, Thomas Zimmermann  wrote:

I forgot to mention that we backmerged v5.19-rc2. That's why the list of
changed files is so long.


I thought we should only backmerge Linus' tree via backmerging drm-next,
which avoids this problem altogether.


I did backmerge via drm-next.

Best regards
Thomas



BR,
Jani.




--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev


OpenPGP_signature
Description: OpenPGP digital signature


Re: [PULL] drm-misc-next

2022-06-23 Thread Jani Nikula
On Thu, 23 Jun 2022, Thomas Zimmermann  wrote:
> I forgot to mention that we backmerged v5.19-rc2. That's why the list of 
> changed files is so long.

I thought we should only backmerge Linus' tree via backmerging drm-next,
which avoids this problem altogether.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center


Re: [PULL] drm-misc-next

2022-06-23 Thread Thomas Zimmermann

Hi

Am 23.06.22 um 10:02 schrieb Thomas Zimmermann:

Hi Dave and Daniel,

here's the drm-misc-next PR for this week.


I forgot to mention that we backmerged v5.19-rc2. That's why the list of 
changed files is so long.


Best regards
Thomas





--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev


OpenPGP_signature
Description: OpenPGP digital signature


Re: [PULL] drm-misc-next

2022-06-15 Thread Daniel Vetter
On Wed, Jun 08, 2022 at 12:34:41PM +0200, Thomas Zimmermann wrote:
> Hi Dave and Daniel,
> 
> here's the first PR for drm-misc-next that will go into v5.20.
> 
> Best regards
> Thomas
> 
> drm-misc-next-2022-06-08:
> drm-misc-next for 5.20:
> 
> UAPI Changes:
> 
>  * connector: export bpc limits in debugfs
> 
>  * dma-buf: Print buffer name in debugfs
> 
> Cross-subsystem Changes:
> 
>  * dma-buf: Improve dma-fence handling; Cleanups
> 
>  * fbdev: Device-unregistering fixes
> 
> Core Changes:
> 
>  * client: Only use driver-validated modes to avoid blank screen
> 
>  * dp-aux: Make probing more reliable; Small fixes
> 
>  * edit: CEA data-block iterators; Introduce struct drm_edid; Many cleanups
> 
>  * gem: Don't use framebuffer format's non-exising color planes
> 
>  * probe-helper: Use 640x480 as DisplayPort fallback; Refactoring
> 
>  * scheduler: Don't kill jobs in interrupt context
> 
> Driver Changes:
> 
>  * amdgpu: Use atomic fence helpers in DM; Fix VRAM address calculation;
>Export CRTC bpc settings via debugfs
> 
>  * bridge: Add TI-DLPC3433;  anx7625: Fixes;  fy07024di26a30d: Optional
>GPIO reset;  icn6211: Cleanups;  ldb: Add reg and reg-name properties
>to bindings, Kconfig fixes;  lt9611: Fix display sensing;  lt9611uxc:
>Fixes;  nwl-dsi: Fixes;  ps8640: Cleanups;  st7735r: Fixes;  tc358767:
>DSI/DPI refactoring and DSI-to-eDP support, Fixes; ti-sn65dsi83:
>Fixes;
> 
>  * gma500: Cleanup connector I2C handling
> 
>  * hyperv: Unify VRAM allocation of Gen1 and Gen2
> 
>  * i915: export CRTC bpc settings via debugfs
> 
>  * meson: Support YUV422 output; Refcount fixes
> 
>  * mgag200: Support damage clipping; Support gamma handling; Protect
>concurrent HW access; Fixes to connector; Store model-specific limits
>in device-info structure; Cleanups
> 
>  * nouveau: Fixes and Cleanups
> 
>  * panel: Kconfig fixes
> 
>  * panfrost: Valhall support
> 
>  * r128: Fix bit-shift overflow
> 
>  * rockchip: Locking fixes in error path; Minor cleanups
> 
>  * ssd130x: Fix built-in linkage
> 
>  * ttm: Cleanups
> 
>  * udl; Always advertize VGA connector
> 
>  * fbdev/vesa: Support COMPILE_TEST
> The following changes since commit 6071c4c2a319da360b0bf2bc397d4fefad10b2c8:
> 
>   drm/qxl: add drm_gem_plane_helper_prepare_fb (2022-05-05 12:30:10 +0200)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2022-06-08
> 
> for you to fetch changes up to dfa687bffc8a4a21ed929c7dececf01b8f1f52ee:
> 
>   drm/bridge: lt9611uxc: Cancel only driver's work (2022-06-07 14:57:47 +0200)

Pulled, thanks.
-Daniel

> 
> 
> drm-misc-next for 5.20:
> 
> UAPI Changes:
> 
>  * connector: export bpc limits in debugfs
> 
>  * dma-buf: Print buffer name in debugfs
> 
> Cross-subsystem Changes:
> 
>  * dma-buf: Improve dma-fence handling; Cleanups
> 
>  * fbdev: Device-unregistering fixes
> 
> Core Changes:
> 
>  * client: Only use driver-validated modes to avoid blank screen
> 
>  * dp-aux: Make probing more reliable; Small fixes
> 
>  * edit: CEA data-block iterators; Introduce struct drm_edid; Many cleanups
> 
>  * gem: Don't use framebuffer format's non-exising color planes
> 
>  * probe-helper: Use 640x480 as DisplayPort fallback; Refactoring
> 
>  * scheduler: Don't kill jobs in interrupt context
> 
> Driver Changes:
> 
>  * amdgpu: Use atomic fence helpers in DM; Fix VRAM address calculation;
>Export CRTC bpc settings via debugfs
> 
>  * bridge: Add TI-DLPC3433;  anx7625: Fixes;  fy07024di26a30d: Optional
>GPIO reset;  icn6211: Cleanups;  ldb: Add reg and reg-name properties
>to bindings, Kconfig fixes;  lt9611: Fix display sensing;  lt9611uxc:
>Fixes;  nwl-dsi: Fixes;  ps8640: Cleanups;  st7735r: Fixes;  tc358767:
>DSI/DPI refactoring and DSI-to-eDP support, Fixes; ti-sn65dsi83:
>Fixes;
> 
>  * gma500: Cleanup connector I2C handling
> 
>  * hyperv: Unify VRAM allocation of Gen1 and Gen2
> 
>  * i915: export CRTC bpc settings via debugfs
> 
>  * meson: Support YUV422 output; Refcount fixes
> 
>  * mgag200: Support damage clipping; Support gamma handling; Protect
>concurrent HW access; Fixes to connector; Store model-specific limits
>in device-info structure; Cleanups
> 
>  * nouveau: Fixes and Cleanups
> 
>  * panel: Kconfig fixes
> 
>  * panfrost: Valhall support
> 
>  * r128: Fix bit-shift overflow
> 
>  * rockchip: Locking fixes in error path; Minor cleanups
> 
>  * ssd130x: Fix built-in linkage
> 
>  * ttm: Cleanups
> 
>  * udl; Always advertize VGA connector
> 
>  * fbdev/vesa: Support COMPILE_TEST
> 
> 
> Alyssa Rosenzweig (9):
>   dt-bindings: Add compatible for Mali Valhall (JM)
>   drm/panfrost: Handle HW_ISSUE_TTRX_2968_TTRX_3162
>   drm/panfrost: Constify argument to has_hw_issue
>   drm/panfrost: Handle HW_ISSUE_TTRX_3076
>   drm/panfrost: 

Re: [PULL] drm-misc-next-fixes

2022-04-07 Thread Maxime Ripard
Hi

On Thu, Apr 07, 2022 at 12:56:27PM +0200, Maarten Lankhorst wrote:
> drm-misc-next-fixes-2022-04-07:
> drm-misc-next-fixes for v5.18-rc2:
> - fix warning about fence containers
> - fix logic error in new fence merge code
> - handle empty dma_fence_arrays gracefully
> - Try all possible cases for bridge/panel detection.
> The following changes since commit 7344bad7fb6daa4877a1c064b52c7d5f9182c41b:
> 
>   drm/edid: fix CEA extension byte #3 parsing (2022-03-24 11:41:14 +0200)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc 
> tags/drm-misc-next-fixes-2022-04-07
> 
> for you to fetch changes up to 67bae5f28c895f8737a1974c3f31cf12b9170b14:
> 
>   drm: of: Properly try all possible cases for bridge/panel detection 
> (2022-03-30 10:16:05 +0200)
> 
> 
> drm-misc-next-fixes for v5.18-rc2:
> - fix warning about fence containers
> - fix logic error in new fence merge code
> - handle empty dma_fence_arrays gracefully
> - Try all possible cases for bridge/panel detection.

I merged it in drm-misc-fixes earlier this week, so drm-misc-fixes is
the only PR that needs to be merged

Maxime


signature.asc
Description: PGP signature


Re: [PULL] drm-misc-next

2022-02-22 Thread Thomas Zimmermann

Hi

Am 01.02.22 um 09:17 schrieb Maarten Lankhorst:

Op 01-02-2022 om 07:38 schreef Dave Airlie:

On Thu, 27 Jan 2022 at 21:57, Maarten Lankhorst
 wrote:

Hi Dave & Daniel,

First pull for v5.18

I was trying to be all efficient and get this pulled in time for once.


However it broke building on my arm test build.

The new DP helper Kconfig is wrong somewhere.

I've attached the .config, but it appears I get DRM_DP_HELPER set to M
but ANALOGIX_DP set to Y and it fails to link because the dp helper
should be Y.

Regards,
Dave.

Below should likely fix it?


I have been trying again just now with the latest drm-tip and cannot 
reproduce the issue with the attached config.


This PR has been long overdue. Maarten, can you please send out an 
update ASAP?


Best regards
Thomas



diff --git a/drivers/gpu/drm/exynos/Kconfig b/drivers/gpu/drm/exynos/Kconfig
index 6a251e3aa779..f27cfd2a9726 100644
--- a/drivers/gpu/drm/exynos/Kconfig
+++ b/drivers/gpu/drm/exynos/Kconfig
@@ -66,6 +66,7 @@ config DRM_EXYNOS_DP
bool "Exynos specific extensions for Analogix DP driver"
depends on DRM_EXYNOS_FIMD || DRM_EXYNOS7_DECON
select DRM_ANALOGIX_DP
+   select DRM_DP_HELPER
default DRM_EXYNOS
select DRM_PANEL
help
diff --git a/drivers/gpu/drm/rockchip/Kconfig b/drivers/gpu/drm/rockchip/Kconfig
index d59dca5efb52..fa5cfda4e90e 100644
--- a/drivers/gpu/drm/rockchip/Kconfig
+++ b/drivers/gpu/drm/rockchip/Kconfig
@@ -8,6 +8,7 @@ config DRM_ROCKCHIP
select DRM_PANEL
select VIDEOMODE_HELPERS
select DRM_ANALOGIX_DP if ROCKCHIP_ANALOGIX_DP
+   select DRM_DP_HELPER if ROCKCHIP_ANALOGIX_DP
select DRM_DW_HDMI if ROCKCHIP_DW_HDMI
select DRM_DW_MIPI_DSI if ROCKCHIP_DW_MIPI_DSI
select GENERIC_PHY if ROCKCHIP_DW_MIPI_DSI



--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev


OpenPGP_signature
Description: OpenPGP digital signature


Re: [PULL] drm-misc-next

2022-02-01 Thread Thomas Zimmermann

Hi

Am 01.02.22 um 09:17 schrieb Maarten Lankhorst:

Op 01-02-2022 om 07:38 schreef Dave Airlie:

On Thu, 27 Jan 2022 at 21:57, Maarten Lankhorst
 wrote:

Hi Dave & Daniel,

First pull for v5.18

I was trying to be all efficient and get this pulled in time for once.


However it broke building on my arm test build.

The new DP helper Kconfig is wrong somewhere.

I've attached the .config, but it appears I get DRM_DP_HELPER set to M
but ANALOGIX_DP set to Y and it fails to link because the dp helper
should be Y.

Regards,
Dave.

Below should likely fix it?

diff --git a/drivers/gpu/drm/exynos/Kconfig b/drivers/gpu/drm/exynos/Kconfig
index 6a251e3aa779..f27cfd2a9726 100644
--- a/drivers/gpu/drm/exynos/Kconfig
+++ b/drivers/gpu/drm/exynos/Kconfig
@@ -66,6 +66,7 @@ config DRM_EXYNOS_DP
bool "Exynos specific extensions for Analogix DP driver"
depends on DRM_EXYNOS_FIMD || DRM_EXYNOS7_DECON
select DRM_ANALOGIX_DP
+   select DRM_DP_HELPER
default DRM_EXYNOS
select DRM_PANEL
help
diff --git a/drivers/gpu/drm/rockchip/Kconfig b/drivers/gpu/drm/rockchip/Kconfig
index d59dca5efb52..fa5cfda4e90e 100644
--- a/drivers/gpu/drm/rockchip/Kconfig
+++ b/drivers/gpu/drm/rockchip/Kconfig
@@ -8,6 +8,7 @@ config DRM_ROCKCHIP
select DRM_PANEL
select VIDEOMODE_HELPERS
select DRM_ANALOGIX_DP if ROCKCHIP_ANALOGIX_DP
+   select DRM_DP_HELPER if ROCKCHIP_ANALOGIX_DP
select DRM_DW_HDMI if ROCKCHIP_DW_HDMI
select DRM_DW_MIPI_DSI if ROCKCHIP_DW_MIPI_DSI
select GENERIC_PHY if ROCKCHIP_DW_MIPI_DSI


Thanks a lot. This fixes the build for me.

Best regards
Thomas





--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev


OpenPGP_signature
Description: OpenPGP digital signature


Re: [PULL] drm-misc-next

2022-02-01 Thread Maarten Lankhorst
Op 01-02-2022 om 07:38 schreef Dave Airlie:
> On Thu, 27 Jan 2022 at 21:57, Maarten Lankhorst
>  wrote:
>> Hi Dave & Daniel,
>>
>> First pull for v5.18
> I was trying to be all efficient and get this pulled in time for once.
>
>
> However it broke building on my arm test build.
>
> The new DP helper Kconfig is wrong somewhere.
>
> I've attached the .config, but it appears I get DRM_DP_HELPER set to M
> but ANALOGIX_DP set to Y and it fails to link because the dp helper
> should be Y.
>
> Regards,
> Dave.
Below should likely fix it?

diff --git a/drivers/gpu/drm/exynos/Kconfig b/drivers/gpu/drm/exynos/Kconfig
index 6a251e3aa779..f27cfd2a9726 100644
--- a/drivers/gpu/drm/exynos/Kconfig
+++ b/drivers/gpu/drm/exynos/Kconfig
@@ -66,6 +66,7 @@ config DRM_EXYNOS_DP
bool "Exynos specific extensions for Analogix DP driver"
depends on DRM_EXYNOS_FIMD || DRM_EXYNOS7_DECON
select DRM_ANALOGIX_DP
+   select DRM_DP_HELPER
default DRM_EXYNOS
select DRM_PANEL
help
diff --git a/drivers/gpu/drm/rockchip/Kconfig b/drivers/gpu/drm/rockchip/Kconfig
index d59dca5efb52..fa5cfda4e90e 100644
--- a/drivers/gpu/drm/rockchip/Kconfig
+++ b/drivers/gpu/drm/rockchip/Kconfig
@@ -8,6 +8,7 @@ config DRM_ROCKCHIP
select DRM_PANEL
select VIDEOMODE_HELPERS
select DRM_ANALOGIX_DP if ROCKCHIP_ANALOGIX_DP
+   select DRM_DP_HELPER if ROCKCHIP_ANALOGIX_DP
select DRM_DW_HDMI if ROCKCHIP_DW_HDMI
select DRM_DW_MIPI_DSI if ROCKCHIP_DW_MIPI_DSI
select GENERIC_PHY if ROCKCHIP_DW_MIPI_DSI



Re: [PULL] drm-misc-next-fixes

2022-01-14 Thread Daniel Vetter
On Fri, Jan 14, 2022 at 03:24:59PM +0100, Thomas Zimmermann wrote:
> Hi Dave and Daniel,
> 
> here are two more fixes for this week. I cherry-picked both from 
> drm-misc-next.
> 
> Best regards
> Thomas
> 
> drm-misc-next-fixes-2022-01-14:
>  * atomic helpers: Fix error messages
>  * mipi-dbi: Fix buffer mapping
> The following changes since commit 5da8b49de472c1da8658466d4f63ef8d9251a819:
> 
>   dt-bindings: display: bridge: lvds-codec: Fix duplicate key (2021-12-22 
> 14:02:04 -0400)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc 
> tags/drm-misc-next-fixes-2022-01-14

Thanks, pulled to drm-next.
-Daniel

> 
> for you to fetch changes up to 5d474cc501b90b82c182b5d00439eb6790a82e21:
> 
>   drm/mipi-dbi: Fix source-buffer address in mipi_dbi_buf_copy (2022-01-14 
> 14:43:02 +0100)
> 
> 
>  * atomic helpers: Fix error messages
>  * mipi-dbi: Fix buffer mapping
> 
> 
> Claudio Suarez (1):
>   drm: fix error found in some cases after the patch d1af5cd86997
> 
> Liu Ying (1):
>   drm/atomic: Check new_crtc_state->active to determine if CRTC needs 
> disable in self refresh mode
> 
> Thomas Zimmermann (1):
>   drm/mipi-dbi: Fix source-buffer address in mipi_dbi_buf_copy
> 
>  drivers/gpu/drm/drm_atomic_helper.c | 14 +++---
>  drivers/gpu/drm/drm_mipi_dbi.c  |  2 +-
>  2 files changed, 8 insertions(+), 8 deletions(-)
> 
> -- 
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch


Re: [PULL] drm-misc-next-fixes

2022-01-14 Thread Daniel Vetter
On Thu, Jan 13, 2022 at 09:29:51AM +0100, Thomas Zimmermann wrote:
> Hi Dave and Daniel,
> 
> here's this week's PR for drm-misc-next-fixes.
> 
> Best regards
> Thomas
> 
> drm-misc-next-fixes-2022-01-13:
>  * Fix use of CRTC state's active vs enable in atomic helper
> The following changes since commit 5da8b49de472c1da8658466d4f63ef8d9251a819:
> 
>   dt-bindings: display: bridge: lvds-codec: Fix duplicate key (2021-12-22 
> 14:02:04 -0400)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc 
> tags/drm-misc-next-fixes-2022-01-13
> 
> for you to fetch changes up to 69e630016ef4e4a1745310c446f204dc6243e907:

Thanks, pulled to drm-next.
-Daniel

> 
>   drm/atomic: Check new_crtc_state->active to determine if CRTC needs disable 
> in self refresh mode (2022-01-11 10:37:15 -0500)
> 
> 
>  * Fix use of CRTC state's active vs enable in atomic helper
> 
> 
> Liu Ying (1):
>   drm/atomic: Check new_crtc_state->active to determine if CRTC needs 
> disable in self refresh mode
> 
>  drivers/gpu/drm/drm_atomic_helper.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> -- 
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch


Re: [PULL] drm-misc-next

2021-12-14 Thread Daniel Vetter
On Mon, Nov 29, 2021 at 09:56:47AM +0100, Thomas Zimmermann wrote:
> Hi Dave and Daniel,
> 
> here's the second PR for drm-misc-next for what will become Linux 5.17.
> It's a bit late, as I was on vacation last week. The most significant
> change moves the nomodeset parameter entirely into the DRM subsystem.
> 
> Best regards
> Thomas
> 
> drm-misc-next-2021-11-29:
> drm-misc-next for 5.17:
> 
> UAPI Changes:
> 
> Cross-subsystem Changes:
> 
>  * Move 'nomodeset' kernel boot option into DRM subsystem
> 
> Core Changes:
> 
>  * Replace several DRM_*() logging macros with drm_*() equivalents
>  * panel: Add quirk for Lenovo Yoga Book X91F/L
>  * ttm: Documentation fixes
> 
> Driver Changes:
> 
>  * Cleanup nomodeset handling in drivers
>  * Fixes
>  * bridge/anx7625: Fix reading EDID; Fix error code
>  * bridge/megachips: Probe both bridges before registering
>  * vboxvideo: Fix ERR_PTR usage
> The following changes since commit a713ca234ea9d946235ac7248995c5fddfd9e523:
> 
>   Merge drm/drm-next into drm-misc-next (2021-11-18 09:36:39 +0100)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2021-11-29

Pulled, thanks.
-Daniel

> 
> for you to fetch changes up to 69d846126e1653ca9043c3766c66684132586941:
> 
>   drm: Fix build error caused by missing drm_nomodeset.o (2021-11-27 21:05:58 
> +0100)
> 
> 
> drm-misc-next for 5.17:
> 
> UAPI Changes:
> 
> Cross-subsystem Changes:
> 
>  * Move 'nomodeset' kernel boot option into DRM subsystem
> 
> Core Changes:
> 
>  * Replace several DRM_*() logging macros with drm_*() equivalents
>  * panel: Add quirk for Lenovo Yoga Book X91F/L
>  * ttm: Documentation fixes
> 
> Driver Changes:
> 
>  * Cleanup nomodeset handling in drivers
>  * Fixes
>  * bridge/anx7625: Fix reading EDID; Fix error code
>  * bridge/megachips: Probe both bridges before registering
>  * vboxvideo: Fix ERR_PTR usage
> 
> 
> Christian König (1):
>   drm/amdgpu: partially revert "svm bo enable_signal call condition"
> 
> Claudio Suarez (1):
>   drm: get rid of DRM_DEBUG_* log calls in drm core, files drm_a*.c
> 
> Dan Carpenter (2):
>   drm/vboxvideo: fix a NULL vs IS_ERR() check
>   drm/bridge: anx7625: fix an error code in anx7625_register_audio()
> 
> Hans de Goede (1):
>   drm: panel-orientation-quirks: Add quirk for the Lenovo Yoga Book X91F/L
> 
> Hsin-Yi Wang (1):
>   drm/bridge: anx7625: Fix edid_read break case in sp_tx_edid_read()
> 
> Javier Martinez Canillas (7):
>   drm: Don't print messages if drivers are disabled due nomodeset
>   drm/vboxvideo: Drop CONFIG_VGA_CONSOLE guard to call vgacon_text_force()
>   drm: Move nomodeset kernel parameter to the DRM subsystem
>   drm: Decouple nomodeset from CONFIG_VGA_CONSOLE
>   Documentation/admin-guide: Document nomodeset kernel parameter
>   drm: Make the nomodeset message less sensational
>   drm: Fix build error caused by missing drm_nomodeset.o
> 
> Martyn Welch (1):
>   drm/bridge: megachips: Ensure both bridges are probed before 
> registration
> 
> Randy Dunlap (1):
>   drm: ttm: correct ttm_range_manager kernel-doc notation
> 
>  Documentation/admin-guide/kernel-parameters.txt|   7 +
>  drivers/gpu/drm/Kconfig|   6 +
>  drivers/gpu/drm/Makefile   |   2 +
>  drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c|   5 +-
>  drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c|   9 -
>  drivers/gpu/drm/ast/ast_drv.c  |   3 +-
>  drivers/gpu/drm/bridge/analogix/anx7625.c  |   6 +-
>  .../drm/bridge/megachips-stdp-ge-b850v3-fw.c   |  40 +++-
>  drivers/gpu/drm/drm_atomic.c   | 180 ---
>  drivers/gpu/drm/drm_atomic_helper.c| 243 
> -
>  drivers/gpu/drm/drm_atomic_uapi.c  |   2 +-
>  drivers/gpu/drm/drm_auth.c |  12 +-
>  drivers/gpu/drm/drm_nomodeset.c|  24 ++
>  drivers/gpu/drm/drm_panel_orientation_quirks.c |   6 +
>  drivers/gpu/drm/i915/i915_module.c |   4 +-
>  drivers/gpu/drm/mgag200/mgag200_drv.c  |   3 +-
>  drivers/gpu/drm/nouveau/nouveau_drm.c  |   4 +-
>  drivers/gpu/drm/qxl/qxl_drv.c  |   3 +-
>  drivers/gpu/drm/radeon/radeon_drv.c|   9 +-
>  drivers/gpu/drm/tiny/bochs.c   |   3 +-
>  drivers/gpu/drm/tiny/cirrus.c  |   4 +-
>  drivers/gpu/drm/ttm/ttm_range_manager.c|  11 +-
>  drivers/gpu/drm/vboxvideo/vbox_drv.c   |   5 +-
>  drivers/gpu/drm/vboxvideo/vbox_main.c  |   4 +-
>  drivers/gpu/drm/virtio/virtgpu_drv.c   |   3 +-
>  drivers/gpu/drm/vmwgfx/vmwgfx_drv.c|   3 +-
>  

Re: [PULL] drm-misc-next

2021-09-22 Thread Maxime Ripard
Hi,

On Mon, Sep 20, 2021 at 05:29:41PM -0500, Rob Herring wrote:
> On Thu, Sep 16, 2021 at 2:31 AM Maxime Ripard  wrote:
> >
> > Hi Dave, Daniel,
> >
> > Here's the first drm-misc-next PR for 5.16
> >
> > Thanks!
> > Maxime
> >
> > drm-misc-next-2021-09-16:
> > drm-misc-next for $kernel-version:
> >
> > UAPI Changes:
> >
> > Cross-subsystem Changes:
> >   - dma-buf: Avoid a warning with some allocations, Remove
> > DMA_FENCE_TRACE macros
> >
> > Core Changes:
> >   - bridge: New helper to git rid of panels in drivers
> >   - fence: Improve dma_fence_add_callback documentation, Improve
> > dma_fence_ops->wait documentation
> >   - ioctl: Unexport drm_ioctl_permit
> >   - lease: Documentation improvements
> >   - fourcc: Add new macro to determine the modifier vendor
> >   - quirks: Add the Steam Deck, Chuwi HiBook, Chuwi Hi10 Pro, Samsung
> > Galaxy Book 10.6, KD Kurio Smart C15200 2-in-1, Lenovo Ideapad D330
> >   - resv: Improve the documentation
> >   - shmem-helpers: Allocate WC pages on x86, Switch to vmf_insert_pfn
> >   - sched: Fix for a timer being canceled too soon, Avoid null pointer
> > derefence if the fence is null in drm_sched_fence_free, Convert
> > drivers to rely on its dependency tracking
> >   - ttm: Switch to kerneldoc, new helper to clear all DMA mappings, pool
> > shrinker optitimization, Remove ttm_tt_destroy_common, Fix for
> > unbinding on multiple drivers
> >
> > Driver Changes:
> >   - bochs: New PCI IDs
> >   - msm: Fence ordering impromevemnts
> >   - stm: Add layer alpha support, zpos
> >   - v3d: Fix for a Vulkan CTS failure
> >   - vc4: Conversion to the new bridge helpers
> >   - vgem: Use shmem helpers
> >   - virtio: Support mapping exported vram
> >   - zte: Remove obsolete driver
> >
> >   - bridge: Probe improvements for it66121, enable DSI EOTP for anx7625,
> > errors propagation improvements for anx7625
> >
> >   - panels: 60fps mode for otm8009a, New driver for Samsung S6D27A1
> > The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:
> >
> >   Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)
> >
> > are available in the Git repository at:
> >
> >   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2021-09-16
> >
> > for you to fetch changes up to e4f868191138975f2fdf2f37c11318b47db4acc9:
> >
> >   drm/v3d: fix wait for TMU write combiner flush (2021-09-15 18:43:37 +0100)
> >
> > 
> > drm-misc-next for $kernel-version:
> >
> > UAPI Changes:
> >
> > Cross-subsystem Changes:
> >   - dma-buf: Avoid a warning with some allocations, Remove
> > DMA_FENCE_TRACE macros
> >
> > Core Changes:
> >   - bridge: New helper to git rid of panels in drivers
> >   - fence: Improve dma_fence_add_callback documentation, Improve
> > dma_fence_ops->wait documentation
> >   - ioctl: Unexport drm_ioctl_permit
> >   - lease: Documentation improvements
> >   - fourcc: Add new macro to determine the modifier vendor
> >   - quirks: Add the Steam Deck, Chuwi HiBook, Chuwi Hi10 Pro, Samsung
> > Galaxy Book 10.6, KD Kurio Smart C15200 2-in-1, Lenovo Ideapad D330
> >   - resv: Improve the documentation
> >   - shmem-helpers: Allocate WC pages on x86, Switch to vmf_insert_pfn
> >   - sched: Fix for a timer being canceled too soon, Avoid null pointer
> > derefence if the fence is null in drm_sched_fence_free, Convert
> > drivers to rely on its dependency tracking
> >   - ttm: Switch to kerneldoc, new helper to clear all DMA mappings, pool
> > shrinker optitimization, Remove ttm_tt_destroy_common, Fix for
> > unbinding on multiple drivers
> >
> > Driver Changes:
> >   - bochs: New PCI IDs
> >   - msm: Fence ordering impromevemnts
> >   - stm: Add layer alpha support, zpos
> >   - v3d: Fix for a Vulkan CTS failure
> >   - vc4: Conversion to the new bridge helpers
> >   - vgem: Use shmem helpers
> >   - virtio: Support mapping exported vram
> >   - zte: Remove obsolete driver
> >
> >   - bridge: Probe improvements for it66121, enable DSI EOTP for anx7625,
> > errors propagation improvements for anx7625
> >
> >   - panels: 60fps mode for otm8009a, New driver for Samsung S6D27A1
> >
> > 
> > Alyssa Rosenzweig (2):
> >   drm/panfrost: Use upper/lower_32_bits helpers
> >   drm/plane: Fix comment typo
> >
> > Andrey Grodzovsky (2):
> >   drm/ttm: Create pinned list
> >   drm/ttm: Clear all DMA mappings on demand
> >
> > Boris Brezillon (2):
> >   panfrost: Don't cleanup the job if it was successfully queued
> >   drm/sched: Fix drm_sched_fence_free() so it can be passed an 
> > uninitialized fence
> >
> > Cai Huoqing (7):
> >   drm/bridge: cdns: Make use of the helper function 
> > devm_platform_ioremap_resource()
> >   drm: adv7511: Convert to SPDX identifier
> >   drm/vc4: Make use of the helper function 
> > devm_platform_ioremap_resource()
> >   

Re: [PULL] drm-misc-next

2021-09-20 Thread Rob Herring
On Thu, Sep 16, 2021 at 2:31 AM Maxime Ripard  wrote:
>
> Hi Dave, Daniel,
>
> Here's the first drm-misc-next PR for 5.16
>
> Thanks!
> Maxime
>
> drm-misc-next-2021-09-16:
> drm-misc-next for $kernel-version:
>
> UAPI Changes:
>
> Cross-subsystem Changes:
>   - dma-buf: Avoid a warning with some allocations, Remove
> DMA_FENCE_TRACE macros
>
> Core Changes:
>   - bridge: New helper to git rid of panels in drivers
>   - fence: Improve dma_fence_add_callback documentation, Improve
> dma_fence_ops->wait documentation
>   - ioctl: Unexport drm_ioctl_permit
>   - lease: Documentation improvements
>   - fourcc: Add new macro to determine the modifier vendor
>   - quirks: Add the Steam Deck, Chuwi HiBook, Chuwi Hi10 Pro, Samsung
> Galaxy Book 10.6, KD Kurio Smart C15200 2-in-1, Lenovo Ideapad D330
>   - resv: Improve the documentation
>   - shmem-helpers: Allocate WC pages on x86, Switch to vmf_insert_pfn
>   - sched: Fix for a timer being canceled too soon, Avoid null pointer
> derefence if the fence is null in drm_sched_fence_free, Convert
> drivers to rely on its dependency tracking
>   - ttm: Switch to kerneldoc, new helper to clear all DMA mappings, pool
> shrinker optitimization, Remove ttm_tt_destroy_common, Fix for
> unbinding on multiple drivers
>
> Driver Changes:
>   - bochs: New PCI IDs
>   - msm: Fence ordering impromevemnts
>   - stm: Add layer alpha support, zpos
>   - v3d: Fix for a Vulkan CTS failure
>   - vc4: Conversion to the new bridge helpers
>   - vgem: Use shmem helpers
>   - virtio: Support mapping exported vram
>   - zte: Remove obsolete driver
>
>   - bridge: Probe improvements for it66121, enable DSI EOTP for anx7625,
> errors propagation improvements for anx7625
>
>   - panels: 60fps mode for otm8009a, New driver for Samsung S6D27A1
> The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:
>
>   Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2021-09-16
>
> for you to fetch changes up to e4f868191138975f2fdf2f37c11318b47db4acc9:
>
>   drm/v3d: fix wait for TMU write combiner flush (2021-09-15 18:43:37 +0100)
>
> 
> drm-misc-next for $kernel-version:
>
> UAPI Changes:
>
> Cross-subsystem Changes:
>   - dma-buf: Avoid a warning with some allocations, Remove
> DMA_FENCE_TRACE macros
>
> Core Changes:
>   - bridge: New helper to git rid of panels in drivers
>   - fence: Improve dma_fence_add_callback documentation, Improve
> dma_fence_ops->wait documentation
>   - ioctl: Unexport drm_ioctl_permit
>   - lease: Documentation improvements
>   - fourcc: Add new macro to determine the modifier vendor
>   - quirks: Add the Steam Deck, Chuwi HiBook, Chuwi Hi10 Pro, Samsung
> Galaxy Book 10.6, KD Kurio Smart C15200 2-in-1, Lenovo Ideapad D330
>   - resv: Improve the documentation
>   - shmem-helpers: Allocate WC pages on x86, Switch to vmf_insert_pfn
>   - sched: Fix for a timer being canceled too soon, Avoid null pointer
> derefence if the fence is null in drm_sched_fence_free, Convert
> drivers to rely on its dependency tracking
>   - ttm: Switch to kerneldoc, new helper to clear all DMA mappings, pool
> shrinker optitimization, Remove ttm_tt_destroy_common, Fix for
> unbinding on multiple drivers
>
> Driver Changes:
>   - bochs: New PCI IDs
>   - msm: Fence ordering impromevemnts
>   - stm: Add layer alpha support, zpos
>   - v3d: Fix for a Vulkan CTS failure
>   - vc4: Conversion to the new bridge helpers
>   - vgem: Use shmem helpers
>   - virtio: Support mapping exported vram
>   - zte: Remove obsolete driver
>
>   - bridge: Probe improvements for it66121, enable DSI EOTP for anx7625,
> errors propagation improvements for anx7625
>
>   - panels: 60fps mode for otm8009a, New driver for Samsung S6D27A1
>
> 
> Alyssa Rosenzweig (2):
>   drm/panfrost: Use upper/lower_32_bits helpers
>   drm/plane: Fix comment typo
>
> Andrey Grodzovsky (2):
>   drm/ttm: Create pinned list
>   drm/ttm: Clear all DMA mappings on demand
>
> Boris Brezillon (2):
>   panfrost: Don't cleanup the job if it was successfully queued
>   drm/sched: Fix drm_sched_fence_free() so it can be passed an 
> uninitialized fence
>
> Cai Huoqing (7):
>   drm/bridge: cdns: Make use of the helper function 
> devm_platform_ioremap_resource()
>   drm: adv7511: Convert to SPDX identifier
>   drm/vc4: Make use of the helper function 
> devm_platform_ioremap_resource()
>   drm/sun4i: Make use of the helper function 
> devm_platform_ioremap_resource()
>   drm/panfrost: Make use of the helper function 
> devm_platform_ioremap_resource()
>   drm/mcde: Make use of the helper function 
> devm_platform_ioremap_resource()
>   drm/meson: Make use of the helper function 
> 

Re: [PULL] drm-misc-next

2021-07-21 Thread Thomas Zimmermann

Hi

Am 21.07.21 um 06:03 schrieb Dave Airlie:

On Fri, 16 Jul 2021 at 21:07, Maarten Lankhorst
 wrote:


Hi Dave & Daniel,

Lots of stuff this time around.

Enjoy!


I've pulled this but there is an outstanding warning

/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c:
In function ‘hibmc_unload’:
/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c:252:28:
warning: unused variable ‘priv’ [-Wunused-variable]
   252 |  struct hibmc_drm_private *priv = to_hibmc_drm_private(dev);
   |^~~~

Probably due to Thomas irq patches.


I'll take a look.

Best regards
Thomas



Dave.



--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer



OpenPGP_signature
Description: OpenPGP digital signature


Re: [PULL] drm-misc-next

2021-07-20 Thread Dave Airlie
On Fri, 16 Jul 2021 at 21:07, Maarten Lankhorst
 wrote:
>
> Hi Dave & Daniel,
>
> Lots of stuff this time around.
>
> Enjoy!

I've pulled this but there is an outstanding warning

/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c:
In function ‘hibmc_unload’:
/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c:252:28:
warning: unused variable ‘priv’ [-Wunused-variable]
  252 |  struct hibmc_drm_private *priv = to_hibmc_drm_private(dev);
  |^~~~

Probably due to Thomas irq patches.

Dave.


Re: [PULL] drm-misc-next-fixes

2021-06-18 Thread Daniel Vetter
On Fri, Jun 18, 2021 at 4:31 AM Dave Airlie  wrote:
>
> On Fri, 18 Jun 2021 at 12:26, Dave Airlie  wrote:
> >
> > when I pulled this in drm-next I got these.
> >
> > were the mst fixes meant for next or fixes btw? I'm not really sure,
> > but either way I don't think this is a local reason it doesn't build
> > or did I miss something?
>
> Hi Thomas,
>
> Please resend with the fix Lyude has pushed (just keep building, just
> keep building).

Yeah I think both committer when applying and probably also maintainer
before sending pull should have rechecked the works. Until we have CI
on gitlab this grunk work is just needed because a ton of people don't
do it - as this patch shows, where out of 4 people only seems to have
fired up the compiler :-)
-Daniel

>
> Thanks,
> Dave.
> >
> > Dave.
> >
> > /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:
> > In function ‘drm_dp_update_payload_part1’:
> > /home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:450:27:
> > error: request for member ‘dev’ in something not a structure or union
> >   450 |  drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_KMS, fmt, 
> > ##__VA_ARGS__)
> >   |   ^~
> > /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3392:5:
> > note: in expansion of macro ‘drm_dbg_kms’
> >  3392 | drm_dbg_kms("Virtual channel %d is not in current topology\n", 
> > i);
> >   | ^~~
> > /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3392:68:
> > warning: passing argument 3 of ‘drm_dev_dbg’ makes pointer from
> > integer without a cast [-Wint-conversion]
> >  3392 | drm_dbg_kms("Virtual channel %d is not in current topology\n", 
> > i);
> >   |^
> >   ||
> >   |
> > int
> > /home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:450:53:
> > note: in definition of macro ‘drm_dbg_kms’
> >   450 |  drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_KMS, fmt, 
> > ##__VA_ARGS__)
> >   | ^~~
> > /home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:338:16:
> > note: expected ‘const char *’ but argument is of type ‘int’
> >   338 |const char *format, ...);
> >   |^~
> > /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3407:53:
> > error: macro "drm_dbg_kms" requires 3 arguments, but only 1 given
> >  3407 |   drm_dbg_kms("Fail:set payload to invalid sink");
> >   | ^
> > In file included from
> > /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:45:
> > /home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:449: note:
> > macro "drm_dbg_kms" defined here
> >   449 | #define drm_dbg_kms(drm, fmt, ...) \
> >   |
> > /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3407:7:
> > error: ‘drm_dbg_kms’ undeclared (first use in this function)
> >  3407 |   drm_dbg_kms("Fail:set payload to invalid sink");
> >   |   ^~~
> > /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3407:7:
> > note: each undeclared identifier is reported only once for each
> > function it appears in
> > make[4]: *** [/home/airlied/devel/kernel/dim/src/scripts/Makefile.build:272:
> > drivers/gpu/drm/drm_dp_mst_topology.o] Error 1
> > make[4]: *** Waiting for unfinished jobs
> >
> > On Thu, 17 Jun 2021 at 04:30, Thomas Zimmermann  wrote:
> > >
> > > Hi Dave and Daniel,
> > >
> > > here's this week's PR for drm-misc-next-fixes.
> > >
> > > Best regards
> > > Thomas
> > >
> > > drm-misc-next-fixes-2021-06-16:
> > > Short summary of fixes pull:
> > >
> > >  * hyperv: advertise the correct formatmodifiers for its primary plane
> > >  * dp_mst: VCPI fixes to make it work with StarTech hub
> > >
> > > The following changes since commit 
> > > 1bd8a7dc28c1c410f1ceefae1f2a97c06d1a67c2:
> > >
> > >   Merge tag 'exynos-drm-next-for-v5.14' of 
> > > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into 
> > > drm-next (2021-06-11 14:19:12 +1000)
> > >
> > > are available in the Git repository at:
> > >
> > >   git://anongit.freedesktop.org/drm/drm-misc 
> > > tags/drm-misc-next-fixes-2021-06-16
> > >
> > > for you to fetch changes up to 3769e4c0af5b82c8ea21d037013cb9564dfaa51f:
> > >
> > >   drm/dp_mst: Avoid to mess up payload table by ports in stale topology 
> > > (2021-06-16 12:57:46 -0400)
> > >
> > > 
> > > Short summary of fixes pull:
> > >
> > >  * hyperv: advertise the correct formatmodifiers for its primary plane
> > >  * dp_mst: VCPI fixes to make it work with StarTech hub
> > >
> > > 

Re: [PULL] drm-misc-next-fixes

2021-06-17 Thread Dave Airlie
On Fri, 18 Jun 2021 at 12:26, Dave Airlie  wrote:
>
> when I pulled this in drm-next I got these.
>
> were the mst fixes meant for next or fixes btw? I'm not really sure,
> but either way I don't think this is a local reason it doesn't build
> or did I miss something?

Hi Thomas,

Please resend with the fix Lyude has pushed (just keep building, just
keep building).

Thanks,
Dave.
>
> Dave.
>
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:
> In function ‘drm_dp_update_payload_part1’:
> /home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:450:27:
> error: request for member ‘dev’ in something not a structure or union
>   450 |  drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_KMS, fmt, 
> ##__VA_ARGS__)
>   |   ^~
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3392:5:
> note: in expansion of macro ‘drm_dbg_kms’
>  3392 | drm_dbg_kms("Virtual channel %d is not in current topology\n", i);
>   | ^~~
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3392:68:
> warning: passing argument 3 of ‘drm_dev_dbg’ makes pointer from
> integer without a cast [-Wint-conversion]
>  3392 | drm_dbg_kms("Virtual channel %d is not in current topology\n", i);
>   |^
>   ||
>   |int
> /home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:450:53:
> note: in definition of macro ‘drm_dbg_kms’
>   450 |  drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_KMS, fmt, 
> ##__VA_ARGS__)
>   | ^~~
> /home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:338:16:
> note: expected ‘const char *’ but argument is of type ‘int’
>   338 |const char *format, ...);
>   |^~
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3407:53:
> error: macro "drm_dbg_kms" requires 3 arguments, but only 1 given
>  3407 |   drm_dbg_kms("Fail:set payload to invalid sink");
>   | ^
> In file included from
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:45:
> /home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:449: note:
> macro "drm_dbg_kms" defined here
>   449 | #define drm_dbg_kms(drm, fmt, ...) \
>   |
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3407:7:
> error: ‘drm_dbg_kms’ undeclared (first use in this function)
>  3407 |   drm_dbg_kms("Fail:set payload to invalid sink");
>   |   ^~~
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3407:7:
> note: each undeclared identifier is reported only once for each
> function it appears in
> make[4]: *** [/home/airlied/devel/kernel/dim/src/scripts/Makefile.build:272:
> drivers/gpu/drm/drm_dp_mst_topology.o] Error 1
> make[4]: *** Waiting for unfinished jobs
>
> On Thu, 17 Jun 2021 at 04:30, Thomas Zimmermann  wrote:
> >
> > Hi Dave and Daniel,
> >
> > here's this week's PR for drm-misc-next-fixes.
> >
> > Best regards
> > Thomas
> >
> > drm-misc-next-fixes-2021-06-16:
> > Short summary of fixes pull:
> >
> >  * hyperv: advertise the correct formatmodifiers for its primary plane
> >  * dp_mst: VCPI fixes to make it work with StarTech hub
> >
> > The following changes since commit 1bd8a7dc28c1c410f1ceefae1f2a97c06d1a67c2:
> >
> >   Merge tag 'exynos-drm-next-for-v5.14' of 
> > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into 
> > drm-next (2021-06-11 14:19:12 +1000)
> >
> > are available in the Git repository at:
> >
> >   git://anongit.freedesktop.org/drm/drm-misc 
> > tags/drm-misc-next-fixes-2021-06-16
> >
> > for you to fetch changes up to 3769e4c0af5b82c8ea21d037013cb9564dfaa51f:
> >
> >   drm/dp_mst: Avoid to mess up payload table by ports in stale topology 
> > (2021-06-16 12:57:46 -0400)
> >
> > 
> > Short summary of fixes pull:
> >
> >  * hyperv: advertise the correct formatmodifiers for its primary plane
> >  * dp_mst: VCPI fixes to make it work with StarTech hub
> >
> > 
> > Pu Lehui (1):
> >   drm/hyperv: Fix unused const variable 'hyperv_modifiers'
> >
> > Wayne Lin (2):
> >   drm/dp_mst: Do not set proposed vcpi directly
> >   drm/dp_mst: Avoid to mess up payload table by ports in stale topology
> >
> >  drivers/gpu/drm/drm_dp_mst_topology.c   | 65 
> > +
> >  drivers/gpu/drm/hyperv/hyperv_drm_modeset.c |  2 +-
> >  2 files changed, 40 insertions(+), 27 deletions(-)
> >
> > --
> > Thomas Zimmermann
> > Graphics Driver Developer
> > SUSE Software Solutions Germany GmbH
> > 

Re: [PULL] drm-misc-next-fixes

2021-06-17 Thread Lyude Paul
22:27  airlied: re: the pull, I should have pushed a fix for the
compilation error today. that was something I pulled in from amd that they
didn't compile check and I missed :S
22:28  airlied: 24ff3dc18b99c4b912ab1746e803ddb3be5ced4c in drm-
misc/drm-misc-next-fixes

sorry about this - I already talked to hwentlan the other day about trying to
make sure that AMD is more on top of actually making sure things compile
before submitting them, was my fault for missing this during the initial
review of that fix.

On Fri, 2021-06-18 at 12:26 +1000, Dave Airlie wrote:
> when I pulled this in drm-next I got these.
> 
> were the mst fixes meant for next or fixes btw? I'm not really sure,
> but either way I don't think this is a local reason it doesn't build
> or did I miss something?
> 
> Dave.
> 
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:
> In function ‘drm_dp_update_payload_part1’:
> /home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:450:27:
> error: request for member ‘dev’ in something not a structure or union
>   450 |  drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_KMS, fmt,
> ##__VA_ARGS__)
>   |   ^~
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3392:
> 5:
> note: in expansion of macro ‘drm_dbg_kms’
>  3392 | drm_dbg_kms("Virtual channel %d is not in current topology\n", i);
>   | ^~~
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3392:
> 68:
> warning: passing argument 3 of ‘drm_dev_dbg’ makes pointer from
> integer without a cast [-Wint-conversion]
>  3392 | drm_dbg_kms("Virtual channel %d is not in current topology\n", i);
>   |    ^
>   |    |
>   |    int
> /home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:450:53:
> note: in definition of macro ‘drm_dbg_kms’
>   450 |  drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_KMS, fmt,
> ##__VA_ARGS__)
>   | ^~~
> /home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:338:16:
> note: expected ‘const char *’ but argument is of type ‘int’
>   338 |    const char *format, ...);
>   |    ^~
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3407:
> 53:
> error: macro "drm_dbg_kms" requires 3 arguments, but only 1 given
>  3407 |   drm_dbg_kms("Fail:set payload to invalid sink");
>   | ^
> In file included from
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:45:
> /home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:449: note:
> macro "drm_dbg_kms" defined here
>   449 | #define drm_dbg_kms(drm, fmt, ...) \
>   |
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3407:
> 7:
> error: ‘drm_dbg_kms’ undeclared (first use in this function)
>  3407 |   drm_dbg_kms("Fail:set payload to invalid sink");
>   |   ^~~
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3407:
> 7:
> note: each undeclared identifier is reported only once for each
> function it appears in
> make[4]: *** [/home/airlied/devel/kernel/dim/src/scripts/Makefile.build:272:
> drivers/gpu/drm/drm_dp_mst_topology.o] Error 1
> make[4]: *** Waiting for unfinished jobs
> 
> On Thu, 17 Jun 2021 at 04:30, Thomas Zimmermann  wrote:
> > 
> > Hi Dave and Daniel,
> > 
> > here's this week's PR for drm-misc-next-fixes.
> > 
> > Best regards
> > Thomas
> > 
> > drm-misc-next-fixes-2021-06-16:
> > Short summary of fixes pull:
> > 
> >  * hyperv: advertise the correct formatmodifiers for its primary plane
> >  * dp_mst: VCPI fixes to make it work with StarTech hub
> > 
> > The following changes since commit 1bd8a7dc28c1c410f1ceefae1f2a97c06d1a67c2:
> > 
> >   Merge tag 'exynos-drm-next-for-v5.14' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-
> > next (2021-06-11 14:19:12 +1000)
> > 
> > are available in the Git repository at:
> > 
> >   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-fixes-2021-
> > 06-16
> > 
> > for you to fetch changes up to 3769e4c0af5b82c8ea21d037013cb9564dfaa51f:
> > 
> >   drm/dp_mst: Avoid to mess up payload table by ports in stale topology
> > (2021-06-16 12:57:46 -0400)
> > 
> > 
> > Short summary of fixes pull:
> > 
> >  * hyperv: advertise the correct formatmodifiers for its primary plane
> >  * dp_mst: VCPI fixes to make it work with StarTech hub
> > 
> > 
> > Pu Lehui (1):
> >   drm/hyperv: Fix unused const variable 'hyperv_modifiers'
> > 
> > Wayne Lin (2):
> >   drm/dp_mst: Do not 

Re: [PULL] drm-misc-next-fixes

2021-06-17 Thread Dave Airlie
when I pulled this in drm-next I got these.

were the mst fixes meant for next or fixes btw? I'm not really sure,
but either way I don't think this is a local reason it doesn't build
or did I miss something?

Dave.

/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:
In function ‘drm_dp_update_payload_part1’:
/home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:450:27:
error: request for member ‘dev’ in something not a structure or union
  450 |  drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_KMS, fmt, ##__VA_ARGS__)
  |   ^~
/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3392:5:
note: in expansion of macro ‘drm_dbg_kms’
 3392 | drm_dbg_kms("Virtual channel %d is not in current topology\n", i);
  | ^~~
/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3392:68:
warning: passing argument 3 of ‘drm_dev_dbg’ makes pointer from
integer without a cast [-Wint-conversion]
 3392 | drm_dbg_kms("Virtual channel %d is not in current topology\n", i);
  |^
  ||
  |int
/home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:450:53:
note: in definition of macro ‘drm_dbg_kms’
  450 |  drm_dev_dbg((drm) ? (drm)->dev : NULL, DRM_UT_KMS, fmt, ##__VA_ARGS__)
  | ^~~
/home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:338:16:
note: expected ‘const char *’ but argument is of type ‘int’
  338 |const char *format, ...);
  |^~
/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3407:53:
error: macro "drm_dbg_kms" requires 3 arguments, but only 1 given
 3407 |   drm_dbg_kms("Fail:set payload to invalid sink");
  | ^
In file included from
/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:45:
/home/airlied/devel/kernel/dim/src/include/drm/drm_print.h:449: note:
macro "drm_dbg_kms" defined here
  449 | #define drm_dbg_kms(drm, fmt, ...) \
  |
/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3407:7:
error: ‘drm_dbg_kms’ undeclared (first use in this function)
 3407 |   drm_dbg_kms("Fail:set payload to invalid sink");
  |   ^~~
/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/drm_dp_mst_topology.c:3407:7:
note: each undeclared identifier is reported only once for each
function it appears in
make[4]: *** [/home/airlied/devel/kernel/dim/src/scripts/Makefile.build:272:
drivers/gpu/drm/drm_dp_mst_topology.o] Error 1
make[4]: *** Waiting for unfinished jobs

On Thu, 17 Jun 2021 at 04:30, Thomas Zimmermann  wrote:
>
> Hi Dave and Daniel,
>
> here's this week's PR for drm-misc-next-fixes.
>
> Best regards
> Thomas
>
> drm-misc-next-fixes-2021-06-16:
> Short summary of fixes pull:
>
>  * hyperv: advertise the correct formatmodifiers for its primary plane
>  * dp_mst: VCPI fixes to make it work with StarTech hub
>
> The following changes since commit 1bd8a7dc28c1c410f1ceefae1f2a97c06d1a67c2:
>
>   Merge tag 'exynos-drm-next-for-v5.14' of 
> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into 
> drm-next (2021-06-11 14:19:12 +1000)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-misc 
> tags/drm-misc-next-fixes-2021-06-16
>
> for you to fetch changes up to 3769e4c0af5b82c8ea21d037013cb9564dfaa51f:
>
>   drm/dp_mst: Avoid to mess up payload table by ports in stale topology 
> (2021-06-16 12:57:46 -0400)
>
> 
> Short summary of fixes pull:
>
>  * hyperv: advertise the correct formatmodifiers for its primary plane
>  * dp_mst: VCPI fixes to make it work with StarTech hub
>
> 
> Pu Lehui (1):
>   drm/hyperv: Fix unused const variable 'hyperv_modifiers'
>
> Wayne Lin (2):
>   drm/dp_mst: Do not set proposed vcpi directly
>   drm/dp_mst: Avoid to mess up payload table by ports in stale topology
>
>  drivers/gpu/drm/drm_dp_mst_topology.c   | 65 
> +
>  drivers/gpu/drm/hyperv/hyperv_drm_modeset.c |  2 +-
>  2 files changed, 40 insertions(+), 27 deletions(-)
>
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer


Re: [PULL] drm-misc-next

2021-06-11 Thread Thomas Zimmermann

Hi

Am 10.06.21 um 15:32 schrieb Daniel Vetter:

On Thu, Jun 10, 2021 at 1:15 PM Thomas Zimmermann  wrote:


Hi Dave and Daniel,

here's the second PR for drm-misc-next for this week, and the final one
for 5.14. I backmerged drm-next for the TTM changes. As for highlights
nouveau now has eDP backlight support and udmabuf supports huge pages.


Why did you do this backmerge? It's done now so nothing to fix, but
I'm not really seeing the reason - the backmerge is the last patch
right before you've done the pull request.


From what I understood, there was a TTM change (coming from intel-gt) 
that created significant conflicts between trees. I backmerged to get 
these changes into drm-misc-next. If the drm-next side was outdated, 
people shouldn't have to make patches against it.


Best regards
Thomas


-Daniel



Best regards
Thomas

drm-misc-next-2021-06-10:
drm-misc-next for 5.14:

UAPI Changes:

Cross-subsystem Changes:

  * dma-buf: Support huge pages in udmabuf

Core Changes:

  * Backmerge of drm/drm-next

  * drm/dp: Import eDP backlight code from i915

Driver Changes:

  * drm/bridge: TI SN65DSI83: Fix sparse warnings

  * drm/i915: Cleanup eDP backlight code before moving it into helper

  * drm/nouveau: Support DPCD backlights; Fix GEM init for internal BOs
The following changes since commit c707b73f0cfb1acc94a20389aecde65e6385349b:

   Merge tag 'amd-drm-next-5.14-2021-06-09' of 
https://gitlab.freedesktop.org/agd5f/linux into drm-next (2021-06-10 13:47:13 
+1000)

are available in the Git repository at:

   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2021-06-10

for you to fetch changes up to 86441fa29e57940eeb00f35fefb1853c1fbe67bb:

   Merge drm/drm-next into drm-misc-next (2021-06-10 12:18:54 +0200)


drm-misc-next for 5.14:

UAPI Changes:

Cross-subsystem Changes:

  * dma-buf: Support huge pages in udmabuf

Core Changes:

  * Backmerge of drm/drm-next

  * drm/dp: Import eDP backlight code from i915

Driver Changes:

  * drm/bridge: TI SN65DSI83: Fix sparse warnings

  * drm/i915: Cleanup eDP backlight code before moving it into helper

  * drm/nouveau: Support DPCD backlights; Fix GEM init for internal BOs


Christian König (1):
   drm/nouveau: init the base GEM fields for internal BOs

Lyude Paul (9):
   drm/i915/dpcd_bl: Remove redundant AUX backlight frequency calculations
   drm/i915/dpcd_bl: Handle drm_dpcd_read/write() return values correctly
   drm/i915/dpcd_bl: Cleanup intel_dp_aux_vesa_enable_backlight() a bit
   drm/i915/dpcd_bl: Cache some backlight capabilities in 
intel_panel.backlight
   drm/i915/dpcd_bl: Move VESA backlight enabling code closer together
   drm/i915/dpcd_bl: Return early in vesa_calc_max_backlight if we can't 
read PWMGEN_BIT_COUNT
   drm/i915/dpcd_bl: Print return codes for VESA backlight failures
   drm/dp: Extract i915's eDP backlight code into DRM helpers
   drm/nouveau/kms/nv50-: Add basic DPCD backlight support for nouveau

Marek Vasut (1):
   drm/bridge: ti-sn65dsi83: Fix sparse warnings

Thomas Zimmermann (1):
   Merge drm/drm-next into drm-misc-next

Vivek Kasireddy (1):
   udmabuf: Add support for mapping hugepages (v4)

  drivers/dma-buf/udmabuf.c  |  50 ++-
  drivers/gpu/drm/bridge/ti-sn65dsi83.c  |  21 +-
  drivers/gpu/drm/drm_dp_helper.c| 347 +
  drivers/gpu/drm/i915/display/intel_display_types.h |   2 +-
  .../gpu/drm/i915/display/intel_dp_aux_backlight.c  | 329 +++
  drivers/gpu/drm/nouveau/dispnv50/disp.c|  28 ++
  drivers/gpu/drm/nouveau/nouveau_backlight.c| 166 +-
  drivers/gpu/drm/nouveau/nouveau_bo.c   |   6 +
  drivers/gpu/drm/nouveau/nouveau_connector.h|   9 +-
  drivers/gpu/drm/nouveau/nouveau_encoder.h  |   1 +
  include/drm/drm_dp_helper.h|  48 +++
  11 files changed, 682 insertions(+), 325 deletions(-)

--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer






--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer



OpenPGP_signature
Description: OpenPGP digital signature


Re: [PULL] drm-misc-next

2021-06-10 Thread Daniel Vetter
On Thu, Jun 10, 2021 at 1:15 PM Thomas Zimmermann  wrote:
>
> Hi Dave and Daniel,
>
> here's the second PR for drm-misc-next for this week, and the final one
> for 5.14. I backmerged drm-next for the TTM changes. As for highlights
> nouveau now has eDP backlight support and udmabuf supports huge pages.

Why did you do this backmerge? It's done now so nothing to fix, but
I'm not really seeing the reason - the backmerge is the last patch
right before you've done the pull request.
-Daniel

>
> Best regards
> Thomas
>
> drm-misc-next-2021-06-10:
> drm-misc-next for 5.14:
>
> UAPI Changes:
>
> Cross-subsystem Changes:
>
>  * dma-buf: Support huge pages in udmabuf
>
> Core Changes:
>
>  * Backmerge of drm/drm-next
>
>  * drm/dp: Import eDP backlight code from i915
>
> Driver Changes:
>
>  * drm/bridge: TI SN65DSI83: Fix sparse warnings
>
>  * drm/i915: Cleanup eDP backlight code before moving it into helper
>
>  * drm/nouveau: Support DPCD backlights; Fix GEM init for internal BOs
> The following changes since commit c707b73f0cfb1acc94a20389aecde65e6385349b:
>
>   Merge tag 'amd-drm-next-5.14-2021-06-09' of 
> https://gitlab.freedesktop.org/agd5f/linux into drm-next (2021-06-10 13:47:13 
> +1000)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2021-06-10
>
> for you to fetch changes up to 86441fa29e57940eeb00f35fefb1853c1fbe67bb:
>
>   Merge drm/drm-next into drm-misc-next (2021-06-10 12:18:54 +0200)
>
> 
> drm-misc-next for 5.14:
>
> UAPI Changes:
>
> Cross-subsystem Changes:
>
>  * dma-buf: Support huge pages in udmabuf
>
> Core Changes:
>
>  * Backmerge of drm/drm-next
>
>  * drm/dp: Import eDP backlight code from i915
>
> Driver Changes:
>
>  * drm/bridge: TI SN65DSI83: Fix sparse warnings
>
>  * drm/i915: Cleanup eDP backlight code before moving it into helper
>
>  * drm/nouveau: Support DPCD backlights; Fix GEM init for internal BOs
>
> 
> Christian König (1):
>   drm/nouveau: init the base GEM fields for internal BOs
>
> Lyude Paul (9):
>   drm/i915/dpcd_bl: Remove redundant AUX backlight frequency calculations
>   drm/i915/dpcd_bl: Handle drm_dpcd_read/write() return values correctly
>   drm/i915/dpcd_bl: Cleanup intel_dp_aux_vesa_enable_backlight() a bit
>   drm/i915/dpcd_bl: Cache some backlight capabilities in 
> intel_panel.backlight
>   drm/i915/dpcd_bl: Move VESA backlight enabling code closer together
>   drm/i915/dpcd_bl: Return early in vesa_calc_max_backlight if we can't 
> read PWMGEN_BIT_COUNT
>   drm/i915/dpcd_bl: Print return codes for VESA backlight failures
>   drm/dp: Extract i915's eDP backlight code into DRM helpers
>   drm/nouveau/kms/nv50-: Add basic DPCD backlight support for nouveau
>
> Marek Vasut (1):
>   drm/bridge: ti-sn65dsi83: Fix sparse warnings
>
> Thomas Zimmermann (1):
>   Merge drm/drm-next into drm-misc-next
>
> Vivek Kasireddy (1):
>   udmabuf: Add support for mapping hugepages (v4)
>
>  drivers/dma-buf/udmabuf.c  |  50 ++-
>  drivers/gpu/drm/bridge/ti-sn65dsi83.c  |  21 +-
>  drivers/gpu/drm/drm_dp_helper.c| 347 
> +
>  drivers/gpu/drm/i915/display/intel_display_types.h |   2 +-
>  .../gpu/drm/i915/display/intel_dp_aux_backlight.c  | 329 +++
>  drivers/gpu/drm/nouveau/dispnv50/disp.c|  28 ++
>  drivers/gpu/drm/nouveau/nouveau_backlight.c| 166 +-
>  drivers/gpu/drm/nouveau/nouveau_bo.c   |   6 +
>  drivers/gpu/drm/nouveau/nouveau_connector.h|   9 +-
>  drivers/gpu/drm/nouveau/nouveau_encoder.h  |   1 +
>  include/drm/drm_dp_helper.h|  48 +++
>  11 files changed, 682 insertions(+), 325 deletions(-)
>
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer



-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch


Re: [PULL] drm-misc-next

2021-05-17 Thread Thomas Zimmermann

Hi

Am 17.05.21 um 15:17 schrieb Thomas Zimmermann:

Hi Dave and Daniel,

here's this week's PR for drm-misc-next for what wil become v5.14.
Panfrost gets support for Mediatek MT8381 chips. There are a number of
fixes for resource leaks in various drivers. Unlocking on errors in
aperture helpers gets fixes as well.


Oh, there are last week's patches as well! Apparently last week's PR 
wasn't merged yet. (?) Sorry, I didn't notice. But I received bug 
reports from linux-next. That's confusing.


Dave, Daniel, can you simply merge both tags, drm-misc-next-2021-05-12 
and drm-misc-next-2021-05-17?


Best regards
Thomas



Best regards
Thomas

drm-misc-next-2021-05-17:
drm-misc-next for 5.14:

UAPI Changes:

Cross-subsystem Changes:

Core Changes:

  * aperture: Fix unlocking on errors

  * legacy: Fix some doc comments

Driver Changes:

  * drm/amdgpu: Free resource on fence usage query; Fix fence calculation;

  * drm/bridge: Lt9611: Add missing MODULE_DEVICE_TABLE

  * drm/i915: Print formats with %p4cc

  * drm/ingenic: IPU planes are now always of type OVERLAY

  * drm/nouveau: Remove left-over reference to struct drm_device.pdev

  * drm/panfrost: Disable devfreq if num_supplies > 1; Add Mediatek MT8183 +
DT bindings; Cleanups

  * drm/simpledrm: Print resources with %pr; Fix use-after-free errors;
Fix NULL deref; Fix MAINTAINERS entry

  * drm/vmwgfx: Fix memory allocation and leak in FIFO allocation; Fix
return value in PCI resource setup

The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:

   Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)

are available in the Git repository at:

   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2021-05-17

for you to fetch changes up to 30039405ac25665119ff7bc944d33b136ef1c8a9:

   MAINTAINERS: repair reference in DRM DRIVER FOR SIMPLE FRAMEBUFFERS 
(2021-05-17 14:53:17 +0200)


drm-misc-next for 5.14:

UAPI Changes:

Cross-subsystem Changes:

Core Changes:

  * aperture: Fix unlocking on errors

  * legacy: Fix some doc comments

Driver Changes:

  * drm/amdgpu: Free resource on fence usage query; Fix fence calculation;

  * drm/bridge: Lt9611: Add missing MODULE_DEVICE_TABLE

  * drm/i915: Print formats with %p4cc

  * drm/ingenic: IPU planes are now always of type OVERLAY

  * drm/nouveau: Remove left-over reference to struct drm_device.pdev

  * drm/panfrost: Disable devfreq if num_supplies > 1; Add Mediatek MT8183 +
DT bindings; Cleanups

  * drm/simpledrm: Print resources with %pr; Fix use-after-free errors;
Fix NULL deref; Fix MAINTAINERS entry

  * drm/vmwgfx: Fix memory allocation and leak in FIFO allocation; Fix
return value in PCI resource setup


Adrien Grassein (1):
   drm/bridge: fix LONTIUM_LT8912B dependencies

Alex Deucher (1):
   MAINTAINERS: Fix TTM tree

Andy Shevchenko (7):
   drm/st7735r: Avoid spamming logs if probe is deferred
   drm/st7586: Avoid spamming logs if probe is deferred
   drm/mi0283qt: Avoid spamming logs if probe is deferred
   drm/ili9486: Avoid spamming logs if probe is deferred
   drm/ili9341: Avoid spamming logs if probe is deferred
   drm/ili9225: Avoid spamming logs if probe is deferred
   drm/hx8357d: Avoid spamming logs if probe is deferred

Beatriz Martins de Carvalho (8):
   drm: drm_atomic.c: Adjust end of block comment
   drm: drm_auth.c: Adjust end of block comment
   drm: drm_bufs.c: Adjust end of block comment
   drm: drm_connector.c: Adjust end of block comment
   drm: drm_context.c: Adjust end of block comment
   drm: drm_atomic_uapi.c: Use tabs for code indents
   drm: drm_blend.c: Use tabs for code indents
   drm: drm_connector.c: Use tabs for code indents

Bernard Zhao (2):
   drm/gud: cleanup coding style a bit
   drm/vmwgfx: use min_t to replace min

Bhaskar Chowdhury (1):
   drm/vmwgfx: Fix a typo

Christian König (17):
   drm/ttm: make global mutex and use count static
   drm/ttm: fix return value check
   drm/ttm: re-add debugfs tt_shrink file
   drm/amdgpu: make sure we unpin the UVD BO
   drm/amdgpu: freeing pinned objects is illegal now
   drm/ttm: warn stricter about freeing pinned BOs
   drm/nouveau: use bo->base.size instead of mem->num_pages
   drm/amdgpu: check base size instead of mem.num_pages
   drm/ttm: remove special handling for non GEM drivers
   drm/ttm: minor range manager coding style clean ups
   drm/ttm: move the page_alignment into the BO v2
   drm/ttm: cleanup ttm_agp_backend
   drm/ttm: add ttm_sys_manager v3
   drm/ttm: always initialize the full ttm_resource v2
   drm/ttm: properly allocate sys resource during swapout
   drm/ttm: fix warning in new sys man
   MAINTAINERS: Add Xinhui Pan as another AMDGPU contact

Christophe JAILLET (1):
   

Re: [PULL] drm-misc-next-fixes

2021-04-29 Thread Maxime Ripard
On Wed, Apr 28, 2021 at 04:57:26PM -0400, Alex Deucher wrote:
> On Mon, Apr 26, 2021 at 3:35 AM Maxime Ripard  wrote:
> >
> > Hi Alex,
> >
> > On Thu, Apr 22, 2021 at 12:40:10PM -0400, Alex Deucher wrote:
> > > On Thu, Apr 22, 2021 at 12:33 PM Maxime Ripard  wrote:
> > > >
> > > > Hi Dave, Daniel,
> > > >
> > > > Here's this week drm-misc-next-fixes PR, for the next merge window
> > > >
> > >
> > > Can we also cherry-pick this patch:
> > > https://cgit.freedesktop.org/drm/drm-misc/commit/?id=d510c88cfbb294d2b1e2d0b71576e9b79d0e2e83
> > > It should have really gone into drm-misc-next-fixes rather than
> > > drm-misc-next, but I misjudged the timing.
> >
> > Yeah, just cherry-pick it, I'll keep sending PR during the merge window :)
> 
> Thanks, I cherry-picked it yesterday.

I sent the PR earlier :)

Maxime


signature.asc
Description: PGP signature
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


Re: [PULL] drm-misc-next-fixes

2021-04-28 Thread Alex Deucher
On Mon, Apr 26, 2021 at 3:35 AM Maxime Ripard  wrote:
>
> Hi Alex,
>
> On Thu, Apr 22, 2021 at 12:40:10PM -0400, Alex Deucher wrote:
> > On Thu, Apr 22, 2021 at 12:33 PM Maxime Ripard  wrote:
> > >
> > > Hi Dave, Daniel,
> > >
> > > Here's this week drm-misc-next-fixes PR, for the next merge window
> > >
> >
> > Can we also cherry-pick this patch:
> > https://cgit.freedesktop.org/drm/drm-misc/commit/?id=d510c88cfbb294d2b1e2d0b71576e9b79d0e2e83
> > It should have really gone into drm-misc-next-fixes rather than
> > drm-misc-next, but I misjudged the timing.
>
> Yeah, just cherry-pick it, I'll keep sending PR during the merge window :)

Thanks, I cherry-picked it yesterday.

Alex
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


Re: [PULL] drm-misc-next-fixes

2021-04-26 Thread Maxime Ripard
Hi Alex,

On Thu, Apr 22, 2021 at 12:40:10PM -0400, Alex Deucher wrote:
> On Thu, Apr 22, 2021 at 12:33 PM Maxime Ripard  wrote:
> >
> > Hi Dave, Daniel,
> >
> > Here's this week drm-misc-next-fixes PR, for the next merge window
> >
> 
> Can we also cherry-pick this patch:
> https://cgit.freedesktop.org/drm/drm-misc/commit/?id=d510c88cfbb294d2b1e2d0b71576e9b79d0e2e83
> It should have really gone into drm-misc-next-fixes rather than
> drm-misc-next, but I misjudged the timing.

Yeah, just cherry-pick it, I'll keep sending PR during the merge window :)

Maxime


signature.asc
Description: PGP signature
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


Re: [PULL] drm-misc-next-fixes

2021-04-22 Thread Alex Deucher
On Thu, Apr 22, 2021 at 12:33 PM Maxime Ripard  wrote:
>
> Hi Dave, Daniel,
>
> Here's this week drm-misc-next-fixes PR, for the next merge window
>

Can we also cherry-pick this patch:
https://cgit.freedesktop.org/drm/drm-misc/commit/?id=d510c88cfbb294d2b1e2d0b71576e9b79d0e2e83
It should have really gone into drm-misc-next-fixes rather than
drm-misc-next, but I misjudged the timing.

Thanks,

Alex

> Thanks!
> Maxime
>
> drm-misc-next-fixes-2021-04-22:
> A few fixes for the next merge window, with some build fixes for anx7625
> and lt8912b bridges, incorrect error handling for lt8912b and TTM, and
> one fix for TTM page limit accounting.
> The following changes since commit 9c0fed84d5750e1eea6c664e073ffa2534a17743:
>
>   Merge tag 'drm-intel-next-2021-04-01' of 
> git://anongit.freedesktop.org/drm/drm-intel into drm-next (2021-04-08 
> 14:02:21 +1000)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-misc 
> tags/drm-misc-next-fixes-2021-04-22
>
> for you to fetch changes up to a4394b6d0a273941a75ebe86a86d6416d536ed0f:
>
>   drm/ttm: Don't count pages in SG BOs against pages_limit (2021-04-21 
> 15:35:20 +0200)
>
> 
> A few fixes for the next merge window, with some build fixes for anx7625
> and lt8912b bridges, incorrect error handling for lt8912b and TTM, and
> one fix for TTM page limit accounting.
>
> 
> Adrien Grassein (1):
>   drm/bridge: lt8912b: fix incorrect handling of of_* return values
>
> Christian König (1):
>   drm/ttm: fix return value check
>
> Felix Kuehling (1):
>   drm/ttm: Don't count pages in SG BOs against pages_limit
>
> Randy Dunlap (2):
>   drm: bridge: fix ANX7625 use of mipi_dsi_() functions
>   drm: bridge: fix LONTIUM use of mipi_dsi_() functions
>
>  drivers/gpu/drm/bridge/Kconfig   |  3 +++
>  drivers/gpu/drm/bridge/analogix/Kconfig  |  1 +
>  drivers/gpu/drm/bridge/lontium-lt8912b.c | 32 
> +---
>  drivers/gpu/drm/ttm/ttm_tt.c | 29 +++--
>  4 files changed, 40 insertions(+), 25 deletions(-)
> ___
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


Re: [PULL] drm-misc-next

2021-01-20 Thread Daniel Vetter
On Tue, Jan 19, 2021 at 12:39:22PM +0100, Maarten Lankhorst wrote:
> drm-misc-next-2021-01-19:
> drm-misc-next for v5.12:
> 
> UAPI Changes:
> - Fix fourcc macro for amlogic video fbc.
> 
> Cross-subsystem Changes:
> - Export pci_rebar_bytes_to_size.
> - Add a PCI quirk to increase bar0 for RX 5600 XT Pulse to max possible size.
> - Convert devicetree bindings to use the OF graph schema.
> - Update s6e63m0 bindings.
> - Make omapfb2 DSI_CM incompatible with drm/omap2 DSI-CM because of
>   module conflicts.
> - Add Zack Rusin as vmwgfx maintainer.
> - Add CONFIG_DMABUF_DEBUG for validating dma-buf users don't loo kat struct 
> page when importing or detaching.
> 
> Core Changes:
> - Remove references to drm_device.pdev
> - Fix regression in ttm_bo_move_to_lru_tail().
> - Assorted docbook updates.
> - Do not send dp-mst hotplug events on error when probing.
> - Move some agp macros to agpsupport.c, so it's not always compiled.
> - Move drm_need_swiotlb.h to drm_cache.c
> - Only build drm_memory.o for legacy drivers, and move CONFIG_DRM_VM to 
> legacy.
> - Nuke drm_device.hose
> - Warn when the ttm resource manager is non-empty when disabling.
> - Assorted small fixes.
> 
> Driver Changes:
> - Small assorted fixes in radeon, v3d, hisilicon, mipi-dbi, panfrost, hibmc, 
> vc4, amdgpu, vkms, vmwgfx.
> - Move hisilicon to use simple encode.
> - Add writeback connector to vkms.
> - Add support for BT2020 to DE3.
> - Use gem prime mmap helpers in vc4, and move the mmap function upwards.
> - Use managed drm device, and cleanup error paths and display registers in 
> vmwgfx.
> - Use correct bus_format and connector_type for innolux_n116bge.
> - Fix a lot of warnings with W=1 (Lee Jones)
> The following changes since commit cb3cfbf79aff7decb4e5ee69a7c74864497f61dc:
> 
>   Merge tag 'drm-misc-next-2021-01-06' of 
> git://anongit.freedesktop.org/drm/drm-misc into drm-next (2021-01-07 13:40:20 
> +0100)

Pulled, thanks.
-Daniel

> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2021-01-19
> 
> for you to fetch changes up to c31eb10fd5aee124b78ce72ebf7d0cd13fca6095:
> 
>   drm/amdgpu: Remove accidentally added small unused hunk. (2021-01-19 
> 11:18:39 +0100)
> 
> 
> drm-misc-next for v5.12:
> 
> UAPI Changes:
> - Fix fourcc macro for amlogic video fbc.
> 
> Cross-subsystem Changes:
> - Export pci_rebar_bytes_to_size.
> - Add a PCI quirk to increase bar0 for RX 5600 XT Pulse to max possible size.
> - Convert devicetree bindings to use the OF graph schema.
> - Update s6e63m0 bindings.
> - Make omapfb2 DSI_CM incompatible with drm/omap2 DSI-CM because of
>   module conflicts.
> - Add Zack Rusin as vmwgfx maintainer.
> - Add CONFIG_DMABUF_DEBUG for validating dma-buf users don't loo kat struct 
> page when importing or detaching.
> 
> Core Changes:
> - Remove references to drm_device.pdev
> - Fix regression in ttm_bo_move_to_lru_tail().
> - Assorted docbook updates.
> - Do not send dp-mst hotplug events on error when probing.
> - Move some agp macros to agpsupport.c, so it's not always compiled.
> - Move drm_need_swiotlb.h to drm_cache.c
> - Only build drm_memory.o for legacy drivers, and move CONFIG_DRM_VM to 
> legacy.
> - Nuke drm_device.hose
> - Warn when the ttm resource manager is non-empty when disabling.
> - Assorted small fixes.
> 
> Driver Changes:
> - Small assorted fixes in radeon, v3d, hisilicon, mipi-dbi, panfrost, hibmc, 
> vc4, amdgpu, vkms, vmwgfx.
> - Move hisilicon to use simple encode.
> - Add writeback connector to vkms.
> - Add support for BT2020 to DE3.
> - Use gem prime mmap helpers in vc4, and move the mmap function upwards.
> - Use managed drm device, and cleanup error paths and display registers in 
> vmwgfx.
> - Use correct bus_format and connector_type for innolux_n116bge.
> - Fix a lot of warnings with W=1 (Lee Jones)
> 
> 
> Andrey Grodzovsky (2):
>   drm: Unamp the entire device address space on device unplug
>   drm/sched: Cancel and flush all outstanding jobs before finish.
> 
> Chia-I Wu (2):
>   drm/virtio: make sure context is created in gem open
>   drm/virtio: fix prime export for vram objects
> 
> Colin Ian King (1):
>   drm/vkms: Fix missing kmalloc allocation failure check
> 
> Daniel Vetter (4):
>   drm/vmwgfx: Drop svga_lock
>   drm/vmwgfx: Always evict vram _before_ disabling it
>   drm/ttm: WARN_ON non-empty lru when disabling a resource manager
>   dma-buf: Add debug option
> 
> Darren Salt (1):
>   PCI: Export pci_rebar_get_possible_sizes()
> 
> Giulio Benetti (1):
>   drm/sun4i: tcon: fix inverted DCLK polarity
> 
> Heiko Stuebner (1):
>   drm/panel: panel-simple: add bus-format and connector-type to Innolux 
> n116bge
> 
> Jernej Skrabec (3):
>   drm/sun4i: csc: Rework DE3 CSC macros
>   drm/sun4i: de2/de3: Remove redundant CSC 

Re: [PULL] drm-misc-next

2021-01-07 Thread Daniel Vetter
On Wed, Jan 06, 2021 at 12:13:12PM +0100, Maarten Lankhorst wrote:
> drm-misc-next-2021-01-06:
> drm-misc-next for v5.12:
> 
> Core Changes:
> - Lots of drm documentation updates by Simor Ser.

Extra kudos for documentation work!

> - Require that each crtc has a unique primary plane.
> - Add fixme that fbdev_generic_setup is confusing.
> 
> Driver Changes:
> - Update addresses for TI display drivers maintainers.
> - Make DRM_VIRTIO_GPU select VIRTIO.
> - Small fixes to qxl, virtio, hisilicon, tve200, panel/s6e63m0.
> The following changes since commit 5fbd41d3bf123af6a135bdea564087ec0f563eb0:
> 
>   Merge tag 'drm-misc-next-2020-11-27-1' of 
> git://anongit.freedesktop.org/drm/drm-misc into drm-next (2020-12-15 10:21:48 
> +0100)

Pulled, thanks.
-Daniel

> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2021-01-06
> 
> for you to fetch changes up to cf9a4be47fd14473b4d0dd6f494ed7279c2bc8a0:
> 
>   drm/doc: render drm.h uapi docs (2021-01-05 14:22:26 +0100)
> 
> 
> drm-misc-next for v5.12:
> 
> Core Changes:
> - Lots of drm documentation updates by Simor Ser.
> - Require that each crtc has a unique primary plane.
> - Add fixme that fbdev_generic_setup is confusing.
> 
> Driver Changes:
> - Update addresses for TI display drivers maintainers.
> - Make DRM_VIRTIO_GPU select VIRTIO.
> - Small fixes to qxl, virtio, hisilicon, tve200, panel/s6e63m0.
> 
> 
> Arnd Bergmann (1):
>   drm/kmb: fix array bounds warning
> 
> Bernard Zhao (1):
>   via/via_irq: use __func__ to replace string function name
> 
> Chia-I Wu (1):
>   drm/virtio: align blob resources to page sizes
> 
> Christian König (13):
>   drm/radeon: fix check order in radeon_bo_move
>   drm/radeon: stop using pages with drm_prime_sg_to_page_addr_arrays v2
>   drm/amdgpu: stop using pages with drm_prime_sg_to_page_addr_arrays
>   drm/nouveau: stop using pages with drm_prime_sg_to_page_addr_arrays v2
>   drm/vmwgfx: switch to ttm_sg_tt_init
>   drm/qxl: switch to ttm_sg_tt_init
>   drm/ttm: nuke ttm_dma_tt_init
>   drm/prime: split array import functions v4
>   drm/ttm/drivers: remove unecessary ttm_module.h include v2
>   drm/ttm: stop destroying pinned ghost object
>   drm/ttm: cleanup BO size handling v3
>   drm/ttm: use pin_count more extensively
>   drm/ttm: cleanup LRU handling further
> 
> Chuhong Yuan (1):
>   drm/fb-helper: Add missed unlocks in setcmap_legacy()
> 
> Dafna Hirschfeld (2):
>   drm/rockchip: for error print, use the correct device pointer
>   drm/rockchip: fix typo in Kconfig 's/HDMI/dsi/'
> 
> Dan Carpenter (3):
>   drm/kmb: Remove an unnecessary NULL check
>   gma500: clean up error handling in init
>   drm/panel: khadas: Fix error code in khadas_ts050_panel_add()
> 
> Daniel Vetter (10):
>   drm/ttm: Warn on pinning without holding a reference
>   drm/nouveau: Drop mutex_lock_nested for atomic
>   dma-buf: Fix kerneldoc formatting
>   drm/vkms: Unset preferred_depth
>   drm/amdkfd: fix ttm size refactor fallout
>   dma-buf: Remove kmap kerneldoc vestiges
>   dma-buf: some kerneldoc formatting fixes
>   dma-buf: begin/end_cpu might lock the dma_resv lock
>   dma-buf: doc polish for pin/unpin
>   drm/fb-helper: Add a FIXME that generic_setup is very confusing
> 
> Dave Stevenson (4):
>   drm/vc4: dsi: Correct DSI register definition
>   drm/vc4: dsi: Add support for DSI0
>   dt-bindings: Add compatible for BCM2711 DSI1
>   drm/vc4: dsi: Add configuration for BCM2711 DSI1
> 
> Douglas Anderson (7):
>   drm: panel: simple: Fixup the struct panel_desc kernel doc
>   drm: panel: simple: Defer unprepare delay till next prepare to shorten 
> it
>   drm: panel: simple: Allow specifying the delay from prepare to enable
>   dt-bindings: dt-bindings: display: simple: Add BOE NV110WTM-N61
>   drm: panel: simple: Add BOE NV110WTM-N61
>   drm: panel: Fully transition panel_desc kerneldoc to inline style
>   drm: panel: add flags to BOE NV110WTM-N61
> 
> Enrico Weigelt, metux IT consult (1):
>   drivers: gpu: drm: virtio: fix dependency of DRM_VIRTIO_GPU on VIRTIO
> 
> Guido Günther (6):
>   drm/panel: st7703: Use dev_err_probe
>   drm/panel: mantix: Tweak init sequence
>   drm/panel: mantix: Allow to specify default mode for different panels
>   drm/panel: mantix: Support panel from Shenzhen Yashi Changhua 
> Intelligent Technology Co
>   dt-bindings: vendor-prefixes: Add ys vendor prefix
>   dt-bindings: display: mantix: Add compatible for panel from YS
> 
> Gurchetan Singh (3):
>   drm/virtio: virtio_{blah} --> virtio_gpu_{blah}
>   drm/virtio: rework virtio_fence_signaled
>   drm/virtio: consider dma-fence context when signaling
> 
> Jialin 

Re: [PULL] drm-misc-next

2021-01-07 Thread Daniel Vetter
On Thu, Dec 17, 2020 at 11:12 AM Maarten Lankhorst
 wrote:
>
> drm-misc-next-2020-12-17:
> drm-misc-next for v5.12:
>
> UAPI Changes:
> - Not necessarily one, but we document that userspace needs to force probe 
> connectors.
>
> Cross-subsystem Changes:
> - Require FB_ATY_CT for aty on sparc64.
> - video: Fix documentation, and a few compiler warnings.
> - Add devicetree bindings for DP connectors.
> - dma-buf: Update kernel-doc, and add might_lock for resv objects in 
> begin/end_cpu_access.
>
> Core Changes:
> - ttm: Warn when releasing a pinned bo.
> - ttm: Cleanup bo size handling.
> - cma-helper: Remove prime infix, and implement mmap as GEM CMA functions.
> - Split drm_prime_sg_to_page_addr_arrays into 2 functions.
> - Add a new api to install irq using devm.
> - Update panel kerneldoc to inline style.
> - Add DP support to drm/bridge.
> - Assorted small fixes to ttm, fb-helper, scheduler.
> - Add atomic_commit_setup function callback.
> - Automatically use the atomic gamma_set, instead of forcing drivers to 
> declare the default atomic version.
> - Allow using degamma for legacy gamma if gamma is not available.
> - Clarify that primary/cursor planes are not tied to 1 crtc (depending on 
> possible_crtcs).
> - ttm: Cleanup the lru handler.
>
> Driver Changes:
> - Add pm support to ingenic.
> - Assorted small fixes in radeon, via, rockchip, omap2fb, kmb, gma500, 
> nouveau, virtio, hisilicon, ingenic, s6e63m0 panel, ast, udlfb.
> - Add BOE NV110WTM-N61, ys57pss36bh5gq, Khadas TS050 panels.
> - Stop using pages with drm_prime_sg_to_page_addr_arrays, and switch all 
> callers to use ttm_sg_tt_init.
> - Cleanup compiler and docbook warnings in a lot of fbdev devices.
> - Use the drmm_vram_helper in hisilicon.
> - Add support for BCM2711 DSI1 in vc4.
> - Add support for 8-bit delta RGB panels to ingenic.
> - Add documentation on how to test vkms.
> - Convert vc4 to atomic helpers.
> - Use degamma instead of gamma table in omap, to add support for CTM and 
> color encoding/range properties.
> - Rework omap DSI code, and merge all omapdrm modules now that the last omap 
> panel is now a drm panel.
> - More refactoring of omap dsi code.
> - Enable 10/12 bpc outputs in vc4.
> The following changes since commit 5fbd41d3bf123af6a135bdea564087ec0f563eb0:
>
>   Merge tag 'drm-misc-next-2020-11-27-1' of 
> git://anongit.freedesktop.org/drm/drm-misc into drm-next (2020-12-15 10:21:48 
> +0100)

Pulled, thanks.
-Daniel

>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2020-12-17
>
> for you to fetch changes up to c545781e1c55ab680dcc49c37212d5327b9d6812:
>
>   dma-buf: doc polish for pin/unpin (2020-12-16 11:28:34 +0100)
>
> 
> drm-misc-next for v5.12:
>
> UAPI Changes:
> - Not necessarily one, but we document that userspace needs to force probe 
> connectors.
>
> Cross-subsystem Changes:
> - Require FB_ATY_CT for aty on sparc64.
> - video: Fix documentation, and a few compiler warnings.
> - Add devicetree bindings for DP connectors.
> - dma-buf: Update kernel-doc, and add might_lock for resv objects in 
> begin/end_cpu_access.
>
> Core Changes:
> - ttm: Warn when releasing a pinned bo.
> - ttm: Cleanup bo size handling.
> - cma-helper: Remove prime infix, and implement mmap as GEM CMA functions.
> - Split drm_prime_sg_to_page_addr_arrays into 2 functions.
> - Add a new api to install irq using devm.
> - Update panel kerneldoc to inline style.
> - Add DP support to drm/bridge.
> - Assorted small fixes to ttm, fb-helper, scheduler.
> - Add atomic_commit_setup function callback.
> - Automatically use the atomic gamma_set, instead of forcing drivers to 
> declare the default atomic version.
> - Allow using degamma for legacy gamma if gamma is not available.
> - Clarify that primary/cursor planes are not tied to 1 crtc (depending on 
> possible_crtcs).
> - ttm: Cleanup the lru handler.
>
> Driver Changes:
> - Add pm support to ingenic.
> - Assorted small fixes in radeon, via, rockchip, omap2fb, kmb, gma500, 
> nouveau, virtio, hisilicon, ingenic, s6e63m0 panel, ast, udlfb.
> - Add BOE NV110WTM-N61, ys57pss36bh5gq, Khadas TS050 panels.
> - Stop using pages with drm_prime_sg_to_page_addr_arrays, and switch all 
> callers to use ttm_sg_tt_init.
> - Cleanup compiler and docbook warnings in a lot of fbdev devices.
> - Use the drmm_vram_helper in hisilicon.
> - Add support for BCM2711 DSI1 in vc4.
> - Add support for 8-bit delta RGB panels to ingenic.
> - Add documentation on how to test vkms.
> - Convert vc4 to atomic helpers.
> - Use degamma instead of gamma table in omap, to add support for CTM and 
> color encoding/range properties.
> - Rework omap DSI code, and merge all omapdrm modules now that the last omap 
> panel is now a drm panel.
> - More refactoring of omap dsi code.
> - Enable 10/12 bpc outputs in vc4.
>
> 
> Arnd 

Re: [PULL] drm-misc-next-fixes

2021-01-04 Thread Thomas Zimmermann

Hi,

it looks like this PR has not been merged yet.

Best regard
Thomas

Am 22.12.20 um 20:13 schrieb Thomas Zimmermann:

Hi Dave and Daniel,

here's this week's PR for drm-misc-next-fixes.

Best regards
Thomas

drm-misc-next-fixes-2020-12-22:
Short summary of fixes pull:

  * dma-buf: Include  for building on MIPS
  * komeda: Fix order of operation in commit tail; Fix NULL-pointer and
out-of-bounds access; Cleanups
  * ttm: Fix an unused-function warning
The following changes since commit ee46d16d2e40bebc2aa790fd7b6a056466ff895c:

   drm: mxsfb: Silence -EPROBE_DEFER while waiting for bridge (2020-12-15 
11:01:10 +0100)

are available in the Git repository at:

   git://anongit.freedesktop.org/drm/drm-misc 
tags/drm-misc-next-fixes-2020-12-22

for you to fetch changes up to be3e477effba636ad25dcd244db264c6cd5c1f36:

   drm/komeda: Fix bit check to import to value of proper type (2020-12-18 
16:36:00 +)


Short summary of fixes pull:

  * dma-buf: Include  for building on MIPS
  * komeda: Fix order of operation in commit tail; Fix NULL-pointer and
out-of-bounds access; Cleanups
  * ttm: Fix an unused-function warning


Arnd Bergmann (1):
   drm/ttm: fix unused function warning

Carsten Haitzler (3):
   drm/komeda: Remove useless variable assignment
   drm/komeda: Handle NULL pointer access code path in error case
   drm/komeda: Fix bit check to import to value of proper type

Christian König (1):
   drm/qxl: don't allocate a dma_address array

James Qian Wang (1):
   drm/komeda: Correct the sequence of hw_done() and flip_done()

John Stultz (1):
   dma-buf: cma_heap: Include linux/vmalloc.h to fix build failures on MIPS

  drivers/dma-buf/heaps/cma_heap.c   |  1 +
  drivers/gpu/drm/arm/display/komeda/komeda_dev.c|  1 -
  drivers/gpu/drm/arm/display/komeda/komeda_kms.c|  4 +--
  .../gpu/drm/arm/display/komeda/komeda_pipeline.c   |  3 ++-
  .../drm/arm/display/komeda/komeda_pipeline_state.c |  4 +--
  drivers/gpu/drm/qxl/qxl_ttm.c  |  2 +-
  drivers/gpu/drm/ttm/ttm_pool.c | 29 +++---
  7 files changed, 22 insertions(+), 22 deletions(-)

--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel



--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer



OpenPGP_signature
Description: OpenPGP digital signature
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


Re: [PULL] drm-misc-next-fixes

2020-12-15 Thread Daniel Vetter
On Tue, Dec 15, 2020 at 02:04:31PM +0100, Thomas Zimmermann wrote:
> Hi Dave and Daniel,
> 
> here's this week's PR for drm-misc-next-fixes. IIRC the radeon fix is
> already in drm-misc-next.

Pulled, and also your previous -next pull which got stuck somewhere.

Thanks, Daniel

> 
> Best regards
> Thomas
> 
> drm-misc-next-fixes-2020-12-15:
> Short summary of fixes pull (less than what git shortlog provides):
> 
>  * dma-buf: Fix docs
>  * mxsfb: Silence invalid error message
>  * radeon: Fix TTM multihop
> 
> The following changes since commit 05faf1559de52465f1e753e31883aa294e6179c1:
> 
>   drm/imx/dcss: allow using nearest neighbor interpolation scaling 
> (2020-11-26 11:29:44 +0100)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc 
> tags/drm-misc-next-fixes-2020-12-15
> 
> for you to fetch changes up to ee46d16d2e40bebc2aa790fd7b6a056466ff895c:
> 
>   drm: mxsfb: Silence -EPROBE_DEFER while waiting for bridge (2020-12-15 
> 11:01:10 +0100)
> 
> 
> Short summary of fixes pull (less than what git shortlog provides):
> 
>  * dma-buf: Fix docs
>  * mxsfb: Silence invalid error message
>  * radeon: Fix TTM multihop
> 
> 
> Christian König (1):
>   drm/radeon: fix check order in radeon_bo_move
> 
> Daniel Vetter (1):
>   dma-buf: Fix kerneldoc formatting
> 
> Guido Günther (1):
>   drm: mxsfb: Silence -EPROBE_DEFER while waiting for bridge
> 
>  Documentation/driver-api/dma-buf.rst |  2 +-
>  drivers/gpu/drm/mxsfb/mxsfb_drv.c| 10 +++
>  drivers/gpu/drm/radeon/radeon_ttm.c  | 54 
> 
>  include/linux/dma-buf-map.h  |  2 +-
>  4 files changed, 30 insertions(+), 38 deletions(-)
> 
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


Re: [PULL] drm-misc-next

2020-10-27 Thread Thomas Zimmermann


Am 27.10.20 um 11:09 schrieb Thomas Zimmermann:
> Hi Dave and Daniel,
> 
> with 5.11-rc tagged, here's the first PR for drm-misc-next for what will 
> become

s/5.11-rc1/5.10-rc1

> Linux 5.11. What sticks out is the large number of TTM refactoring patches, 
> and
> the conversion to GEM object functions. THe framebuffer code is now orphaned.
> There are tons of small changes for compiler warnings throughout fbdev
> 
> Best regards
> Thomas
> 
> 
> drm-misc-next-2020-10-27:
> drm-misc-next for 5.11:
> 
> UAPI Changes:
> 
>   - doc: rules for EBUSY on non-blocking commits; requirements for fourcc
> modifiers; on parsing EDID
>   - fbdev/sbuslib: Remove unused FBIOSCURSOR32
>   - fourcc: deprecate DRM_FORMAT_MOD_NONE
>   - virtio: Support blob resources for memory allocations; Expose host-visible
> and cross-device features
> 
> Cross-subsystem Changes:
> 
>   - devicetree: Add vendor Prefix for Yes Optoelectronics, Shanghai Top 
> Display
> Optoelectronics
>   - dma-buf: Add struct dma_buf_map that stores DMA pointer and I/O-memory 
> flag;
> dma_buf_vmap()/vunmap() return address in dma_buf_map; Use struct_size() 
> macro
> 
> Core Changes:
> 
>   - atomic: pass full state to CRTC atomic enable/disable; warn for EBUSY 
> during
> non-blocking commits
>   - dp: Prepare for DP 2.0 DPCD
>   - dp_mst: Receive extended DPCD caps
>   - dma-buf: Documentation
>   - doc: Format modifiers; dma-buf-map; Cleanups
>   - fbdev: Don't use compat_alloc_user_space(); mark as orphaned
>   - fb-helper: Take lock in drm_fb_helper_restore_work_fb()
>   - gem: Convert implementation and drivers to GEM object functions, remove
> GEM callbacks from struct drm_driver (expect gem_prime_mmap)
>   - panel: Cleanups
>   - pci: Add legacy infix to drm_irq_by_busid()
>   - sched: Avoid infinite waits in drm_sched_entity_destroy()
>   - switcheroo: Cleanups
>   - ttm: Remove AGP support; Don't modify caching during swapout; Major
> refactoring of the implementation and API that affects all depending
> drivers; Add ttm_bo_wait_ctx(); Add ttm_bo_pin()/unpin() in favor of
> TTM_PL_FLAG_NO_EVICT; Remove ttm_bo_create(); Remove 
> fault_reserve_notify()
> callback; Push move() implementation into drivers; Remove 
> TTM_PAGE_FLAG_WRITE;
> Replace caching flags with init-time cache setting; Push ttm_tt_bind() 
> into
> drivers; Replace move_notify() with delete_mem_notify(); No overlapping 
> memcpy();
> no more ttm_set_populated()
>   - vram-helper: Fix BO top-down placement; TTM-related changes; Init GEM
> object functions with defaults; Default placement in system memory; 
> Cleanups
> 
> Driver Changes:
> 
>   - amdgpu: Use GEM object functions
>   - armada: Use GEM object functions
>   - aspeed: Configure output via sysfs; Init struct drm_driver with
>   - ast: Reload LUT after FB format changes
>   - bridge: Add driver and DT bindings for anx7625; Cleanups
>   - bridge/dw-hdmi: Constify ops
>   - bridge/ti-sn65dsi86: Add retries for link training
>   - bridge/lvds-codec: Add support for regulator
>   - bridge/tc358768: Restore connector support DRM_GEM_CMA_DRIVEROPS; Cleanups
>   - display/ti,j721e-dss: Add DT properies assigned-clocks, 
> assigned-clocks-parent and
> dma-coherent
>   - display/ti,am65s-dss: Add DT properies assigned-clocks, 
> assigned-clocks-parent and
> dma-coherent
>   - etnaviv: Use GEM object functions
>   - exynos: Use GEM object functions
>   - fbdev: Cleanups and compiler fixes throughout framebuffer drivers
>   - fbdev/cirrusfb: Avoid division by 0
>   - gma500: Use GEM object functions; Fix double-free of connector; Cleanups
>   - hisilicon/hibmc: I2C-based DDC support; Use to_hibmc_drm_device(); 
> Cleanups
>   - i915: Use GEM object functions
>   - imx/dcss: Init driver with DRM_GEM_CMA_DRIVER_OPS; Cleanups
>   - ingenic: Reset pixel clock when parent clock changes; support reserved
> memory; Alloc F0 and F1 DMA channels at once; Support different pixel 
> formats;
> Revert support for cached mmap buffers
> on F0/F1; support 30-bit/24-bit/8-bit-palette modes
>   - komeda: Use DEFINE_SHOW_ATTRIBUTE
>   - mcde: Detect platform_get_irq() errors
>   - mediatek: Use GEM object functions
>   - msm: Use GEM object functions
>   - nouveau: Cleanups; TTM-related changes; Use GEM object functions
>   - omapdrm: Use GEM object functions
>   - panel: Add driver and DT bindings for Novatak nt36672a; Add driver and DT
> bindings for YTC700TLAG-05-201C; Add driver and DT bindings for TDO 
> TL070WSH30;
> Cleanups
>   - panel/mantix: Fix reset; Fix deref of NULL pointer in mantix_get_modes()
>   - panel/otm8009a: Allow non-continuous dsi clock; Cleanups
>   - panel/rm68200: Allow non-continuous dsi clock; Fix mode to 50 FPS
>   - panfrost: Fix job timeout handling; Cleanups
>   - pl111: Use GEM object functions
>   - qxl: Cleanups; TTM-related changes; Pin new BOs with 
> ttm_bo_init_reserved()
>   - radeon: Cleanups; TTM-related changes; 

Re: [PULL] drm-misc-next

2020-08-30 Thread Daniel Vetter
On Wed, Aug 26, 2020 at 12:02 PM Jani Nikula
 wrote:
>
> On Thu, 20 Aug 2020, Maxime Ripard  wrote:
> > This PR diffstat is pretty massive since we merged 5.9-rc1 and it's not 
> > (yet?) in drm-next.
> >
> > I'm not entirely sure how to tackle this (if it causes an issue?).
> >
> > Let me know, thanks!
>
> Whatever Dave & Daniel say, but previously the rule of thumb has been to
> only ever do backmerges from drm-next. If you need a backmerge from
> Linus' tree, you ask for a backmerge to drm-next, and then backmerge
> that.

Yup. drm-misc docs even say that if you roll forward (or backmerge)
before it's in drm.git it's going to be a bit of a mess.
-Daniel

>
> BR,
> Jani.
>
> --
> Jani Nikula, Intel Open Source Graphics Center



-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


Re: [PULL] drm-misc-next

2020-08-26 Thread Jani Nikula
On Thu, 20 Aug 2020, Maxime Ripard  wrote:
> This PR diffstat is pretty massive since we merged 5.9-rc1 and it's not 
> (yet?) in drm-next.
>
> I'm not entirely sure how to tackle this (if it causes an issue?).
>
> Let me know, thanks!

Whatever Dave & Daniel say, but previously the rule of thumb has been to
only ever do backmerges from drm-next. If you need a backmerge from
Linus' tree, you ask for a backmerge to drm-next, and then backmerge
that.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


Re: [PULL] drm-misc-next

2020-04-21 Thread Thomas Zimmermann
Hi

Am 21.04.20 um 15:41 schrieb Daniel Vetter:
> On Tue, Apr 21, 2020 at 2:46 PM Thomas Zimmermann  wrote:
>>
>> Hi Dave, Daniel,
>>
>> just a friendly reminder to merge these changes. They don't seem to be
>> in the upstream tree yet.
> 
> Dave noticed and pinged me on irc that there's some changes in core mm
> in this one. That patch is correctly acked by akpm, but stuff like
> that should be highlighted in the pull summary. Essentially anything
> outside of what's officially maintainer by drm.git needs a special
> highlight (and double-checking by maintainers that all the right acks
> are there).

I see. I'll be more careful next time.

Best regards
Thomas

> 
> I'm assuming Dave is just going to edit the merge commit himself and
> doesn't need a new pull request.
> -Daniel
> 
>>
>> Best regards
>> Thomas
>>
>> Am 14.04.20 um 11:07 schrieb Thomas Zimmermann:
>>> Hi Dave, Daniel,
>>>
>>> with 5.7-rc1 being tagged, here's the first PR for drm-next-misc for what 
>>> will become Linux 5.8.
>>>
>>> Best regards
>>> Thomas
>>>
>>>
>>> drm-misc-next-2020-04-14:
>>> drm-misc-next for 5.8:
>>>
>>> UAPI Changes:
>>>
>>>   - drm: error out with EBUSY when device has existing master
>>>   - drm: rework SET_MASTER and DROP_MASTER perm handling
>>>
>>> Cross-subsystem Changes:
>>>
>>>   - fbdev: savage: fix -Wextra build warning
>>>   - video: omap2: Use scnprintf() for avoiding potential buffer overflow
>>>
>>> Core Changes:
>>>
>>>   - Remove drm_pci.h
>>>   - drm_pci_{alloc/free)() are now legacy
>>>   - Introduce managed DRM resourcesA
>>>   - Allow drivers to subclass struct drm_framebuffer
>>>   - Introduce struct drm_afbc_framebuffer and helpers
>>>   - fbdev: remove return value from generic fbdev setup
>>>   - Introduce simple-encoder helper
>>>   - vram-helpers: set fence on plane
>>>   - dp_mst: ACT timeout improvements
>>>   - dp_mst: Remove drm_dp_mst_has_audio()
>>>   - TTM: ttm_trace_dma_{map/unmap}() cleanups
>>>   - dma-buf: add flag for PCIP2P support
>>>   - EDID: Various improvements
>>>   - Encoder: cleanup semantics of possible_clones and possible_crtcs
>>>   - VBLANK documentation updates
>>>   - Writeback documentation updates
>>>
>>> Driver Changes:
>>>
>>>   - Convert several drivers to i2c_new_client_device()
>>>   - Drop explicit drm_mode_config_cleanup() calls from drivers
>>>   - Auto-release device structures with drmm_add_final_kfree()
>>>   - Init bfdev console after registering DRM device
>>>   - Make various .debugfs functions return 0 unconditionally; ignore errors
>>>   - video: Use scnprintf() to avoid buffer overflows
>>>   - Convert drivers to simple encoders
>>>
>>>   - drm/amdgpu: note that we can handle peer2peer DMA-buf
>>>   - drm/amdgpu: add support for exporting VRAM using DMA-buf v3
>>>   - drm/kirin: Revert change to register connectors
>>>   - drm/lima: Add optional devfreq and cooling device support
>>>   - drm/lima: Various improvements wrt. task handling
>>>   - drm/panel: nt39016: Support multiple modes and 50Hz
>>>   - drm/panel: Support Leadtek LTK050H3146W
>>>   - drm/rockchip: Add support for afbc
>>>   - drm/virtio: Various cleanups
>>>   - drm/hisilicon/hibmc: Enforce 128-byte stride alignment
>>>   - drm/qxl: Fix notify port address of cursor ring buffer
>>>   - drm/sun4i: Improvements to format handling
>>>   - drm/bridge: dw-hdmi: Various improvements
>>>
>>> The following changes since commit c2556238120bce8be37670e145226c12870a9e5a:
>>>
>>>   Merge branch 'feature/staging_sm5' of 
>>> git://people.freedesktop.org/~sroland/linux into drm-next (2020-03-25 
>>> 15:45:45 +1000)
>>>
>>> are available in the Git repository at:
>>>
>>>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2020-04-14
>>>
>>> for you to fetch changes up to 14d0066b845971db7d0ef03c86fefe4d5bf2:
>>>
>>>   drm: kirin: Revert change to add register connect helper functions 
>>> (2020-04-13 01:46:02 +)
>>>
>>> 
>>> drm-misc-next for 5.8:
>>>
>>> UAPI Changes:
>>>
>>>   - drm: error out with EBUSY when device has existing master
>>>   - drm: rework SET_MASTER and DROP_MASTER perm handling
>>>
>>> Cross-subsystem Changes:
>>>
>>>   - fbdev: savage: fix -Wextra build warning
>>>   - video: omap2: Use scnprintf() for avoiding potential buffer overflow
>>>
>>> Core Changes:
>>>
>>>   - Remove drm_pci.h
>>>   - drm_pci_{alloc/free)() are now legacy
>>>   - Introduce managed DRM resourcesA
>>>   - Allow drivers to subclass struct drm_framebuffer
>>>   - Introduce struct drm_afbc_framebuffer and helpers
>>>   - fbdev: remove return value from generic fbdev setup
>>>   - Introduce simple-encoder helper
>>>   - vram-helpers: set fence on plane
>>>   - dp_mst: ACT timeout improvements
>>>   - dp_mst: Remove drm_dp_mst_has_audio()
>>>   - TTM: ttm_trace_dma_{map/unmap}() cleanups
>>>   - dma-buf: add flag for PCIP2P support
>>>   - EDID: Various improvements
>>>   - Encoder: cleanup semantics of possible_clones 

Re: [PULL] drm-misc-next

2020-04-21 Thread Daniel Vetter
On Tue, Apr 21, 2020 at 2:46 PM Thomas Zimmermann  wrote:
>
> Hi Dave, Daniel,
>
> just a friendly reminder to merge these changes. They don't seem to be
> in the upstream tree yet.

Dave noticed and pinged me on irc that there's some changes in core mm
in this one. That patch is correctly acked by akpm, but stuff like
that should be highlighted in the pull summary. Essentially anything
outside of what's officially maintainer by drm.git needs a special
highlight (and double-checking by maintainers that all the right acks
are there).

I'm assuming Dave is just going to edit the merge commit himself and
doesn't need a new pull request.
-Daniel

>
> Best regards
> Thomas
>
> Am 14.04.20 um 11:07 schrieb Thomas Zimmermann:
> > Hi Dave, Daniel,
> >
> > with 5.7-rc1 being tagged, here's the first PR for drm-next-misc for what 
> > will become Linux 5.8.
> >
> > Best regards
> > Thomas
> >
> >
> > drm-misc-next-2020-04-14:
> > drm-misc-next for 5.8:
> >
> > UAPI Changes:
> >
> >   - drm: error out with EBUSY when device has existing master
> >   - drm: rework SET_MASTER and DROP_MASTER perm handling
> >
> > Cross-subsystem Changes:
> >
> >   - fbdev: savage: fix -Wextra build warning
> >   - video: omap2: Use scnprintf() for avoiding potential buffer overflow
> >
> > Core Changes:
> >
> >   - Remove drm_pci.h
> >   - drm_pci_{alloc/free)() are now legacy
> >   - Introduce managed DRM resourcesA
> >   - Allow drivers to subclass struct drm_framebuffer
> >   - Introduce struct drm_afbc_framebuffer and helpers
> >   - fbdev: remove return value from generic fbdev setup
> >   - Introduce simple-encoder helper
> >   - vram-helpers: set fence on plane
> >   - dp_mst: ACT timeout improvements
> >   - dp_mst: Remove drm_dp_mst_has_audio()
> >   - TTM: ttm_trace_dma_{map/unmap}() cleanups
> >   - dma-buf: add flag for PCIP2P support
> >   - EDID: Various improvements
> >   - Encoder: cleanup semantics of possible_clones and possible_crtcs
> >   - VBLANK documentation updates
> >   - Writeback documentation updates
> >
> > Driver Changes:
> >
> >   - Convert several drivers to i2c_new_client_device()
> >   - Drop explicit drm_mode_config_cleanup() calls from drivers
> >   - Auto-release device structures with drmm_add_final_kfree()
> >   - Init bfdev console after registering DRM device
> >   - Make various .debugfs functions return 0 unconditionally; ignore errors
> >   - video: Use scnprintf() to avoid buffer overflows
> >   - Convert drivers to simple encoders
> >
> >   - drm/amdgpu: note that we can handle peer2peer DMA-buf
> >   - drm/amdgpu: add support for exporting VRAM using DMA-buf v3
> >   - drm/kirin: Revert change to register connectors
> >   - drm/lima: Add optional devfreq and cooling device support
> >   - drm/lima: Various improvements wrt. task handling
> >   - drm/panel: nt39016: Support multiple modes and 50Hz
> >   - drm/panel: Support Leadtek LTK050H3146W
> >   - drm/rockchip: Add support for afbc
> >   - drm/virtio: Various cleanups
> >   - drm/hisilicon/hibmc: Enforce 128-byte stride alignment
> >   - drm/qxl: Fix notify port address of cursor ring buffer
> >   - drm/sun4i: Improvements to format handling
> >   - drm/bridge: dw-hdmi: Various improvements
> >
> > The following changes since commit c2556238120bce8be37670e145226c12870a9e5a:
> >
> >   Merge branch 'feature/staging_sm5' of 
> > git://people.freedesktop.org/~sroland/linux into drm-next (2020-03-25 
> > 15:45:45 +1000)
> >
> > are available in the Git repository at:
> >
> >   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2020-04-14
> >
> > for you to fetch changes up to 14d0066b845971db7d0ef03c86fefe4d5bf2:
> >
> >   drm: kirin: Revert change to add register connect helper functions 
> > (2020-04-13 01:46:02 +)
> >
> > 
> > drm-misc-next for 5.8:
> >
> > UAPI Changes:
> >
> >   - drm: error out with EBUSY when device has existing master
> >   - drm: rework SET_MASTER and DROP_MASTER perm handling
> >
> > Cross-subsystem Changes:
> >
> >   - fbdev: savage: fix -Wextra build warning
> >   - video: omap2: Use scnprintf() for avoiding potential buffer overflow
> >
> > Core Changes:
> >
> >   - Remove drm_pci.h
> >   - drm_pci_{alloc/free)() are now legacy
> >   - Introduce managed DRM resourcesA
> >   - Allow drivers to subclass struct drm_framebuffer
> >   - Introduce struct drm_afbc_framebuffer and helpers
> >   - fbdev: remove return value from generic fbdev setup
> >   - Introduce simple-encoder helper
> >   - vram-helpers: set fence on plane
> >   - dp_mst: ACT timeout improvements
> >   - dp_mst: Remove drm_dp_mst_has_audio()
> >   - TTM: ttm_trace_dma_{map/unmap}() cleanups
> >   - dma-buf: add flag for PCIP2P support
> >   - EDID: Various improvements
> >   - Encoder: cleanup semantics of possible_clones and possible_crtcs
> >   - VBLANK documentation updates
> >   - Writeback documentation updates
> >
> > Driver Changes:
> >
> >   - Convert 

Re: [PULL] drm-misc-next

2020-04-21 Thread Thomas Zimmermann
Hi Dave, Daniel,

just a friendly reminder to merge these changes. They don't seem to be
in the upstream tree yet.

Best regards
Thomas

Am 14.04.20 um 11:07 schrieb Thomas Zimmermann:
> Hi Dave, Daniel,
> 
> with 5.7-rc1 being tagged, here's the first PR for drm-next-misc for what 
> will become Linux 5.8.
> 
> Best regards
> Thomas
> 
> 
> drm-misc-next-2020-04-14:
> drm-misc-next for 5.8:
> 
> UAPI Changes:
> 
>   - drm: error out with EBUSY when device has existing master
>   - drm: rework SET_MASTER and DROP_MASTER perm handling
> 
> Cross-subsystem Changes:
> 
>   - fbdev: savage: fix -Wextra build warning
>   - video: omap2: Use scnprintf() for avoiding potential buffer overflow
> 
> Core Changes:
> 
>   - Remove drm_pci.h
>   - drm_pci_{alloc/free)() are now legacy
>   - Introduce managed DRM resourcesA
>   - Allow drivers to subclass struct drm_framebuffer
>   - Introduce struct drm_afbc_framebuffer and helpers
>   - fbdev: remove return value from generic fbdev setup
>   - Introduce simple-encoder helper
>   - vram-helpers: set fence on plane
>   - dp_mst: ACT timeout improvements
>   - dp_mst: Remove drm_dp_mst_has_audio()
>   - TTM: ttm_trace_dma_{map/unmap}() cleanups
>   - dma-buf: add flag for PCIP2P support
>   - EDID: Various improvements
>   - Encoder: cleanup semantics of possible_clones and possible_crtcs
>   - VBLANK documentation updates
>   - Writeback documentation updates
> 
> Driver Changes:
> 
>   - Convert several drivers to i2c_new_client_device()
>   - Drop explicit drm_mode_config_cleanup() calls from drivers
>   - Auto-release device structures with drmm_add_final_kfree()
>   - Init bfdev console after registering DRM device
>   - Make various .debugfs functions return 0 unconditionally; ignore errors
>   - video: Use scnprintf() to avoid buffer overflows
>   - Convert drivers to simple encoders
> 
>   - drm/amdgpu: note that we can handle peer2peer DMA-buf
>   - drm/amdgpu: add support for exporting VRAM using DMA-buf v3
>   - drm/kirin: Revert change to register connectors
>   - drm/lima: Add optional devfreq and cooling device support
>   - drm/lima: Various improvements wrt. task handling
>   - drm/panel: nt39016: Support multiple modes and 50Hz
>   - drm/panel: Support Leadtek LTK050H3146W
>   - drm/rockchip: Add support for afbc
>   - drm/virtio: Various cleanups
>   - drm/hisilicon/hibmc: Enforce 128-byte stride alignment
>   - drm/qxl: Fix notify port address of cursor ring buffer
>   - drm/sun4i: Improvements to format handling
>   - drm/bridge: dw-hdmi: Various improvements
> 
> The following changes since commit c2556238120bce8be37670e145226c12870a9e5a:
> 
>   Merge branch 'feature/staging_sm5' of 
> git://people.freedesktop.org/~sroland/linux into drm-next (2020-03-25 
> 15:45:45 +1000)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2020-04-14
> 
> for you to fetch changes up to 14d0066b845971db7d0ef03c86fefe4d5bf2:
> 
>   drm: kirin: Revert change to add register connect helper functions 
> (2020-04-13 01:46:02 +)
> 
> 
> drm-misc-next for 5.8:
> 
> UAPI Changes:
> 
>   - drm: error out with EBUSY when device has existing master
>   - drm: rework SET_MASTER and DROP_MASTER perm handling
> 
> Cross-subsystem Changes:
> 
>   - fbdev: savage: fix -Wextra build warning
>   - video: omap2: Use scnprintf() for avoiding potential buffer overflow
> 
> Core Changes:
> 
>   - Remove drm_pci.h
>   - drm_pci_{alloc/free)() are now legacy
>   - Introduce managed DRM resourcesA
>   - Allow drivers to subclass struct drm_framebuffer
>   - Introduce struct drm_afbc_framebuffer and helpers
>   - fbdev: remove return value from generic fbdev setup
>   - Introduce simple-encoder helper
>   - vram-helpers: set fence on plane
>   - dp_mst: ACT timeout improvements
>   - dp_mst: Remove drm_dp_mst_has_audio()
>   - TTM: ttm_trace_dma_{map/unmap}() cleanups
>   - dma-buf: add flag for PCIP2P support
>   - EDID: Various improvements
>   - Encoder: cleanup semantics of possible_clones and possible_crtcs
>   - VBLANK documentation updates
>   - Writeback documentation updates
> 
> Driver Changes:
> 
>   - Convert several drivers to i2c_new_client_device()
>   - Drop explicit drm_mode_config_cleanup() calls from drivers
>   - Auto-release device structures with drmm_add_final_kfree()
>   - Init bfdev console after registering DRM device
>   - Make various .debugfs functions return 0 unconditionally; ignore errors
>   - video: Use scnprintf() to avoid buffer overflows
>   - Convert drivers to simple encoders
> 
>   - drm/amdgpu: note that we can handle peer2peer DMA-buf
>   - drm/amdgpu: add support for exporting VRAM using DMA-buf v3
>   - drm/kirin: Revert change to register connectors
>   - drm/lima: Add optional devfreq and cooling device support
>   - drm/lima: Various improvements wrt. task handling
>   - drm/panel: nt39016: Support multiple modes 

Re: [PULL] drm-misc-next

2020-01-07 Thread Daniel Vetter
On Tue, Jan 7, 2020 at 12:50 PM Maarten Lankhorst
 wrote:
>
> drm-misc-next-2020-01-07:
> drm-misc-next for v5.6:
>
> UAPI Changes:
> - Allow overriding number of bootup penguins in fbcon using 
> fbcon=logo-count:n.
>
> Cross-subsystem Changes:
> - fbdev fixes for mmp, and make it work with CONFIG_COMPILE_TEST.
> - Use devm_platform_ioremap_resource in fbdev drivers.
> - Various small fbdev fixes.
>
> Core Changes:
> - Support scanline alignment for dumb buffers.
> - Add atomic_check() hook to bridge ops, to support bus format negotiation.

This breaks depmod because of the classic dependency loop between
drm.ko and drm-kms-helpers.ko. Compile-testing alone wont catch it,
you need make modules_install 

Boris is working on a fix, but yea I guess we need to respin this pull :-/
-Daniel

> - Add gem_create_object() to vram helpers.
>
> Driver Changes:
> - Rockchip: Add support for PX30.
> - Use generic fbdev code and dumb helpers in hisilicon/hibmc.
> - Add support for Leadtek LTK500HD1829 panel, and xinpeng XPP055C272.
> - Clock fixes for atmel-hlcdc.
> - Various smaller fixes to all drivers.
> The following changes since commit f5c547efa16c0ea5abff0596e829f502be11902e:
>
>   Merge tag 'drm-misc-next-2020-01-02' of 
> git://anongit.freedesktop.org/drm/drm-misc into drm-next (2020-01-03 11:43:44 
> +1000)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2020-01-07
>
> for you to fetch changes up to 3cacb2086e41bbdf4a43e494d47d05db356992b9:
>
>   drm/mgag200: Add module parameter to pin all buffers at offset 0 
> (2020-01-07 11:53:19 +0100)
>
> 
> drm-misc-next for v5.6:
>
> UAPI Changes:
> - Allow overriding number of bootup penguins in fbcon using 
> fbcon=logo-count:n.
>
> Cross-subsystem Changes:
> - fbdev fixes for mmp, and make it work with CONFIG_COMPILE_TEST.
> - Use devm_platform_ioremap_resource in fbdev drivers.
> - Various small fbdev fixes.
>
> Core Changes:
> - Support scanline alignment for dumb buffers.
> - Add atomic_check() hook to bridge ops, to support bus format negotiation.
> - Add gem_create_object() to vram helpers.
>
> Driver Changes:
> - Rockchip: Add support for PX30.
> - Use generic fbdev code and dumb helpers in hisilicon/hibmc.
> - Add support for Leadtek LTK500HD1829 panel, and xinpeng XPP055C272.
> - Clock fixes for atmel-hlcdc.
> - Various smaller fixes to all drivers.
>
> 
> Andrew F. Davis (1):
>   omapfb/dss: remove unneeded conversions to bool
>
> Bartlomiej Zolnierkiewicz (3):
>   video: fbdev: mmp: remove duplicated MMP_DISP dependency
>   video: fbdev: mmp: add COMPILE_TEST support
>   video: fbdev: mmp: fix sparse warnings about using incorrect types
>
> Boris Brezillon (4):
>   drm/bridge: Add a drm_bridge_state object
>   drm/bridge: Patch atomic hooks to take a drm_bridge_state
>   drm/bridge: Add an ->atomic_check() hook
>   drm/bridge: Add the necessary bits to support bus format negotiation
>
> Christophe JAILLET (1):
>   pxa168fb: Fix the function used to release some memory in an error 
> handling path
>
> Claudiu Beznea (3):
>   drm: atmel-hlcdc: use double rate for pixel clock only if supported
>   drm: atmel-hlcdc: enable clock before configuring timing engine
>   Revert "drm: atmel-hlcdc: enable sys_clk during initalization."
>
> Colin Ian King (1):
>   fbdev: matrox: make array wtst_xlat static const, makes object smaller
>
> Geert Uytterhoeven (1):
>   drm/mipi_dbi: Fix off-by-one bugs in mipi_dbi_blank()
>
> Gustavo A. R. Silva (1):
>   video: fbdev: fsl-diu-fb: mark expected switch fall-throughs
>
> Heiko Stuebner (6):
>   dt-bindings: Add vendor prefix for Xinpeng Technology
>   dt-bindings: display: panel: Add binding document for Xinpeng XPP055C272
>   drm/panel: add panel driver for Xinpeng XPP055C272 panels
>   dt-bindings: Add vendor prefix for Leadtek Technology
>   dt-bindings: display: panel: Add binding document for Leadtek 
> LTK500HD1829
>   drm/panel: add panel driver for Leadtek LTK500HD1829
>
> Julia Lawall (1):
>   drm: bridge: dw-hdmi: constify copied structure
>
> Maarten Lankhorst (1):
>   Merge drm/drm-next into drm-misc-next
>
> Markus Elfring (2):
>   video: ocfb: Use devm_platform_ioremap_resource() in ocfb_probe()
>   video: pxafb: Use devm_platform_ioremap_resource() in pxafb_probe()
>
> Miquel Raynal (9):
>   dt-bindings: display: rockchip-lvds: Declare PX30 compatible
>   dt-bindings: display: rockchip-lvds: Document PX30 PHY
>   drm/rockchip: lvds: Fix indentation of a #define
>   drm/rockchip: lvds: Harmonize function names
>   drm/rockchip: lvds: Change platform data to hold helper_funcs pointer
>   drm/rockchip: lvds: Create an RK3288 specific probe function
>   drm/rockchip: lvds: improve error handling 

Re: [PULL] drm-misc-next

2019-12-17 Thread Daniel Vetter
On Tue, Dec 17, 2019 at 09:48:53AM +0100, Maarten Lankhorst wrote:
> Hey,
> 
> First pull for v5.6!
> 
> Enjoy!
> 
> ~Maarten
> 
> drm-misc-next-2019-12-16:
> drm-misc-next for v5.6:
> 
> UAPI Changes:
> - Add support for DMA-BUF HEAPS.
> 
> Cross-subsystem Changes:
> - mipi dsi definition updates, pulled into drm-intel as well.
> - Add lockdep annotations for dma_resv vs mmap_sem and fs_reclaim.
> - Remove support for dma-buf kmap/kunmap.
> - Constify fb_ops in all fbdev drivers, including drm drivers and drm-core, 
> and media as well.
> 
> Core Changes:
> - Small cleanups to ttm.
> - Fix SCDC definition.
> - Assorted cleanups to core.
> - Add todo to remove load/unload hooks, and use generic fbdev emulation.
> - Assorted documentation updates.
> - Use blocking ww lock in ttm fault handler.
> - Remove drm_fb_helper_fbdev_setup/teardown.
> - Warning fixes with W=1 for atomic.
> - Use drm_debug_enabled() instead of drm_debug flag testing in various 
> drivers.
> - Fallback to nontiled mode in fbdev emulation when not all tiles are 
> present. (Later on reverted)
> - Various kconfig indentation fixes in core and drivers.
> - Fix freeing transactions in dp-mst correctly.
> - Sean Paul is steping down as core maintainer. :-(
> - Add lockdep annotations for atomic locks vs dma-resv.
> - Prevent use-after-free for a bad job in drm_scheduler.
> - Fill out all block sizes in the P01x and P210 definitions.
> - Avoid division by zero in drm/rect, and fix bounds.
> - Add drm/rect selftests.
> - Add aspect ratio and alternate clocks for HDMI 4k modes.
> - Add todo for drm_framebuffer_funcs and fb_create cleanup.
> - Drop DRM_AUTH for prime import/export ioctls.
> - Clear DP-MST payload id tables downstream when initializating.
> - Fix for DSC throughput definition.
> - Add extra FEC definitions.
> - Fix fake offset in drm_gem_object_funs.mmap.
> - Stop using encoder->bridge in core directly
> - Handle bridge chaining slightly better.
> - Add backlight support to drm/panel, and use it in many panel drivers.
> - Increase max number of y420 modes from 128 to 256, as preparation to add 
> the new modes.
> 
> Driver Changes:
> - Small fixes all over.
> - Fix documentation in vkms.
> - Fix mmap_sem vs dma_resv in nouveau.
> - Small cleanup in komeda.
> - Add page flip support in gma500 for psb/cdv.
> - Add ddc symlink in the connector sysfs directory for many drivers.
> - Add support for analogic an6345, and fix small bugs in it.
> - Add atomic modesetting support to ast.
> - Fix radeon fault handler VMA race.
> - Switch udl to use generic shmem helpers.
> - Unconditional vblank handling for mcde.
> - Miscellaneous fixes to mcde.
> - Tweak debug output from komeda using debugfs.
> - Add gamma and color transform support to komeda for DOU-IPS.
> - Add support for sony acx424AKP panel.
> - Various small cleanups to gma500.
> - Use generic fbdev emulation in udl, and replace udl_framebuffer with 
> generic implementation.
> - Add support for Logic PD Type 28 panel.
> - Use drm_panel_* wrapper functions in exynos/tegra/msm.
> - Add devicetree bindings for generic DSI panels.
> - Don't include drm_pci.h directly in many drivers.
> - Add support for begin/end_cpu_access in udmabuf.
> - Stop using drm_get_pci_dev in gma500 and mga200.
> - Fixes to UDL damage handling, and use dma_buf_begin/end_cpu_access.
> - Add devfreq thermal support to panfrost.
> - Fix hotplug with daisy chained monitors by removing VCPI when disabling 
> topology manager.
> - meson: Add support for OSD1 plane AFBC commit.
> - Stop displaying garbage when toggling ast primary plane on/off.
> - More cleanups and fixes to UDL.
> - Add D32 suport to komeda.
> - Remove globle copy of drm_dev in gma500.
> - Add support for Boe Himax8279d MIPI-DSI LCD panel.
> - Add support for ingenic JZ4770 panel.
> - Small null pointer deference fix in ingenic.
> - Remove support for the special tfp420 driver, as there is a generic way to 
> do it.
> The following changes since commit fae7d7d5f374eadbb0b5dd31b39162e7176e9c3d:
> 
>   Revert "dma-buf: Add dma-buf heaps framework" (2019-10-30 16:41:49 -0400)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2019-12-16

Pulled, and many thanks for the careful summary.
-Daniel

> 
> for you to fetch changes up to 2156873f08c7893811f34177aa923ab1ea486591:
> 
>   drm/tilcdc: Remove obsolete bundled tilcdc tfp410 driver (2019-12-16 
> 10:45:43 +0200)
> 
> 
> drm-misc-next for v5.6:
> 
> UAPI Changes:
> - Add support for DMA-BUF HEAPS.
> 
> Cross-subsystem Changes:
> - mipi dsi definition updates, pulled into drm-intel as well.
> - Add lockdep annotations for dma_resv vs mmap_sem and fs_reclaim.
> - Remove support for dma-buf kmap/kunmap.
> - Constify fb_ops in all fbdev drivers, including drm drivers and drm-core, 
> and media as well.
> 
> Core Changes:
> - Small cleanups to ttm.
> - Fix SCDC definition.
> - 

Re: [PULL] drm-misc-next

2019-10-21 Thread Sean Paul
On Mon, Oct 21, 2019 at 4:11 AM Tomi Valkeinen  wrote:
>
> Hi,
>
> On 18/10/2019 23:11, Sean Paul wrote:
> > On Fri, Oct 18, 2019 at 9:46 AM Tomi Valkeinen  
> > wrote:
> >>
> >> Hi Sean,
> >>
> >> On 17/10/2019 22:26, Sean Paul wrote:
> >>
> >>> concern for those. The omap OMAP_BO_MEM_* changes though I don't think 
> >>> have
> >>> really reached non-TI eyes. There's no link in the commit message to a 
> >>> UAPI
> >>> implementation and the only reference I could find is libkmsxx which can 
> >>> set
> >>> them through the python bindings. Since this is TI-specific gunk in 
> >>> TI-specific
> >>> headers I'm inclined to let it pass, but I would have liked to have this
> >>> conversation upfront. I figured I'd call this out so you have final say.
> >>
> >> There was some discussion about that a few years back when I initially
> >> sent the patches, but now that I look, the discussion died before really
> >> even starting.
> >>
> >> This is what I said about userspace implementation:
> >>
> >>> Yes, unfortunately that is not going to happen. I don't see how this
> >>> could be used in a generic system like Weston or X. It's meant for very
> >>> specific use cases, where you know exactly the requirements of your
> >>> application and the capabilities of the whole system, and optimize based
> >>> on that.
> >
> > Thanks for the context, Tomi.
> >
> > Indeed it looks like the discussion died, but Laurent still brought up
> > the u/s requirement and the patch was effectively dead until Daniel or
> > Dave weighed in. I'd expect at least some outreach before pushing the
> > patch directly 2+ years later. Has anything changed since then?
>
> There were new review rounds for the series this summer & autumn, but
> no, nothing else. I haven't specifically pinged anyone about the UAPI
> changes.
>
> This series introduces three new flags to an already existing UAPI, and,
> for whatever reason, this didn't register to me as a new UAPI, even if
> Laurent asked about it some years back.
>
> So, my mistake.
>
> The flags are added in a single patch, so I can easily push a revert for
> that if this patch is not acceptable. The rest of the series is cleanup.
>

I'll wait for Dave or Daniel to weigh in on whether they want to take
this, otherwise I'll revert before sending the next pull and we can
have this conversation on the review.

> >> I know this feature is used by customers, but I don't have access to
> >> their applications.
> >
> > Unfortunately, and as you know, that is insufficient/irrelevant for
> > introducing new UAPI. So the question is if the libkmsxx bindings
> > constitute opensource userspace, it's really thin IMO.
>
> Ok. Well, I know and understand the general rule here. But perhaps I
> haven't taken it as strictly as needed.
>
> I have to say I don't quite understand why this rule would be always
> strictly held, though.
>

It's strictly held because once you start accepting the
harmless/isolated features every driver has, you end up with
untestable bloat sprinkled everywhere.

> These flags, for example, what should we do with them?
> - They provide a proven, real use-case benefit.
> - They are specific to SoCs with OMAP DSS and DMM IPs.
> - They are relatively simple.
> - All the details, including the details about the HW, are public.
> - Using them makes sense only in cases where you are tuning your system
> to your application, and you must know the resource needs of all the
> apps in your system. So they cannot really be used in any generic setup,
> or at least I have no idea how.
>
> Does the history and experience say that such specific case as above
> cases don't really exist, and we can always have a generic UAPI (or, in
> worst case, a device specific UAPI) which can be used from X/Weston/or-such?
>

We don't need generic userspace to be able to make use of it, but at
least some oss project should find it useful. Otherwise why are we
maintaining code that no one in the open source community cares about?
How do we test it when the closed source implementations have been
abandoned?

> Or do things like above exist, but they need to carried in vendors' kernels?

That's really the problem. _Everybody_ has features they would
describe as above, so where do we draw the line?

Sean

>
>   Tomi
>
> --
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
> ___
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-10-21 Thread Tomi Valkeinen

Hi,

On 18/10/2019 23:11, Sean Paul wrote:

On Fri, Oct 18, 2019 at 9:46 AM Tomi Valkeinen  wrote:


Hi Sean,

On 17/10/2019 22:26, Sean Paul wrote:


concern for those. The omap OMAP_BO_MEM_* changes though I don't think have
really reached non-TI eyes. There's no link in the commit message to a UAPI
implementation and the only reference I could find is libkmsxx which can set
them through the python bindings. Since this is TI-specific gunk in TI-specific
headers I'm inclined to let it pass, but I would have liked to have this
conversation upfront. I figured I'd call this out so you have final say.


There was some discussion about that a few years back when I initially
sent the patches, but now that I look, the discussion died before really
even starting.

This is what I said about userspace implementation:


Yes, unfortunately that is not going to happen. I don't see how this
could be used in a generic system like Weston or X. It's meant for very
specific use cases, where you know exactly the requirements of your
application and the capabilities of the whole system, and optimize based
on that.


Thanks for the context, Tomi.

Indeed it looks like the discussion died, but Laurent still brought up
the u/s requirement and the patch was effectively dead until Daniel or
Dave weighed in. I'd expect at least some outreach before pushing the
patch directly 2+ years later. Has anything changed since then?


There were new review rounds for the series this summer & autumn, but 
no, nothing else. I haven't specifically pinged anyone about the UAPI 
changes.


This series introduces three new flags to an already existing UAPI, and, 
for whatever reason, this didn't register to me as a new UAPI, even if 
Laurent asked about it some years back.


So, my mistake.

The flags are added in a single patch, so I can easily push a revert for 
that if this patch is not acceptable. The rest of the series is cleanup.



I know this feature is used by customers, but I don't have access to
their applications.


Unfortunately, and as you know, that is insufficient/irrelevant for
introducing new UAPI. So the question is if the libkmsxx bindings
constitute opensource userspace, it's really thin IMO.


Ok. Well, I know and understand the general rule here. But perhaps I 
haven't taken it as strictly as needed.


I have to say I don't quite understand why this rule would be always 
strictly held, though.


These flags, for example, what should we do with them?
- They provide a proven, real use-case benefit.
- They are specific to SoCs with OMAP DSS and DMM IPs.
- They are relatively simple.
- All the details, including the details about the HW, are public.
- Using them makes sense only in cases where you are tuning your system 
to your application, and you must know the resource needs of all the 
apps in your system. So they cannot really be used in any generic setup, 
or at least I have no idea how.


Does the history and experience say that such specific case as above 
cases don't really exist, and we can always have a generic UAPI (or, in 
worst case, a device specific UAPI) which can be used from X/Weston/or-such?


Or do things like above exist, but they need to carried in vendors' kernels?

 Tomi

--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-10-18 Thread Sean Paul
On Fri, Oct 18, 2019 at 9:46 AM Tomi Valkeinen  wrote:
>
> Hi Sean,
>
> On 17/10/2019 22:26, Sean Paul wrote:
>
> > concern for those. The omap OMAP_BO_MEM_* changes though I don't think have
> > really reached non-TI eyes. There's no link in the commit message to a UAPI
> > implementation and the only reference I could find is libkmsxx which can set
> > them through the python bindings. Since this is TI-specific gunk in 
> > TI-specific
> > headers I'm inclined to let it pass, but I would have liked to have this
> > conversation upfront. I figured I'd call this out so you have final say.
>
> There was some discussion about that a few years back when I initially
> sent the patches, but now that I look, the discussion died before really
> even starting.
>
> This is what I said about userspace implementation:
>
> > Yes, unfortunately that is not going to happen. I don't see how this
> > could be used in a generic system like Weston or X. It's meant for very
> > specific use cases, where you know exactly the requirements of your
> > application and the capabilities of the whole system, and optimize based
> > on that.

Thanks for the context, Tomi.

Indeed it looks like the discussion died, but Laurent still brought up
the u/s requirement and the patch was effectively dead until Daniel or
Dave weighed in. I'd expect at least some outreach before pushing the
patch directly 2+ years later. Has anything changed since then?


> I know this feature is used by customers, but I don't have access to
> their applications.

Unfortunately, and as you know, that is insufficient/irrelevant for
introducing new UAPI. So the question is if the libkmsxx bindings
constitute opensource userspace, it's really thin IMO.

Sean


>
>   Tomi
>
> --
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-10-18 Thread Tomi Valkeinen

Hi Sean,

On 17/10/2019 22:26, Sean Paul wrote:


concern for those. The omap OMAP_BO_MEM_* changes though I don't think have
really reached non-TI eyes. There's no link in the commit message to a UAPI
implementation and the only reference I could find is libkmsxx which can set
them through the python bindings. Since this is TI-specific gunk in TI-specific
headers I'm inclined to let it pass, but I would have liked to have this
conversation upfront. I figured I'd call this out so you have final say.


There was some discussion about that a few years back when I initially 
sent the patches, but now that I look, the discussion died before really 
even starting.


This is what I said about userspace implementation:


Yes, unfortunately that is not going to happen. I don't see how this
could be used in a generic system like Weston or X. It's meant for very
specific use cases, where you know exactly the requirements of your
application and the capabilities of the whole system, and optimize based
on that.
I know this feature is used by customers, but I don't have access to 
their applications.


 Tomi

--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-19 Thread Maxime Ripard
Hi Chris,

On Fri, Aug 16, 2019 at 12:47:06PM +0100, Chris Wilson wrote:
> Quoting Maxime Ripard (2019-08-16 12:32:01)
> > Hi Daniel, Dave,
> >
> > Here's this week drm-misc-next PR.
> >
> > Maxime
> >
> > drm-misc-next-2019-08-16:
> > drm-misc-next for 5.4:
> >
> > UAPI Changes:
> >
> > Cross-subsystem Changes:
> >
> > Core Changes:
> >   - dma-buf: add reservation_object_fences helper, relax
> >  reservation_object_add_shared_fence, remove
> >  reservation_object seq number
>
> I just undid these. Probably better to respin without the headline
> feature being immediately reverted :)

Thanks for telling us :)

I've sent a new PR with the revert

Maxime

--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


signature.asc
Description: PGP signature
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-16 Thread Chris Wilson
Quoting Maxime Ripard (2019-08-16 12:32:01)
> Hi Daniel, Dave,
> 
> Here's this week drm-misc-next PR.
> 
> Maxime
> 
> drm-misc-next-2019-08-16:
> drm-misc-next for 5.4:
> 
> UAPI Changes:
> 
> Cross-subsystem Changes:
> 
> Core Changes:
>   - dma-buf: add reservation_object_fences helper, relax
>  reservation_object_add_shared_fence, remove
>  reservation_object seq number

I just undid these. Probably better to respin without the headline
feature being immediately reverted :)
-Chris
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-08 Thread Maxime Ripard
Hi,

On Wed, Aug 07, 2019 at 02:30:25PM +0200, Daniel Vetter wrote:
> On Wed, Aug 7, 2019 at 2:02 PM Maxime Ripard  
> wrote:
> > On Tue, Aug 06, 2019 at 06:11:32PM +0200, Daniel Vetter wrote:
> > > On Tue, Aug 06, 2019 at 06:01:46PM +0200, Maxime Ripard wrote:
> > > > On Tue, Aug 06, 2019 at 10:33:53AM +1000, Dave Airlie wrote:
> > > > > On Sat, 3 Aug 2019 at 20:47, Maxime Ripard 
> > > > >  wrote:
> > > > > >
> > > > > > Hi Daniel, Dave,
> > > > > >
> > > > > > Here is the first (and pretty late) drm-misc-next PR.
> > > > > >
> > > > > > It's pretty big due to the lateness, but there's nothing really 
> > > > > > major
> > > > > > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > > > > > new helpers being introduced.
> > > > >
> > > > > dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> > > > > to drm_gem_map_offset()""): mandatory review missing.
> > > > > dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> > > > > mandatory review missing.
> > > > > dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> > > > > mandatory review missing.
> > > > > dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> > > > > mandatory review missing.
> > > > > dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> > > > > mandatory review missing.
> > > > >
> > > > > Pretty sure review in drm-misc-next is a rule. I don't even see acks
> > > > > on most of these.
> > > >
> > > > Ugh, sorry for that. I guess I'm still pretty new to the
> > > > maintainer-side of dim, which commands did you use to check that?
> > >
> > > dim apply-pull does this. If all committers use the tooling as they should
> > > they shouldn't be able to push patches which violate anything here, that's
> > > why dim request-pull doesn't reject.
> >
> > Yeah, sure, I meant to ask if there was anyway to check this before
> > sending the PR on our end.
>
> I think we'd need to create new command. Or maybe we should integrate
> it as part of the pull request generation, as an information/warning
> that there might be problems you need to explain. Want to write a dim
> patch?

I just sent something that should catch that, but considering my
dim-fu, you probably want to review it :)

Maxime

--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


signature.asc
Description: PGP signature
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-07 Thread Daniel Vetter
On Wed, Aug 7, 2019 at 2:02 PM Maxime Ripard  wrote:
> On Tue, Aug 06, 2019 at 06:11:32PM +0200, Daniel Vetter wrote:
> > On Tue, Aug 06, 2019 at 06:01:46PM +0200, Maxime Ripard wrote:
> > > On Tue, Aug 06, 2019 at 10:33:53AM +1000, Dave Airlie wrote:
> > > > On Sat, 3 Aug 2019 at 20:47, Maxime Ripard  
> > > > wrote:
> > > > >
> > > > > Hi Daniel, Dave,
> > > > >
> > > > > Here is the first (and pretty late) drm-misc-next PR.
> > > > >
> > > > > It's pretty big due to the lateness, but there's nothing really major
> > > > > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > > > > new helpers being introduced.
> > > >
> > > > dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> > > > to drm_gem_map_offset()""): mandatory review missing.
> > > > dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> > > > mandatory review missing.
> > > > dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> > > > mandatory review missing.
> > > > dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> > > > mandatory review missing.
> > > > dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> > > > mandatory review missing.
> > > >
> > > > Pretty sure review in drm-misc-next is a rule. I don't even see acks
> > > > on most of these.
> > >
> > > Ugh, sorry for that. I guess I'm still pretty new to the
> > > maintainer-side of dim, which commands did you use to check that?
> >
> > dim apply-pull does this. If all committers use the tooling as they should
> > they shouldn't be able to push patches which violate anything here, that's
> > why dim request-pull doesn't reject.
>
> Yeah, sure, I meant to ask if there was anyway to check this before
> sending the PR on our end.

I think we'd need to create new command. Or maybe we should integrate
it as part of the pull request generation, as an information/warning
that there might be problems you need to explain. Want to write a dim
patch?
-Daniel

>
> > We're now working on patqches to make sure you really have to use
> > dim for managing drm-misc and applying patches.
>
> Great, thanks
>
> Maxime
>
> --
> Maxime Ripard, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-07 Thread Maxime Ripard
On Tue, Aug 06, 2019 at 06:11:32PM +0200, Daniel Vetter wrote:
> On Tue, Aug 06, 2019 at 06:01:46PM +0200, Maxime Ripard wrote:
> > On Tue, Aug 06, 2019 at 10:33:53AM +1000, Dave Airlie wrote:
> > > On Sat, 3 Aug 2019 at 20:47, Maxime Ripard  
> > > wrote:
> > > >
> > > > Hi Daniel, Dave,
> > > >
> > > > Here is the first (and pretty late) drm-misc-next PR.
> > > >
> > > > It's pretty big due to the lateness, but there's nothing really major
> > > > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > > > new helpers being introduced.
> > >
> > > dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> > > to drm_gem_map_offset()""): mandatory review missing.
> > > dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> > > mandatory review missing.
> > > dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> > > mandatory review missing.
> > > dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> > > mandatory review missing.
> > > dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> > > mandatory review missing.
> > >
> > > Pretty sure review in drm-misc-next is a rule. I don't even see acks
> > > on most of these.
> >
> > Ugh, sorry for that. I guess I'm still pretty new to the
> > maintainer-side of dim, which commands did you use to check that?
>
> dim apply-pull does this. If all committers use the tooling as they should
> they shouldn't be able to push patches which violate anything here, that's
> why dim request-pull doesn't reject.

Yeah, sure, I meant to ask if there was anyway to check this before
sending the PR on our end.

> We're now working on patqches to make sure you really have to use
> dim for managing drm-misc and applying patches.

Great, thanks

Maxime

--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Daniel Vetter
On Tue, Aug 06, 2019 at 06:01:46PM +0200, Maxime Ripard wrote:
> On Tue, Aug 06, 2019 at 10:33:53AM +1000, Dave Airlie wrote:
> > On Sat, 3 Aug 2019 at 20:47, Maxime Ripard  
> > wrote:
> > >
> > > Hi Daniel, Dave,
> > >
> > > Here is the first (and pretty late) drm-misc-next PR.
> > >
> > > It's pretty big due to the lateness, but there's nothing really major
> > > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > > new helpers being introduced.
> >
> > dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> > to drm_gem_map_offset()""): mandatory review missing.
> > dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> > mandatory review missing.
> > dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> > mandatory review missing.
> > dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> > mandatory review missing.
> > dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> > mandatory review missing.
> >
> > Pretty sure review in drm-misc-next is a rule. I don't even see acks
> > on most of these.
> 
> Ugh, sorry for that. I guess I'm still pretty new to the
> maintainer-side of dim, which commands did you use to check that?

dim apply-pull does this. If all committers use the tooling as they should
they shouldn't be able to push patches which violate anything here, that's
why dim request-pull doesn't reject. We're now working on patches to make
sure you really have to use dim for managing drm-misc and applying
patches.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Maxime Ripard
On Tue, Aug 06, 2019 at 10:33:53AM +1000, Dave Airlie wrote:
> On Sat, 3 Aug 2019 at 20:47, Maxime Ripard  wrote:
> >
> > Hi Daniel, Dave,
> >
> > Here is the first (and pretty late) drm-misc-next PR.
> >
> > It's pretty big due to the lateness, but there's nothing really major
> > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > new helpers being introduced.
>
> dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> to drm_gem_map_offset()""): mandatory review missing.
> dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> mandatory review missing.
> dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> mandatory review missing.
> dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> mandatory review missing.
> dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> mandatory review missing.
>
> Pretty sure review in drm-misc-next is a rule. I don't even see acks
> on most of these.

Ugh, sorry for that. I guess I'm still pretty new to the
maintainer-side of dim, which commands did you use to check that?

Thanks!
Maxime

--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Daniel Vetter
On Tue, Aug 6, 2019 at 4:25 PM Rob Herring  wrote:
>
> On Tue, Aug 6, 2019 at 1:34 AM Daniel Vetter  wrote:
> >
> > On Tue, Aug 6, 2019 at 2:34 AM Dave Airlie  wrote:
> > >
> > > On Sat, 3 Aug 2019 at 20:47, Maxime Ripard  
> > > wrote:
> > > >
> > > > Hi Daniel, Dave,
> > > >
> > > > Here is the first (and pretty late) drm-misc-next PR.
> > > >
> > > > It's pretty big due to the lateness, but there's nothing really major
> > > > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > > > new helpers being introduced.
> > > >
> > >
> > > dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> > > to drm_gem_map_offset()""): mandatory review missing.
> > > dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> > > mandatory review missing.
> > > dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> > > mandatory review missing.
> > > dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> > > mandatory review missing.
> > > dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> > > mandatory review missing.
> > >
> > > Pretty sure review in drm-misc-next is a rule. I don't even see acks
> > > on most of these.
> >
> > Yes. I guess for reverts it's not cool, but also not the worst. Still
> > better to get someone to ack, heck I can pull that off for emergency
> > reverts with a few pings on irc, and the 2 reverts landed much later.
> > But for normal patches it's definitely not ok at all. Also only
> > possible if people bypass the tooling, or override the tooling with
> > the -f flag to force a push.
> >
> > Rob, Emil, what's up here?
>
> I committed the changes, they turned out to clearly break things and
> not be fixable in any way. I said I was going to revert them[1] in
> reply to the original, got no reply, and so I reverted them. Seemed
> sufficient to me, but next time I'll keep the tool happy.

Generally submitting the full revert and then going ack-shopping on
irc you can land reverts within a few hours tops. Seeing a patch with
the dreaded "Revert" subject gets people going a lot more than a reply
in some old thread somewhere, which is easily overlooked.
-Daniel

>
> Rob
>
> [1] https://lists.freedesktop.org/archives/dri-devel/2019-July/225092.html



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Rob Herring
On Tue, Aug 6, 2019 at 1:34 AM Daniel Vetter  wrote:
>
> On Tue, Aug 6, 2019 at 2:34 AM Dave Airlie  wrote:
> >
> > On Sat, 3 Aug 2019 at 20:47, Maxime Ripard  
> > wrote:
> > >
> > > Hi Daniel, Dave,
> > >
> > > Here is the first (and pretty late) drm-misc-next PR.
> > >
> > > It's pretty big due to the lateness, but there's nothing really major
> > > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > > new helpers being introduced.
> > >
> >
> > dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> > to drm_gem_map_offset()""): mandatory review missing.
> > dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> > mandatory review missing.
> > dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> > mandatory review missing.
> > dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> > mandatory review missing.
> > dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> > mandatory review missing.
> >
> > Pretty sure review in drm-misc-next is a rule. I don't even see acks
> > on most of these.
>
> Yes. I guess for reverts it's not cool, but also not the worst. Still
> better to get someone to ack, heck I can pull that off for emergency
> reverts with a few pings on irc, and the 2 reverts landed much later.
> But for normal patches it's definitely not ok at all. Also only
> possible if people bypass the tooling, or override the tooling with
> the -f flag to force a push.
>
> Rob, Emil, what's up here?

I committed the changes, they turned out to clearly break things and
not be fixable in any way. I said I was going to revert them[1] in
reply to the original, got no reply, and so I reverted them. Seemed
sufficient to me, but next time I'll keep the tool happy.

Rob

[1] https://lists.freedesktop.org/archives/dri-devel/2019-July/225092.html
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Jani Nikula
On Tue, 06 Aug 2019, Emil Velikov  wrote:
> On Tue, 6 Aug 2019 at 11:14, Daniel Stone  wrote:
>
>> The idea I had a few weeks ago was to have dim use 'git push
>> --push-option fdo.pushedWithDim=this-was-pushed-with-dim-and-not-manually',
>> then have the hooks on the server side check for that option and
>> refuse any direct pushes. (Or at least, if people are pushing
>> directly, they have to _really_ try to be doing it, and can't do it by
>> accident.)
>>
> Let me try and write a DIM patch for that.

Ooops, I was wondering how this would all work out, and ended up writing
the patch [1].

BR,
Jani.


[1] http://marc.info/?i=20190806104630.14675-1-jani.nik...@intel.com


-- 
Jani Nikula, Intel Open Source Graphics Center
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Emil Velikov
On Tue, 6 Aug 2019 at 11:14, Daniel Stone  wrote:

> The idea I had a few weeks ago was to have dim use 'git push
> --push-option fdo.pushedWithDim=this-was-pushed-with-dim-and-not-manually',
> then have the hooks on the server side check for that option and
> refuse any direct pushes. (Or at least, if people are pushing
> directly, they have to _really_ try to be doing it, and can't do it by
> accident.)
>
Let me try and write a DIM patch for that.

-Emil
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Daniel Stone
Hi,

On Tue, 6 Aug 2019 at 10:58, Daniel Vetter  wrote:
> On Tue, Aug 6, 2019 at 11:55 AM Emil Velikov  wrote:
> > On Tue, 6 Aug 2019 at 10:49, Daniel Vetter  wrote:
> > > The thing is, dim push shouldn't allow you to do that. And the patches
> > > have clearly been applied with dim apply (or at least you added the
> > > Link), unlike Rob who seems to just have pushed the revert.
> > >
> > Thanks, did not know about dim push. Will make sure I use it.
>
> So the intro doc isn't good enough, and we need to enforce it. I think
> Daniel's idea was to have a pre-merge hook which checks for a git
> variable using --push-option. Can you pls look into this? I guess we'd
> need the dim patch, and example premerge hook to be installed
> server-side. Should have a nice error message too ofc.

Yeah, the docs are already quite clear that you cannot push to the DRM
trees with normal git, and that you have to use dim. Not only does it
check and enforce all the rules in the documentation, but it also
rebuilds drm-tip and keeps other trees in sync, which isn't done with
a regular git push.

The idea I had a few weeks ago was to have dim use 'git push
--push-option fdo.pushedWithDim=this-was-pushed-with-dim-and-not-manually',
then have the hooks on the server side check for that option and
refuse any direct pushes. (Or at least, if people are pushing
directly, they have to _really_ try to be doing it, and can't do it by
accident.)

If someone types up the dim patch to do that and gets it committed,
after a couple of days' grace period for everyone to update I can roll
out the server-side hooks which refuse non-dim pushes.

Cheers,
Daniel
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Daniel Vetter
On Tue, Aug 6, 2019 at 11:55 AM Emil Velikov  wrote:
>
> On Tue, 6 Aug 2019 at 10:49, Daniel Vetter  wrote:
> >
> > On Tue, Aug 6, 2019 at 11:40 AM Emil Velikov  
> > wrote:
> > > On Tue, 6 Aug 2019 at 08:34, Daniel Vetter  wrote:
> > > >
> > > > On Tue, Aug 6, 2019 at 2:34 AM Dave Airlie  wrote:
> > > > >
> > > > > On Sat, 3 Aug 2019 at 20:47, Maxime Ripard 
> > > > >  wrote:
> > > > > >
> > > > > > Hi Daniel, Dave,
> > > > > >
> > > > > > Here is the first (and pretty late) drm-misc-next PR.
> > > > > >
> > > > > > It's pretty big due to the lateness, but there's nothing really 
> > > > > > major
> > > > > > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > > > > > new helpers being introduced.
> > > > > >
> > > > >
> > > > > dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> > > > > to drm_gem_map_offset()""): mandatory review missing.
> > > > > dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> > > > > mandatory review missing.
> > > > > dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> > > > > mandatory review missing.
> > > > > dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> > > > > mandatory review missing.
> > > > > dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> > > > > mandatory review missing.
> > > > >
> > > > > Pretty sure review in drm-misc-next is a rule. I don't even see acks
> > > > > on most of these.
> > > >
> > > > Yes. I guess for reverts it's not cool, but also not the worst. Still
> > > > better to get someone to ack, heck I can pull that off for emergency
> > > > reverts with a few pings on irc, and the 2 reverts landed much later.
> > > > But for normal patches it's definitely not ok at all. Also only
> > > > possible if people bypass the tooling, or override the tooling with
> > > > the -f flag to force a push.
> > > >
> > > > Rob, Emil, what's up here?
> > > >
> > > I've got was an "Thanks" [1] from Ben on the nouveau patch - so I merged 
> > > it.
> > > The msm and vgem ones are my bad - must have missed those one
> > > inbetween the other patches.
> >
> > The thing is, dim push shouldn't allow you to do that. And the patches
> > have clearly been applied with dim apply (or at least you added the
> > Link), unlike Rob who seems to just have pushed the revert.
> >
> Thanks, did not know about dim push. Will make sure I use it.

So the intro doc isn't good enough, and we need to enforce it. I think
Daniel's idea was to have a pre-merge hook which checks for a git
variable using --push-option. Can you pls look into this? I guess we'd
need the dim patch, and example premerge hook to be installed
server-side. Should have a nice error message too ofc.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Daniel Vetter
On Tue, Aug 6, 2019 at 11:49 AM Daniel Vetter  wrote:
>
> On Tue, Aug 6, 2019 at 11:40 AM Emil Velikov  wrote:
> > On Tue, 6 Aug 2019 at 08:34, Daniel Vetter  wrote:
> > >
> > > On Tue, Aug 6, 2019 at 2:34 AM Dave Airlie  wrote:
> > > >
> > > > On Sat, 3 Aug 2019 at 20:47, Maxime Ripard  
> > > > wrote:
> > > > >
> > > > > Hi Daniel, Dave,
> > > > >
> > > > > Here is the first (and pretty late) drm-misc-next PR.
> > > > >
> > > > > It's pretty big due to the lateness, but there's nothing really major
> > > > > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > > > > new helpers being introduced.
> > > > >
> > > >
> > > > dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> > > > to drm_gem_map_offset()""): mandatory review missing.
> > > > dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> > > > mandatory review missing.
> > > > dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> > > > mandatory review missing.
> > > > dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> > > > mandatory review missing.
> > > > dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> > > > mandatory review missing.
> > > >
> > > > Pretty sure review in drm-misc-next is a rule. I don't even see acks
> > > > on most of these.
> > >
> > > Yes. I guess for reverts it's not cool, but also not the worst. Still
> > > better to get someone to ack, heck I can pull that off for emergency
> > > reverts with a few pings on irc, and the 2 reverts landed much later.
> > > But for normal patches it's definitely not ok at all. Also only
> > > possible if people bypass the tooling, or override the tooling with
> > > the -f flag to force a push.
> > >
> > > Rob, Emil, what's up here?
> > >
> > I've got was an "Thanks" [1] from Ben on the nouveau patch - so I merged it.
> > The msm and vgem ones are my bad - must have missed those one
> > inbetween the other patches.
>
> The thing is, dim push shouldn't allow you to do that. And the patches
> have clearly been applied with dim apply (or at least you added the
> Link), unlike Rob who seems to just have pushed the revert.
>
> If you used git push directly, then I guess you just volunteered to
> implement Daniel Stone's idea to enforce dim tooling. Adding Daniel,
> since I guess that was just an irc chat.

Helps if I actually add Daniel.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Emil Velikov
On Tue, 6 Aug 2019 at 10:49, Daniel Vetter  wrote:
>
> On Tue, Aug 6, 2019 at 11:40 AM Emil Velikov  wrote:
> > On Tue, 6 Aug 2019 at 08:34, Daniel Vetter  wrote:
> > >
> > > On Tue, Aug 6, 2019 at 2:34 AM Dave Airlie  wrote:
> > > >
> > > > On Sat, 3 Aug 2019 at 20:47, Maxime Ripard  
> > > > wrote:
> > > > >
> > > > > Hi Daniel, Dave,
> > > > >
> > > > > Here is the first (and pretty late) drm-misc-next PR.
> > > > >
> > > > > It's pretty big due to the lateness, but there's nothing really major
> > > > > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > > > > new helpers being introduced.
> > > > >
> > > >
> > > > dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> > > > to drm_gem_map_offset()""): mandatory review missing.
> > > > dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> > > > mandatory review missing.
> > > > dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> > > > mandatory review missing.
> > > > dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> > > > mandatory review missing.
> > > > dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> > > > mandatory review missing.
> > > >
> > > > Pretty sure review in drm-misc-next is a rule. I don't even see acks
> > > > on most of these.
> > >
> > > Yes. I guess for reverts it's not cool, but also not the worst. Still
> > > better to get someone to ack, heck I can pull that off for emergency
> > > reverts with a few pings on irc, and the 2 reverts landed much later.
> > > But for normal patches it's definitely not ok at all. Also only
> > > possible if people bypass the tooling, or override the tooling with
> > > the -f flag to force a push.
> > >
> > > Rob, Emil, what's up here?
> > >
> > I've got was an "Thanks" [1] from Ben on the nouveau patch - so I merged it.
> > The msm and vgem ones are my bad - must have missed those one
> > inbetween the other patches.
>
> The thing is, dim push shouldn't allow you to do that. And the patches
> have clearly been applied with dim apply (or at least you added the
> Link), unlike Rob who seems to just have pushed the revert.
>
Thanks, did not know about dim push. Will make sure I use it.

-Emil
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Daniel Vetter
On Tue, Aug 6, 2019 at 11:40 AM Emil Velikov  wrote:
> On Tue, 6 Aug 2019 at 08:34, Daniel Vetter  wrote:
> >
> > On Tue, Aug 6, 2019 at 2:34 AM Dave Airlie  wrote:
> > >
> > > On Sat, 3 Aug 2019 at 20:47, Maxime Ripard  
> > > wrote:
> > > >
> > > > Hi Daniel, Dave,
> > > >
> > > > Here is the first (and pretty late) drm-misc-next PR.
> > > >
> > > > It's pretty big due to the lateness, but there's nothing really major
> > > > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > > > new helpers being introduced.
> > > >
> > >
> > > dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> > > to drm_gem_map_offset()""): mandatory review missing.
> > > dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> > > mandatory review missing.
> > > dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> > > mandatory review missing.
> > > dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> > > mandatory review missing.
> > > dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> > > mandatory review missing.
> > >
> > > Pretty sure review in drm-misc-next is a rule. I don't even see acks
> > > on most of these.
> >
> > Yes. I guess for reverts it's not cool, but also not the worst. Still
> > better to get someone to ack, heck I can pull that off for emergency
> > reverts with a few pings on irc, and the 2 reverts landed much later.
> > But for normal patches it's definitely not ok at all. Also only
> > possible if people bypass the tooling, or override the tooling with
> > the -f flag to force a push.
> >
> > Rob, Emil, what's up here?
> >
> I've got was an "Thanks" [1] from Ben on the nouveau patch - so I merged it.
> The msm and vgem ones are my bad - must have missed those one
> inbetween the other patches.

The thing is, dim push shouldn't allow you to do that. And the patches
have clearly been applied with dim apply (or at least you added the
Link), unlike Rob who seems to just have pushed the revert.

If you used git push directly, then I guess you just volunteered to
implement Daniel Stone's idea to enforce dim tooling. Adding Daniel,
since I guess that was just an irc chat.
-Daniel

> Will double-check and follow-up on all of those.
>
> -Emil
> [1] https://lists.freedesktop.org/archives/dri-devel/2019-May/218823.html


--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Emil Velikov
On Tue, 6 Aug 2019 at 08:34, Daniel Vetter  wrote:
>
> On Tue, Aug 6, 2019 at 2:34 AM Dave Airlie  wrote:
> >
> > On Sat, 3 Aug 2019 at 20:47, Maxime Ripard  
> > wrote:
> > >
> > > Hi Daniel, Dave,
> > >
> > > Here is the first (and pretty late) drm-misc-next PR.
> > >
> > > It's pretty big due to the lateness, but there's nothing really major
> > > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > > new helpers being introduced.
> > >
> >
> > dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> > to drm_gem_map_offset()""): mandatory review missing.
> > dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> > mandatory review missing.
> > dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> > mandatory review missing.
> > dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> > mandatory review missing.
> > dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> > mandatory review missing.
> >
> > Pretty sure review in drm-misc-next is a rule. I don't even see acks
> > on most of these.
>
> Yes. I guess for reverts it's not cool, but also not the worst. Still
> better to get someone to ack, heck I can pull that off for emergency
> reverts with a few pings on irc, and the 2 reverts landed much later.
> But for normal patches it's definitely not ok at all. Also only
> possible if people bypass the tooling, or override the tooling with
> the -f flag to force a push.
>
> Rob, Emil, what's up here?
>
I've got was an "Thanks" [1] from Ben on the nouveau patch - so I merged it.
The msm and vgem ones are my bad - must have missed those one
inbetween the other patches.

Will double-check and follow-up on all of those.

-Emil
[1] https://lists.freedesktop.org/archives/dri-devel/2019-May/218823.html
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-06 Thread Daniel Vetter
On Tue, Aug 6, 2019 at 2:34 AM Dave Airlie  wrote:
>
> On Sat, 3 Aug 2019 at 20:47, Maxime Ripard  wrote:
> >
> > Hi Daniel, Dave,
> >
> > Here is the first (and pretty late) drm-misc-next PR.
> >
> > It's pretty big due to the lateness, but there's nothing really major
> > showing up. It's pretty much the usual bunch of reworks, fixes, and
> > new helpers being introduced.
> >
>
> dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
> to drm_gem_map_offset()""): mandatory review missing.
> dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
> mandatory review missing.
> dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
> mandatory review missing.
> dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
> mandatory review missing.
> dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
> mandatory review missing.
>
> Pretty sure review in drm-misc-next is a rule. I don't even see acks
> on most of these.

Yes. I guess for reverts it's not cool, but also not the worst. Still
better to get someone to ack, heck I can pull that off for emergency
reverts with a few pings on irc, and the 2 reverts landed much later.
But for normal patches it's definitely not ok at all. Also only
possible if people bypass the tooling, or override the tooling with
the -f flag to force a push.

Rob, Emil, what's up here?

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-08-05 Thread Dave Airlie
On Sat, 3 Aug 2019 at 20:47, Maxime Ripard  wrote:
>
> Hi Daniel, Dave,
>
> Here is the first (and pretty late) drm-misc-next PR.
>
> It's pretty big due to the lateness, but there's nothing really major
> showing up. It's pretty much the usual bunch of reworks, fixes, and
> new helpers being introduced.
>

dim: 415d2e9e0757 ("Revert "drm/gem: Rename drm_gem_dumb_map_offset()
to drm_gem_map_offset()""): mandatory review missing.
dim: be855382bacb ("Revert "drm/panfrost: Use drm_gem_map_offset()""):
mandatory review missing.
dim: e4eee93d2577 ("drm/vgem: drop DRM_AUTH usage from the driver"):
mandatory review missing.
dim: 88209d2c5035 ("drm/msm: drop DRM_AUTH usage from the driver"):
mandatory review missing.
dim: ccdae4257569 ("drm/nouveau: remove open-coded drm_invalid_op()"):
mandatory review missing.

Pretty sure review in drm-misc-next is a rule. I don't even see acks
on most of these.

Dave.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PULL] drm-misc-next

2019-06-14 Thread Daniel Vetter
On Fri, Jun 14, 2019 at 10:57:34AM +0200, Maarten Lankhorst wrote:
> Hi Dave and Daniel,
> 
> Next pull request, with more fixes and features!
> 
> drm-misc-next-2019-06-14:
> drm-misc-next for v5.3:
> 
> UAPI Changes:
> 
> Cross-subsystem Changes:
> - Add code to signal all dma-fences when freed with pending signals.
> - Annotate reservation object access in CONFIG_DEBUG_MUTEXES
> 
> Core Changes:
> - Assorted documentation fixes.
> - Use irqsave/restore spinlock to add crc entry.
> - Move code around to drm_client, for internal modeset clients.
> - Make drm_crtc.h and drm_debugfs.h self-contained.
> - Remove drm_fb_helper_connector.
> - Add bootsplash to todo.
> - Fix lock ordering in pan_display_legacy.
> - Support pinning buffers to current location in gem-vram.
> - Remove the now unused locking functions from gem-vram.
> - Remove the now unused kmap-object argument from vram helpers.
> - Stop checking return value of debugfs_create.
> - Add atomic encoder enable/disable helpers.
> - pass drm_atomic_state to atomic connector check.
> - Add atomic support for bridge enable/disable.
> - Add self refresh helpers to core.
> 
> Driver Changes:
> - Add extra delay to make MTP SDM845 work.
> - Small fixes to virtio, vkms, sii902x, sii9234, ast, mcde, analogix, 
> rockchip.
> - Add zpos and ?BGR support to meson.
> - More removals of drm_os_linux and drmP headers for amd, radeon, sti, r128, 
> r128, savage, sis.
> - Allow synopsis to unwedge the i2c hdmi bus.
> - Add orientation quirks for GPD panels.
> - Edid cleanups and fixing handling for edid < 1.2.
> - Add runtime pm to stm.
> - Handle s/r in dw-hdmi.
> - Add hooks for power on/off to dsi for stm.
> - Remove virtio dirty tracking code, done in drm core.
> - Rework BO handling in ast and mgag200.

Pulled, assuming it all compiles, I'll check my script after lunch.

Thanks, Daniel

> 
> The following changes since commit f5b07b04e5f090a85d1e96938520f2b2b58e4a8e:
> 
>   dma-buf: Discard old fence_excl on retrying get_fences_rcu for realloc 
> (2019-06-05 07:38:37 +0100)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2019-06-14
> 
> for you to fetch changes up to 51e857af9f3f1ab78be10ff6bf5c4a8a56f4e4d6:
> 
>   drm/amdgpu: Fix connector atomic_check compilation fail (2019-06-14 
> 09:33:56 +0200)
> 
> 
> drm-misc-next for v5.3:
> 
> UAPI Changes:
> 
> Cross-subsystem Changes:
> - Add code to signal all dma-fences when freed with pending signals.
> - Annotate reservation object access in CONFIG_DEBUG_MUTEXES
> 
> Core Changes:
> - Assorted documentation fixes.
> - Use irqsave/restore spinlock to add crc entry.
> - Move code around to drm_client, for internal modeset clients.
> - Make drm_crtc.h and drm_debugfs.h self-contained.
> - Remove drm_fb_helper_connector.
> - Add bootsplash to todo.
> - Fix lock ordering in pan_display_legacy.
> - Support pinning buffers to current location in gem-vram.
> - Remove the now unused locking functions from gem-vram.
> - Remove the now unused kmap-object argument from vram helpers.
> - Stop checking return value of debugfs_create.
> - Add atomic encoder enable/disable helpers.
> - pass drm_atomic_state to atomic connector check.
> - Add atomic support for bridge enable/disable.
> - Add self refresh helpers to core.
> 
> Driver Changes:
> - Add extra delay to make MTP SDM845 work.
> - Small fixes to virtio, vkms, sii902x, sii9234, ast, mcde, analogix, 
> rockchip.
> - Add zpos and ?BGR support to meson.
> - More removals of drm_os_linux and drmP headers for amd, radeon, sti, r128, 
> r128, savage, sis.
> - Allow synopsis to unwedge the i2c hdmi bus.
> - Add orientation quirks for GPD panels.
> - Edid cleanups and fixing handling for edid < 1.2.
> - Add runtime pm to stm.
> - Handle s/r in dw-hdmi.
> - Add hooks for power on/off to dsi for stm.
> - Remove virtio dirty tracking code, done in drm core.
> - Rework BO handling in ast and mgag200.
> 
> 
> Chris Wilson (2):
>   dma-fence: Signal all callbacks from dma_fence_release()
>   dma-fence/reservation: Markup rcu protected access for DEBUG_MUTEXES
> 
> Colin Ian King (1):
>   drm/bridge: sii902x: fix comparision of u32 with less than zero
> 
> Dan Carpenter (2):
>   drm/bridge: sii902x: re-order conditions to prevent out of bounds read
>   drm/mcde: Fix an uninitialized variable
> 
> Daniel Vetter (5):
>   drm/crc-debugfs: User irqsafe spinlock in drm_crtc_add_crc_entry
>   drm/vkms: Forward timer right after drm_crtc_handle_vblank
>   drm/crc-debugfs: Also sprinkle irqrestore over early exits
>   drm/fb: document dirty helper better
>   drm/ast: Drop fb_debug_enter/leave
> 
> David Riley (4):
>   drm/virtio: Ensure cached capset entries are valid before copying.
>   drm/virtio: Wake up all waiters when capset response comes 

Re: [PULL] drm-misc-next

2019-05-23 Thread Sean Paul
On Thu, May 23, 2019 at 05:47:04PM +0200, Maarten Lankhorst wrote:
> Hi Daniel and Dave,
> 
> We keep adding support for panels at a high rate, is it still worth listing 
> them individually under cross subsystem changes?
> 
> First pull req for v5.3 here, enjoy!
> As I was writing this mail, I missed a fix in mtk_hdmi_hw_send_info_frame for 
> the unhandled
> HDR case in switch, hope it's not too bad or I will send another. :)

It's not, but we should wait for Maxime's fix to my botched backmerge [1] in
order to avoid propagating the vendor prefixes file zombie to other trees.

So can we backburner this until that lands?

Sean

[1]- 
https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git/commit/?h=drm-misc-next=3832f2cad5307ebcedeead13fbd8d3cf06ba5e90

> 
> drm-misc-next-2019-05-23:
> 
> drm-misc-next for v5.3:
> 
> UAPI Changes:
> - Add HDR source metadata property.
> - Make drm.h compile on GNU/kFreeBSD by including stdint.h
> - Clarify how the userspace reviewer has to review new kernel UAPI.
> - Clarify that for using new UAPI, merging to drm-next or drm-misc-next 
> should be enough.
> 
> Cross-subsystem Changes:
> - video/hdmi: Add unpack function for DRM infoframes.
> - Device tree bindings:
>   * Updating a property for Mali Midgard GPUs
>   * Updating a property for STM32 DSI panel
>   * Adding support for FriendlyELEC HD702E 800x1280 panel
>   * Adding support for Evervision VGG804821 800x480 5.0" WVGA TFT panel
>   * Adding support for the EDT ET035012DM6 3.5" 320x240 QVGA 24-bit RGB TFT.
>   * Adding support for Three Five displays TFC S9700RTWV43TR-01B 800x480 panel
> with resistive touch found on TI's AM335X-EVM.
>   * Adding support for EDT ETM0430G0DH6 480x272 panel.
> - Add OSD101T2587-53TS driver with DT bindings.
> - Add Samsung S6E63M0 panel driver with DT bindings.
> - Add VXT VL050-8048NT-C01 800x480 panel with DT bindings.
> - Dma-buf:
>   - Make mmap callback actually optional.
>   - Documentation updates.
>   - Fix debugfs refcount inbalance.
>   - Remove unused sync_dump function.
> 
> Core Changes:
> - Add support for HDR infoframes and related EDID parsing.
> - Remove prime sg_table caching, now done inside dma-buf.
> - Add shiny new drm_gem_vram helpers for simple VRAM drivers;
>   with some fixes to the new API on top.
> - Small fix to job cleanup without timeout handler.
> - Documentation fixes to drm_fourcc.
> - Replace lookups of drm_format with struct drm_format_info;
>   remove functions that become obsolete by this conversion.
> - Remove double include in bridge/panel.c and some drivers.
> - Remove drmP.h include from drm/edid and drm/dp.
> - Fix null pointer deref in drm_fb_helper_hotplug_event().
> - Remove most members from drm_fb_helper_crtc, only mode_set is kept.
> - Remove race of fb helpers with userspace; only restore mode
>   when userspace is not master.
> - Move legacy setup from drm_file.c to drm_legacy_misc.c
> - Rework scheduler job destruction.
> - drm/bus was removed, remove from TODO.
> - Add __drm_atomic_helper_crtc_reset() to subclass crtc_state,
>   and convert some drivers to use it (conversion is not complete yet).
> - Bump vblank timeout wait to 100 ms for atomic.
> 
> Driver Changes:
> - sun4i: Use DRM_GEM_CMA_VMAP_DRIVER_OPS instead of definining manually.
> - v3d: Small cleanups, adding support for compute shaders,
>reservation/synchronization fixes and job management refactoring,
>fixes MMU and debugfs.
> - lima: Fix null pointer in irq handler on startup, set default timeout for 
> scheduled jobs.
> - stm/ltdc: Assorted fixes and adding FB modifier support.
> - amdgpu: Avoid hw reset if guilty job was already signaled.
> - virtio: Add seqno to fences, add trace events, use correct flags for fence 
> allocation.
> - Convert AST, bochs, mgag200, vboxvideo, hisilicon to the new drm_gem_vram 
> API.
> - sun6i_mipi_dsi: Support DSI GENERIC_SHORT_WRITE_2 transfers.
> - bochs: Small fix to use PTR_RET_OR_ZERO and driver unload.
> - gma500: header fixes
> - cirrus: Remove unused files.
> The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> 
>   Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2019-05-23
> 
> for you to fetch changes up to cbb56814fbe7fedd71cd6b29dc83bab2915a5b74:
> 
>   drm/virtio: remove irrelevant DRM_UNLOCKED flag (2019-05-23 12:16:01 +0200)
> 
> 
> We keep adding support for panels at a high rate, is it still worth listing 
> them individually?
> 
> drm-misc-next for v5.3:
> 
> UAPI Changes:
> - Add HDR source metadata property.
> - Make drm.h compile on GNU/kFreeBSD by including stdint.h
> - Clarify how the userspace reviewer has to review new kernel UAPI.
> - Clarify that for using new UAPI, merging to drm-next or drm-misc-next 
> should be enough.
> 
> Cross-subsystem Changes:
> - video/hdmi: Add 

Re: [PULL] drm-misc-next

2019-03-28 Thread Daniel Vetter
On Thu, Mar 28, 2019 at 4:33 PM Sean Paul  wrote:
>
>
> Hi Da.*,
> This week's -next pull is here! A couple of things to monitor in this one, the
> skip_vt_switch default and the DRM_DISPLAY_INFO_LEN removal (which definitely
> shouldn't be used by anyone, but stranger things have happened).
>
> Please pull.
>
>
> drm-misc-next-2019-03-28:
> drm-misc-next for 5.2:
>
> UAPI Changes:
> - Remove unused DRM_DISPLAY_INFO_LEN (Ville)
>
> Cross-subsystem Changes:
> - None
>
> Core Changes:
> - fbdev: Make skip_vt_switch default (Daniel)
> - Merge fb_helper_fill_fix, fb_helper_fill_var into fb_helper_fill_info 
> (Daniel)
> - Remove unused fields in connector, display_info, and edid_quirks (Ville)
>
> Driver Changes:
> - vkms: Fix potential NULL-dereference bug (Kangjie)
>
> Cc: Kangjie Lu 
> Cc: Daniel Vetter 
> Cc: Ville Syrjälä 

Uh, can you pls respin with

commit ec8bf1942567bf0736314da9723e93bcc73c131f
Author: Daniel Vetter 
Date:   Wed Mar 27 13:58:19 2019 +0100

drm/fb-helper: Fixup fill_info cleanup

included? Doesn't compile too well for !CONFIG_FBDEV otherwise. Sorry
for the mess.
-Daniel

>
> Cheers, Sean
>
>
> The following changes since commit ff01e6971ecd9ba6a9c0538c46d713f38a751f11:
>
>   drm/fourcc: Fix conflicting Y41x definitions (2019-03-21 09:49:04 +0100)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2019-03-28
>
> for you to fetch changes up to 9d5549d8a865793a1faf6ac9a48df08a3e850af6:
>
>   drm/edid: Remove defunct EDID_QUIRK_FIRST_DETAILED_PREFERRED (2019-03-27 
> 13:55:13 +0200)
>
> 
> drm-misc-next for 5.2:
>
> UAPI Changes:
> - Remove unused DRM_DISPLAY_INFO_LEN (Ville)
>
> Cross-subsystem Changes:
> - None
>
> Core Changes:
> - fbdev: Make skip_vt_switch default (Daniel)
> - Merge fb_helper_fill_fix, fb_helper_fill_var into fb_helper_fill_info 
> (Daniel)
> - Remove unused fields in connector, display_info, and edid_quirks (Ville)
>
> Driver Changes:
> - vkms: Fix potential NULL-dereference bug (Kangjie)
>
> Cc: Kangjie Lu 
> Cc: Daniel Vetter 
> Cc: Ville Syrjälä 
>
> 
> Daniel Vetter (24):
>   drm/hibmc: Drop best_encoder
>   drm/doc: Drop "content type" from the legacy kms property table
>   drm/fbdev: Make skip_vt_switch the default
>   drm/fb-helper: Add fill_info() functions
>   drm/fb-helper: set fbi->fix.id in fill_info()
>   drm/fb_helper: set info->par in fill_info()
>   drm/amdgpu: Use drm_fb_helper_fill_info
>   drm/armada: Use drm_fb_helper_fill_info
>   drm/ast: Use drm_fb_helper_fill_info
>   drm/cirrus: Use drm_fb_helper_fill_info
>   drm/exynos: Use drm_fb_helper_fill_info
>   drm/gma500: Use drm_fb_helper_fill_info
>   drm/hibmc: Use drm_fb_helper_fill_info
>   drm/i915: Use drm_fb_helper_fill_info
>   drm/mga200g: Use drm_fb_helper_fill_info
>   drm/msm: Use drm_fb_helper_fill_info
>   drm/nouveau: Use drm_fb_helper_fill_info
>   drm/omap: Use drm_fb_helper_fill_info
>   drm/radeon: Use drm_fb_helper_fill_info
>   drm/rockchip: Use drm_fb_helper_fill_info
>   drm/tegra: Use drm_fb_helper_fill_info
>   drm/vboxvideo: Use drm_fb_helper_fill_info
>   drm/udl: Use drm_fb_helper_fill_info
>   drm/fb-helper: Unexport fill_{var,info}
>
> Kangjie Lu (1):
>   drm: vkms: check status of alloc_ordered_workqueue
>
> Luca Ceresoli (1):
>   drm/doc: fix missing verb
>
> Ville Syrjälä (5):
>   drm: Nuke unused drm_display_info.pixel_clock
>   drm: Fix tabs vs. spaces
>   drm: Kill drm_display_info.name
>   drm/uapi: Remove unused DRM_DISPLAY_INFO_LEN
>   drm/edid: Remove defunct EDID_QUIRK_FIRST_DETAILED_PREFERRED
>
>  Documentation/gpu/kms-properties.csv   |  1 -
>  drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c | 25 +++-
>  drivers/gpu/drm/armada/armada_fbdev.c  |  6 +-
>  drivers/gpu/drm/ast/ast_drv.h  |  2 +-
>  drivers/gpu/drm/ast/ast_fb.c   |  7 +-
>  drivers/gpu/drm/cirrus/cirrus_drv.h|  2 +-
>  drivers/gpu/drm/cirrus/cirrus_fbdev.c  |  8 +--
>  drivers/gpu/drm/drm_edid.c | 10 ---
>  drivers/gpu/drm/drm_fb_helper.c| 75 
> +++---
>  drivers/gpu/drm/exynos/exynos_drm_fbdev.c  |  4 +-
>  drivers/gpu/drm/gma500/framebuffer.c   |  7 +-
>  drivers/gpu/drm/gma500/framebuffer.h   |  2 +-
>  drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.h|  2 +-
>  drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_fbdev.c  |  9 +--
>  drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_vdac.c   |  7 --
>  drivers/gpu/drm/i915/i915_debugfs.c|  1 -
>  drivers/gpu/drm/i915/intel_fbdev.c | 10 +--
>  drivers/gpu/drm/mgag200/mgag200_drv.h  |  2 +-
>  

Re: [PULL] drm-misc-next

2019-03-25 Thread Daniel Vetter
On Thu, Mar 21, 2019 at 6:08 PM Sean Paul  wrote:
>
>
> Hi Da.*,
> Here's the first 5.2 PR from -misc. There's a bit of everything in the PR,
> enjoy!

Pulled, thanks.
-Daniel

> drm-misc-next-2019-03-21:
> drm-misc-next for 5.2:
>
> UAPI Changes:
> - Add Colorspace connector property (Uma)
> - fourcc: Several new YUV formats from ARM (Brian & Ayan)
> - fourcc: Fix merge conflicts between new formats above and Swati's that
>   went in via topic/hdr-formats-2019-03-07 branch (Maarten)
>
> Cross-subsystem Changes:
> - Typed component support via topic/component-typed-2019-02-11 (Maxime/Daniel)
>
> Core Changes:
> - Improve component helper documentation (Daniel)
> - Avoid calling drm_dev_unregister() twice on unplugged devices (Noralf)
> - Add device managed (devm) drm_device init function (Noralf)
> - Graduate TINYDRM_MODE to DRM_SIMPLE_MODE in core (Noralf)
> - Move MIPI/DSI rate control params computation into core from i915 (David)
> - Add support for shmem backed gem objects (Noralf)
>
> Driver Changes:
> - various: Use of_node_name_eq for node name comparisons (Rob Herring)
> - sun4i: Add DSI burst mode support (Konstantin)
> - panel: Add Ronbo RB070D30 MIPI/DSI panel support (Konstantin)
> - virtio: A few prime improvements (Gerd)
> - tinydrm: Remove tinydrm_device (Noralf)
> - vc4: Add load tracker to driver to detect underflow in atomic check (Boris)
> - vboxvideo: Move it out of staging \o/ (Hans)
> - v3d: Add support for V3D v4.2 (Eric)
>
> Cc: Konstantin Sudakov 
> Cc: Rob Herring 
> Cc: Daniel Vetter 
> Cc: Maxime Ripard 
> Cc: Uma Shankar 
> Cc: Noralf Trønnes 
> Cc: Gerd Hoffmann 
> Cc: David Francis 
> Cc: Boris Brezillon 
> Cc: Eric Anholt 
> Cc: Hans de Goede 
> Cc: Brian Starkey 
> Cc: Ayan Kumar Halder 
> Cc: Maarten Lankhorst 
>
> Cheers, Sean
>
>
> The following changes since commit 4b057e73f28f1df13b77b77a52094238ffdf8abd:
>
>   Merge tag 'drm-misc-fixes-2019-02-22' of 
> git://anongit.freedesktop.org/drm/drm-misc into drm-next (2019-03-05 08:14:22 
> +1000)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2019-03-21
>
> for you to fetch changes up to ff01e6971ecd9ba6a9c0538c46d713f38a751f11:
>
>   drm/fourcc: Fix conflicting Y41x definitions (2019-03-21 09:49:04 +0100)
>
> 
> drm-misc-next for 5.2:
>
> UAPI Changes:
> - Add Colorspace connector property (Uma)
> - fourcc: Several new YUV formats from ARM (Brian & Ayan)
> - fourcc: Fix merge conflicts between new formats above and Swati's that
>   went in via topic/hdr-formats-2019-03-07 branch (Maarten)
>
> Cross-subsystem Changes:
> - Typed component support via topic/component-typed-2019-02-11 (Maxime/Daniel)
>
> Core Changes:
> - Improve component helper documentation (Daniel)
> - Avoid calling drm_dev_unregister() twice on unplugged devices (Noralf)
> - Add device managed (devm) drm_device init function (Noralf)
> - Graduate TINYDRM_MODE to DRM_SIMPLE_MODE in core (Noralf)
> - Move MIPI/DSI rate control params computation into core from i915 (David)
> - Add support for shmem backed gem objects (Noralf)
>
> Driver Changes:
> - various: Use of_node_name_eq for node name comparisons (Rob Herring)
> - sun4i: Add DSI burst mode support (Konstantin)
> - panel: Add Ronbo RB070D30 MIPI/DSI panel support (Konstantin)
> - virtio: A few prime improvements (Gerd)
> - tinydrm: Remove tinydrm_device (Noralf)
> - vc4: Add load tracker to driver to detect underflow in atomic check (Boris)
> - vboxvideo: Move it out of staging \o/ (Hans)
> - v3d: Add support for V3D v4.2 (Eric)
>
> Cc: Konstantin Sudakov 
> Cc: Rob Herring 
> Cc: Daniel Vetter 
> Cc: Maxime Ripard 
> Cc: Uma Shankar 
> Cc: Noralf Trønnes 
> Cc: Gerd Hoffmann 
> Cc: David Francis 
> Cc: Boris Brezillon 
> Cc: Eric Anholt 
> Cc: Hans de Goede 
> Cc: Brian Starkey 
> Cc: Ayan Kumar Halder 
> Cc: Maarten Lankhorst 
>
> 
> Andrey Grodzovsky (1):
>   drm/v3d: Fix calling drm_sched_resubmit_jobs for same sched.
>
> Andy Shevchenko (2):
>   drm/tinydrm: Trivia typo fix
>   drm/selftests/mm: Switch to bitmap_zalloc()
>
> Arnd Bergmann (1):
>   drm/stm: fix CONFIG_FB dependency
>
> Ayan Kumar Halder (9):
>   drm: Added a new format DRM_FORMAT_XVYU2101010
>   drm/arm/malidp: Set the AFBC register bits if the framebuffer has AFBC 
> modifier
>   drm/arm/malidp:- Added support for new YUV formats for DP500, DP550 and 
> DP650
>   drm/arm/malidp:- Define a common list of AFBC format modifiers 
> supported for DP500, DP550 and DP650
>   drm/arm/malidp: Specified the rotation memory requirements for AFBC YUV 
> formats
>   drm/arm/malidp:- Writeback framebuffer does not support any modifiers
>   drm/arm/malidp:- Use the newly introduced malidp_format_get_bpp() 
> instead of relying on cpp for calculating framebuffer size
>   drm/arm/malidp:- Disregard the pitch 

Re: [PULL] drm-misc-next

2019-02-14 Thread Daniel Vetter
On Mon, Feb 11, 2019 at 10:52:20AM +0100, Maxime Ripard wrote:
> Hi Dave, Daniel,
> 
> Here is the last (hopefully) pull request of drm-misc-next for the
> upcoming pull request.
> 
> Maxime
> 
> drm-misc-next-2019-02-11:
> drm-misc-next for 5.1:
> 
> UAPI Changes:
>   - New fourcc for P010 and P016 formats
> 
> Cross-subsystem Changes:
> 
> Core Changes:
>   - Removal of drm_calc_{h,v}scale_relaxed
>   - A few fixes for DP-MST
> 
> Driver Changes:
>   - More drmP.h cleanups
>   - A bunch of vkms fixes
>   - Conversion of the Cadence DSI bridge and Allwinner DSI driver to the
> generic phy MIPI-DPHY API
>   - New panel: Innolux EE101IA-01D
> The following changes since commit 16065fcdd19ddb9e093192914ac863884f308766:
> 
>   drm/virtio: do NOT reuse resource ids (2019-02-11 14:44:10 +1000)
> 
> are available in the Git repository at:
> 
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2019-02-11
> 
> for you to fetch changes up to 6649a95d35d850e417f125821a803ca7889c713c:
> 
>   drm/komeda: fix build with drm_modeset_helper.h update (2019-02-11 10:36:00 
> +0100)

Pulled, thanks.
-Daniel

> 
> 
> drm-misc-next for 5.1:
> 
> UAPI Changes:
>   - New fourcc for P010 and P016 formats
> 
> Cross-subsystem Changes:
> 
> Core Changes:
>   - Removal of drm_calc_{h,v}scale_relaxed
>   - A few fixes for DP-MST
> 
> Driver Changes:
>   - More drmP.h cleanups
>   - A bunch of vkms fixes
>   - Conversion of the Cadence DSI bridge and Allwinner DSI driver to the
> generic phy MIPI-DPHY API
>   - New panel: Innolux EE101IA-01D
> 
> 
> Ard Biesheuvel (1):
>   drm: disable uncached DMA optimization for ARM and arm64
> 
> Daniel Vetter (3):
>   staging/vboxvideo: don't set dev_priv_size = 0
>   staging/vboxvideo: Add TODO
>   drm/doc: Make igts for cross-driver stuff strongly suggested
> 
> Gerd Hoffmann (2):
>   drm/cirrus: add plane setup
>   drm/bochs: fix bochs_gem_prime_mmap
> 
> Gustavo A. R. Silva (1):
>   drm/vc4: Use struct_size() in kzalloc()
> 
> Heiko Stuebner (1):
>   dt-bindings: display: add binding for Innolux ee101ia-01d panel
> 
> Lyude Paul (5):
>   drm/dp_mst: Fix unbalanced malloc ref in drm_dp_mst_deallocate_vcpi()
>   drm/dp_mst: Remove port validation in drm_dp_atomic_find_vcpi_slots()
>   drm/atomic: Add drm_atomic_state->duplicated
>   drm/nouveau: Move PBN and VCPI allocation into nv50_head_atom
>   drm/dp_mst: Remove rebase-detritus in VCPI helper kernel-docs
> 
> Manasi Navare (1):
>   drm/dsc: Add kernel documentation for DRM DP DSC helpers
> 
> Matt Roper (1):
>   drm: Trivial comment grammar cleanups
> 
> Maxime Ripard (6):
>   sun6i: dsi: Convert to generic phy handling
>   phy: Move Allwinner A31 D-PHY driver to drivers/phy/
>   drm/bridge: cdns: Separate DSI and D-PHY configuration
>   drm/bridge: cdns: Convert to phy framework
>   drm/sun4i: dsi: Fix unitialized variable warning
>   Merge drm/drm-next into drm-misc-next
> 
> Oleksandr Andrushchenko (1):
>   drm/xen-front: Fix mmap attributes for display buffers
> 
> Randy Li (1):
>   drm/fourcc: Add new P010, P016 video format
> 
> Sam Ravnborg (6):
>   staging/vboxvideo: prepare for drmP.h removal from drm_modeset_helper.h
>   drm/i915: prepare for drmP.h removal from drm_modeset_helper.h
>   drm/rcar-du: prepare for drmP.h removal from drm_modeset_helper.h
>   drm: prepare for drmP.h removal from drm_modeset_helper.h
>   drm: remove drmP.h from drm_modeset_helper.h
>   drm/komeda: fix build with drm_modeset_helper.h update
> 
> Shayenne Moura (5):
>   drm/vkms: Bugfix extra vblank frame
>   drm/vkms: Bugfix racing hrtimer vblank handle
>   drm/doc: Remove solved "VBlank issues"
>   drm/vkms: WARN when hrtimer_forward_now fails
>   drm/doc: Remove solved KMS cleanup task
> 
> Ville Syrjälä (1):
>   drm: Nuke drm_calc_{h,v}scale_relaxed()
> 
> YueHaibing (1):
>   drm/xen-front: Drop pointless static qualifier in fb_destroy()
> 
>  .../bindings/display/panel/innolux,ee101ia-01d.txt |   7 +
>  Documentation/gpu/drm-uapi.rst |   8 +
>  Documentation/gpu/todo.rst |   4 -
>  Documentation/gpu/vkms.rst |  11 -
>  drivers/gpu/drm/arm/display/komeda/komeda_crtc.c   |   8 +-
>  drivers/gpu/drm/arm/display/komeda/komeda_dev.c|   6 +-
>  .../drm/arm/display/komeda/komeda_framebuffer.c|   6 +-
>  drivers/gpu/drm/arm/display/komeda/komeda_kms.c|  12 +-
>  drivers/gpu/drm/arm/display/komeda/komeda_kms.h|   1 +
>  .../gpu/drm/arm/display/komeda/komeda_pipeline.c   |   2 +
>  drivers/gpu/drm/bochs/bochs_mm.c   |   3 +-
>  drivers/gpu/drm/bridge/Kconfig |   1 +
>  drivers/gpu/drm/bridge/cdns-dsi.c  | 542 
> +
> 

Re: [PULL] drm-misc-next

2019-01-16 Thread Daniel Vetter
On Tue, Jan 15, 2019 at 4:57 PM Maxime Ripard  wrote:
>
> Hi Daniel, Dave,
>
> Here is the drm-misc-next PR for this week.
>
> Thanks!
> Maxime
>
> drm-misc-next-2019-01-15:
> drm-misc-next for 5.1:
>
> UAPI Changes:
>
> Cross-subsystem Changes:
>
> Core Changes:
>  - Reorganisation of drm_device and drm_framebuffer headers
>  - Cleanup of the drmP inclusion
>  - Fix leaks in the fb-helpers
>  - Allow for depth different from bpp in fb-helper fbdev emulation
>
> Driver Changes:
>  - Add reflection properties to rockchip
>  - a bunch of fixes for virtio
>  - a bunch of fixes for dp_mst and drivers using it, and introduction of a
>new refcounting scheme

Unfortunately this had a bug in the i915 mst errno handling, which
Lyude fixed in

commit 96550555a78ca3c9fda4b358549a5622810fe32c
Author: Lyude Paul 
Date:   Tue Jan 15 15:08:00 2019 -0500

drm/i915: Pass down rc in intel_encoder->compute_config()

This patch is also causing quite some conflicts with in-flight
drm-intel stuff. Can you please respin your pull request, since
getting the mst stuff in a half-broken state and without the massive
conflicting patches would cause pains for intel folks?

Thanks, Daniel
>  - Convertion of bochs to atomic and generic fbdev emulation
>  - Allow meson to remove the firmware framebuffers
> The following changes since commit e3d093070eb0b5e3df668d3eb04100ea79343c65:
>
>   Merge tag 'tilcdc-4.22' of https://github.com/jsarha/linux into drm-next 
> (2019-01-11 06:29:31 +1000)
>
> are available in the Git repository at:
>
>   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2019-01-15
>
> for you to fetch changes up to ed20151a7699bb2c77eba3610199789a126940c4:
>
>   drm/vblank: Allow dynamic per-crtc max_vblank_count (2019-01-14 21:23:55 
> +0200)
>
> 
> drm-misc-next for 5.1:
>
> UAPI Changes:
>
> Cross-subsystem Changes:
>
> Core Changes:
>  - Reorganisation of drm_device and drm_framebuffer headers
>  - Cleanup of the drmP inclusion
>  - Fix leaks in the fb-helpers
>  - Allow for depth different from bpp in fb-helper fbdev emulation
>
> Driver Changes:
>  - Add reflection properties to rockchip
>  - a bunch of fixes for virtio
>  - a bunch of fixes for dp_mst and drivers using it, and introduction of a
>new refcounting scheme
>  - Convertion of bochs to atomic and generic fbdev emulation
>  - Allow meson to remove the firmware framebuffers
>
> 
> Daniel Vetter (14):
>   drm/todo: Better defio support in the generic fbdev emulation
>   drm/crtc-helpers: WARN when used with atomic drivers
>   drm/ch7006: Stop using drm_crtc_force_disable
>   drm/nouveau: Stop using drm_crtc_force_disable
>   drm: Unexport drm_crtc_force_disable
>   drm/atomic: Add missing () to function ref in kerneldoc
>   drm: Move the legacy kms disable_all helper to crtc helpers
>   drm/arc: Don't set the dpms hook
>   drm/tda998x: Don't set dpms hook
>   drm/doc: Polish kerneldoc for drm_device.h
>   drm/docs: improve docs for drm_drv.c
>   drm/of: Fix kerneldoc
>   drm/panel: Small documentation polish
>   drm/doc: Move bridge link target to the right place
>
> Daniele Castagna (2):
>   drm/rockchip: Fix YUV buffers color rendering
>   drm/rockchip: Add reflection properties
>
> Enric Balletbo i Serra (1):
>   drm/rockchip: update cursors asynchronously through atomic.
>
> Ezequiel Garcia (5):
>   drm/virtio: Remove incorrect kfree()
>   drm/virtio: Add missing virtqueue reset
>   drm/virtio: Drop deprecated load/unload initialization
>   drm/rockchip: Fix typo in VOP macros argument
>   drm/rockchip: Separate RK3288 from RK3368 win01 registers
>
> Gerd Hoffmann (19):
>   drm/virtio: log error responses
>   drm/virtio: fix pageflip flush
>   drm/virtio: drop virtio_gpu_fence_cleanup()
>   drm/bochs: encoder cleanup
>   drm/bochs: split bochs_hw_setmode
>   drm/bochs: atomic: add atomic_flush+atomic_enable callbacks.
>   drm/bochs: atomic: add mode_set_nofb callback.
>   drm/bochs: atomic: switch planes to atomic, wire up helpers.
>   drm/bochs: atomic: use atomic set_config helper
>   drm/bochs: atomic: use atomic page_flip helper
>   drm/bochs: atomic: use suspend/resume helpers
>   drm/bochs: atomic: set DRIVER_ATOMIC
>   drm/bochs: remove old bochs_crtc_* functions
>   drm/bochs: drop unused gpu_addr arg from bochs_bo_pin()
>   drm/bochs: move ttm_bo_(un)reserve calls into bochs_bo_{pin, unpin}
>   drm/bochs: add basic prime support
>   drm/bochs: switch to generic drm fbdev emulation
>   drm/bochs: drop old fbdev emulation code
>   drm/bochs: move remaining fb bits to kms
>
> Gustavo A. R. Silva (1):
>   qxl: Use struct_size() in kzalloc()
>
> Kuo-Hsin Yang (1):
>   drm/gem: Mark pinned pages as unevictable
>
> Linus Walleij 

Re: [PULL] drm-misc-next

2018-11-09 Thread Christian König

Am 07.11.18 um 21:48 schrieb Sean Paul:

On Wed, Nov 07, 2018 at 09:31:51PM +0100, Daniel Vetter wrote:

On Wed, Nov 7, 2018 at 9:29 PM Sean Paul  wrote:

On Wed, Nov 07, 2018 at 09:18:16PM +0100, Daniel Vetter wrote:

On Wed, Nov 07, 2018 at 12:58:56PM +0100, Maarten Lankhorst wrote:

Hey Dave,

First pull for drm-next this cycle. There's been a lot of changes, so I
hope I recorded everything from the changelog correctly.

drm-misc-next-2018-11-07:
drm-misc-next for v4.21, part 1:

UAPI Changes:
- Add syncobj timeline support to drm.

With all the CI breakage this caused I kinda missed that it didn't get
reverted. But afaict this didn't have the ack from anv/radv folks (which I
explicitly asked for as part of what I think should be the merge
criteria), and I'm not sure where the userspace is, and this here isn't
just prep, but already adds new uapi.


+Christian

Can you please land the revert while we get this sorted out?

The revert was for the CI breakage, which is sorted out differently
already. That was kinda just my excuse for not being in the loop. For
just the uapi disallowing timeline obj creation and moving the #define
away from the uapi include is all that's really needed.

Yeah, the uapi #define looked simple enough to back out. Whatever unblocks us
from moving forward is good with me.


Agreed, should I take care of that?



That said, reading through the review thread, this doesn't seem like something
that should have been applied in the first place.


Well it was the usual problem of not getting enough attention on a patch 
set.


Christian.



Sean


Assuming of course that I'm not again having my stuff all mixed up :-)
-Daniel


Sean


The prep work is imo totally ok to keep, but the uapi side seems rather
questionable.
-Daniel


Cross-subsystem Changes:
- Remove shared fence staging in dma-buf's fence object, and allow
   reserving more than 1 fence and add more paranoia when debugging.
- Constify infoframe functions in video/hdmi.

Core Changes:
- Add vkms todo, and a lot of assorted doc fixes.
- Drop transitional helpers and convert drivers to use 
drm_atomic_helper_shutdown().
- Move atomic state helper functions to drm_atomic_state_helper.[ch]
- Refactor drm selftests, and add new tests.
- DP MST atomic state cleanups.
- Drop EXPORT_SYMBOL from drm leases.
- Lease cleanups and fixes.
- Create render node for vgem.

Driver Changes:
- Fix build failure in imx without fbdev emulation.
- Add rotation quirk for GPD win2 panel.
- Add support for various CDTech panels, Banana Pi Panel, DLC1010GIG,
   Olimex LCD-O-LinuXino, Samsung S6D16D0, Truly NT35597 WQXGA,
   Himax HX8357D, simulated RTSM AEMv8.
- Add dw_hdmi support to rockchip driver.
- Fix YUV support in vc4.
- Fix resource id handling in virtio.
- Make rockchip use dw-mipi-dsi bridge driver, and add dual dsi support.
- Advertise that tinydrm only supports DRM_FORMAT_MOD_LINEAR.
- Convert many drivers to use atomic helpers, and drm_fbdev_generic_setup().
- Add Mali linear tiled formats, and enable them in the Mali-DP driver.
- Add support for H6 DE3 mixer 0, DW HDMI, HDMI PHY and TCON TOP.
- Assorted driver cleanups and fixes.

The following changes since commit f2bfc71aee75feff33ca659322b72ffeed5a243d:

   Merge tag 'drm-intel-next-fixes-2018-10-18' of 
git://anongit.freedesktop.org/drm/drm-intel into drm-next (2018-10-19 14:28:11 
+1000)

are available in the Git repository at:

   git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-2018-11-07

for you to fetch changes up to e7afb623b4fb82089c9a50c733c740522b8220bc:

   drm: Add drm_any_plane_has_format() (2018-11-06 21:34:22 +0200)


drm-misc-next for v4.21, part 1:

UAPI Changes:
- Add syncobj timeline support to drm.

Cross-subsystem Changes:
- Remove shared fence staging in dma-buf's fence object, and allow
   reserving more than 1 fence and add more paranoia when debugging.
- Constify infoframe functions in video/hdmi.

Core Changes:
- Add vkms todo, and a lot of assorted doc fixes.
- Drop transitional helpers and convert drivers to use 
drm_atomic_helper_shutdown().
- Move atomic state helper functions to drm_atomic_state_helper.[ch]
- Refactor drm selftests, and add new tests.
- DP MST atomic state cleanups.
- Drop EXPORT_SYMBOL from drm leases.
- Lease cleanups and fixes.
- Create render node for vgem.

Driver Changes:
- Fix build failure in imx without fbdev emulation.
- Add rotation quirk for GPD win2 panel.
- Add support for various CDTech panels, Banana Pi Panel, DLC1010GIG,
   Olimex LCD-O-LinuXino, Samsung S6D16D0, Truly NT35597 WQXGA,
   Himax HX8357D, simulated RTSM AEMv8.
- Add dw_hdmi support to rockchip driver.
- Fix YUV support in vc4.
- Fix resource id handling in virtio.
- Make rockchip use dw-mipi-dsi bridge driver, and add dual dsi support.
- Advertise that tinydrm only supports DRM_FORMAT_MOD_LINEAR.
- Convert many drivers to use atomic helpers, and drm_fbdev_generic_setup().
- Add 

Re: [PULL] drm-misc-next

2018-11-08 Thread Maarten Lankhorst
Op 07-11-18 om 21:48 schreef Sean Paul:
> On Wed, Nov 07, 2018 at 09:31:51PM +0100, Daniel Vetter wrote:
>> On Wed, Nov 7, 2018 at 9:29 PM Sean Paul  wrote:
>>> On Wed, Nov 07, 2018 at 09:18:16PM +0100, Daniel Vetter wrote:
 On Wed, Nov 07, 2018 at 12:58:56PM +0100, Maarten Lankhorst wrote:
> Hey Dave,
>
> First pull for drm-next this cycle. There's been a lot of changes, so I
> hope I recorded everything from the changelog correctly.
>
> drm-misc-next-2018-11-07:
> drm-misc-next for v4.21, part 1:
>
> UAPI Changes:
> - Add syncobj timeline support to drm.
 With all the CI breakage this caused I kinda missed that it didn't get
 reverted. But afaict this didn't have the ack from anv/radv folks (which I
 explicitly asked for as part of what I think should be the merge
 criteria), and I'm not sure where the userspace is, and this here isn't
 just prep, but already adds new uapi.

>>> +Christian
>>>
>>> Can you please land the revert while we get this sorted out?
>> The revert was for the CI breakage, which is sorted out differently
>> already. That was kinda just my excuse for not being in the loop. For
>> just the uapi disallowing timeline obj creation and moving the #define
>> away from the uapi include is all that's really needed.
> Yeah, the uapi #define looked simple enough to back out. Whatever unblocks us
> from moving forward is good with me.
>
> That said, reading through the review thread, this doesn't seem like something
> that should have been applied in the first place.
I didn't follow the syncobj breakage much, but yeah would be good to have it 
fixed first.

I'll send a new pull req when the revert is applied. :)
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel


  1   2   >