Re: [PATCH v2] drm/bridge: imx: i.MX8 bridge drivers should depend on ARCH_MXC

Hi Neil, Robert, On Tue, 2022-06-28 at 09:10 +0200, Neil Armstrong wrote: > On 28/06/2022 04:31, Liu Ying wrote: > > On Mon, 2022-06-27 at 14:22 +0200, Neil Armstrong wrote: > > > Hi, > > > > Hi, > > > > > > > > On 24/06/2022 14:10, Geert Uytterhoeven wrote: > > > > The various Freescale i.MX8

Re: [PATCH 2/5] fbcon: Fix up user-provided virtual screen size

Hi Helge, On Thu, Jun 30, 2022 at 10:10 PM Helge Deller wrote: > On 6/30/22 22:00, Geert Uytterhoeven wrote: > > On Thu, Jun 30, 2022 at 9:46 PM Helge Deller wrote: > >> On 6/30/22 21:36, Geert Uytterhoeven wrote: > >>> On Thu, Jun 30, 2022 at 9:31 PM Helge Deller wrote: > On 6/30/22 21:00

[PATCH 0/7] msm8916/msm8939 DSI controller and DSI PHY bindings fixes

This series fixes up a number of dtbs checks which are being flagged adding in the msm8939 dtsi. When converting from .txt to .yaml a number of the parameters for the older msm8916 silicon were not transmitted into the yaml. Adding in the msm8939 which is a near 1:1 copy of the msm8916 in terms o

[PATCH 5/7] dt-bindings: msm: dsi: Fix clock declarations

When converting from .txt to .yaml dt-binding descriptions we appear to have missed some of the previous detail on the number and names of permissible clocks. Fixes: 4dbe55c97741 ("dt-bindings: msm: dsi: add yaml schemas for DSI bindings") Signed-off-by: Bryan O'Donoghue --- .../display/msm/dsi-

[PATCH 3/7] dt-bindings: msm: dsi: Fix power-domains constraint

The existing msm8916.dtsi does not depend on nor require power-domains. Drop from the list of required. Fixes: 4dbe55c97741 ("dt-bindings: msm: dsi: add yaml schemas for DSI bindings") Signed-off-by: Bryan O'Donoghue --- .../devicetree/bindings/display/msm/dsi-controller-main.yaml | 1 - 1 f

[PATCH 1/7] dt-bindings: msm: dsi: Fix phy-name binding

The driver doesn't care about the name of the phy in DTS. msm8916 has since 2016 named the phy "dsi-phy" with later SoCs taking the name "dsi". There's no reason to have a constraint on the name here, simply to have a name. Remove the redundant const in favour of maxItems: 1. Fixes: 4dbe55c97741

Re: [PATCH v3 00/15] Canaan devicetree fixes

On 7/1/22 02:53, Sudeep Holla wrote: > On Thu, Jun 30, 2022 at 04:28:26PM +, Niklas Cassel wrote: >> On Wed, Jun 29, 2022 at 07:43:29PM +0100, Conor Dooley wrote: >>> From: Conor Dooley >>> >>> Hey all, >>> This series should rid us of dtbs_check errors for the RISC-V Canaan k210 >>> based boa

Re: [PATCH 4/7] dt-bindings: msm: dsi: Add vdd* descriptions back in

On 30/06/2022 18:16, Dmitry Baryshkov wrote: All three descriptions are the same. This looks like a c&p issue Those are what the previous values were. I'll come up with something less robotic though.

[PATCH 6/7] dt-bindings: msm: dsi: Add missing clocks to 28nm DSI PHY YAML

Add in missing clock and clock-names declarations to the 28nm DSI PHY. When converting from .txt to .yaml we missed these. Fixes: 4dbe55c97741 ("dt-bindings: msm: dsi: add yaml schemas for DSI bindings") Signed-off-by: Bryan O'Donoghue --- .../bindings/display/msm/dsi-phy-28nm.yaml | 17 +++

Re: [PATCH v3 13/15] riscv: dts: canaan: fix bus {ranges,reg} warnings

On Wed, Jun 29, 2022 at 07:43:42PM +0100, Conor Dooley wrote: > From: Conor Dooley > > The k210 devicetrees warn about missing/empty reg and/or ranges > properties: > arch/riscv/boot/dts/canaan/k210.dtsi:408.22-460.5: Warning > (unit_address_vs_reg): /soc/bus@5200: node has a unit name, but

[PATCH 4/7] dt-bindings: msm: dsi: Add vdd* descriptions back in

When converting from .txt to .yaml we didn't include descriptions for the existing regulator supplies. - vdd - vdda - vddio Add those descriptions into the yaml now as they were prior to the conversion. Fixes: 4dbe55c97741 ("dt-bindings: msm: dsi: add yaml schemas for DSI bindings") Signed-off-b

Re: [PATCH 3/7] dt-bindings: msm: dsi: Fix power-domains constraint

On 30/06/2022 20:01, Krzysztof Kozlowski wrote: On 30/06/2022 14:08, Bryan O'Donoghue wrote: The existing msm8916.dtsi does not depend on nor require power-domains. Drop from the list of required. That's not good reason. The bindings are about hardware so the question is whether being a part o

[PATCH 7/7] dt-bindings: msm: dsi: Add missing qcom, dsi-phy-regulator-ldo-mode

Add in missing qcom,dsi-phy-regulator-ldo-mode to the 28nm DSI PHY. When converting from .txt to .yaml we missed this one. Fixes: 4dbe55c97741 ("dt-bindings: msm: dsi: add yaml schemas for DSI bindings") Signed-off-by: Bryan O'Donoghue --- .../devicetree/bindings/display/msm/dsi-phy-28nm.yaml

[PATCH 2/7] dt-bindings: msm: dsi: Fix operating-points-v2 constraint

The existing msm8916.dtsi does not depend on nor require operating points. Fixes: 4dbe55c97741 ("dt-bindings: msm: dsi: add yaml schemas for DSI bindings") Signed-off-by: Bryan O'Donoghue --- .../devicetree/bindings/display/msm/dsi-controller-main.yaml | 1 - 1 file changed, 1 deletion(-) d

Re: [PATCH v3 00/15] Canaan devicetree fixes

On Wed, Jun 29, 2022 at 07:43:29PM +0100, Conor Dooley wrote: > From: Conor Dooley > > Hey all, > This series should rid us of dtbs_check errors for the RISC-V Canaan k210 > based boards. To make keeping it that way a little easier, I changed the > Canaan devicetree Makefile so that it would buil

Re: [Freedreno] [PATCH 3/7] dt-bindings: msm: dsi: Fix power-domains constraint

On Thu, Jun 30, 2022 at 08:49:03PM +0100, Bryan O'Donoghue wrote: > On 30/06/2022 20:01, Krzysztof Kozlowski wrote: > > On 30/06/2022 14:08, Bryan O'Donoghue wrote: > > > The existing msm8916.dtsi does not depend on nor require power-domains. > > > Drop from the list of required. > > > > That's no

Re: [PATCH 5/6] drm/i915/gt: Serialize GRDOM access between multiple engine resets

On 30/06/2022 17:01, Mauro Carvalho Chehab wrote: Em Thu, 30 Jun 2022 09:12:41 +0100 Tvrtko Ursulin escreveu: On 30/06/2022 08:32, Mauro Carvalho Chehab wrote: Em Wed, 29 Jun 2022 17:02:59 +0100 Tvrtko Ursulin escreveu: On 29/06/2022 16:30, Mauro Carvalho Chehab wrote: On Tue, 28 Jun

Re: [PATCH v13 05/10] drm/mediatek: Add MT8195 Embedded DisplayPort driver

Il 01/07/22 08:28, Bo-Chen Chen ha scritto: From: Markus Schneider-Pargmann This patch adds a embedded displayport driver for the MediaTek mt8195 SoC. It supports the MT8195, the embedded DisplayPort units. It offers DisplayPort 1.4 with up to 4 lanes. The driver creates a child device for th

Re: [Intel-gfx] [PATCH v6 3/3] drm/doc/rfc: VM_BIND uapi definition

On 30/06/2022 17:22, Niranjana Vishwanathapura wrote: On Thu, Jun 30, 2022 at 08:59:09AM +0100, Tvrtko Ursulin wrote: On 30/06/2022 07:08, Niranjana Vishwanathapura wrote: On Wed, Jun 29, 2022 at 05:33:49PM -0700, Zanoni, Paulo R wrote: On Sat, 2022-06-25 at 18:49 -0700, Niranjana Vishwanat

Re: [PATCH v13 06/10] drm/mediatek: Add MT8195 External DisplayPort support

Il 01/07/22 08:28, Bo-Chen Chen ha scritto: From: Guillaume Ranquet This patch adds External DisplayPort support to the mt8195 eDP driver. Signed-off-by: Guillaume Ranquet Signed-off-by: Bo-Chen Chen --- drivers/gpu/drm/mediatek/mtk_dp.c | 197 +- drivers/gpu/d

Re: [Intel-gfx] [PATCH v2] drm/i915: Fix vm use-after-free in vma destruction

On Mon, 20 Jun 2022 at 13:37, Thomas Hellström wrote: > > In vma destruction, the following race may occur: > > Thread 1: Thread 2: > i915_vma_destroy(); > > ... > list_del_init(vma->vm_link); > ... > mutex_unlock(vma->vm->mutex); >

Re: [PATCH v13 09/10] drm/mediatek: DP audio support for MT8195

Il 01/07/22 08:28, Bo-Chen Chen ha scritto: From: Guillaume Ranquet This patch adds audio support to the DP driver for MT8195 with up to 8 channels. Signed-off-by: Guillaume Ranquet Signed-off-by: Bo-Chen Chen Reviewed-by: AngeloGioacchino Del Regno

[PATCH V2 00/30] OPP: Add new configuration interface: dev_pm_opp_set_config()

Hello, We have too many configuration specific APIs currently, six of them already, like dev_pm_opp_set_regulators(). This makes it complex/messy for both the OPP core and its users to manage. There is also code redundancy in these APIs, in the way they add/manage the OPP table specific stuff. Th

[PATCH V2 13/30] drm/lima: Migrate to dev_pm_opp_set_config()

The OPP core now provides a unified API for setting all configuration types, i.e. dev_pm_opp_set_config(). Lets start using it. Signed-off-by: Viresh Kumar --- drivers/gpu/drm/lima/lima_devfreq.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/drivers/gpu/drm/li

[PATCH V2 14/30] drm/msm: Migrate to dev_pm_opp_set_config()

The OPP core now provides a unified API for setting all configuration types, i.e. dev_pm_opp_set_config(). Lets start using it. Signed-off-by: Viresh Kumar --- drivers/gpu/drm/msm/adreno/a5xx_gpu.c | 8 ++-- drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 10 +- drivers/gpu/drm/msm/dis

[PATCH V2 15/30] drm/panfrost: Migrate to dev_pm_opp_set_config()

The OPP core now provides a unified API for setting all configuration types, i.e. dev_pm_opp_set_config(). Lets start using it. Acked-by: Steven Price Signed-off-by: Viresh Kumar --- drivers/gpu/drm/panfrost/panfrost_devfreq.c | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) dif

[PATCH V2 16/30] drm/tegra: Migrate to dev_pm_opp_set_config()

The OPP core now provides a unified API for setting all configuration types, i.e. dev_pm_opp_set_config(). Lets start using it. Tested-by: Dmitry Osipenko Signed-off-by: Viresh Kumar --- drivers/gpu/drm/tegra/gr3d.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/drive

Re: [PATCH v7 2/2] drm/gem: Don't map imported GEMs

On 6/30/22 23:26, Thomas Hellström (Intel) wrote: > > On 6/30/22 22:22, Dmitry Osipenko wrote: >> Hello Thomas, >> >> On 6/30/22 23:15, Thomas Hellström (Intel) wrote: >>> Hi, Dmitry, >>> >>> On 6/30/22 22:04, Dmitry Osipenko wrote: Drivers that use drm_gem_mmap() and drm_gem_mmap_obj() helpe

Re: [PATCH v13 10/10] drm/mediatek: fix no audio when resolution change

Il 01/07/22 08:28, Bo-Chen Chen ha scritto: When switching resolutions, config the audio setting with the previous audio parameters. Signed-off-by: Jitao Shi Signed-off-by: Bo-Chen Chen Change the title to: drm/mediatek: Use cached audio config when changing resolution ...and a more suitabl

Re: [PATCH v2] drm/bridge: imx: i.MX8 bridge drivers should depend on ARCH_MXC

Hi, On Fri, 24 Jun 2022 14:10:51 +0200, Geert Uytterhoeven wrote: > The various Freescale i.MX8 display bridges are only present on > Freescale i.MX8 SoCs. Hence add a dependency on ARCH_MXC, to prevent > asking the user about these drivers when configuring a kernel without > i.MX SoC support. >

Re: [PATCH v6 3/3] drm/doc/rfc: VM_BIND uapi definition

On 30/06/2022 17:23, Matthew Auld wrote: On 30/06/2022 16:34, Jason Ekstrand wrote: On Thu, Jun 30, 2022 at 10:14 AM Matthew Auld > wrote:     On 30/06/2022 06:11, Jason Ekstrand wrote: > On Sat, Jun 25, 2022 at 8:49 PM Niranjana Vishwanathapura > mailto

Re: [PATCH resend] drm: panel-orientation-quirks: Add quirk for the Lenovo Yoga Tablet 2 830

Hi, On 6/23/22 13:46, Javier Martinez Canillas wrote: > Hello Hans, > > On 6/23/22 13:27, Hans de Goede wrote: >> The Lenovo Yoga Tablet 2 830F / 830L use a panel which has been mounted >> 90 degrees rotated. Add a quirk for this. >> >> Signed-off-by: Hans de Goede >> --- > > The patch looks go

[PATCH v4 1/2] drm/i915/edid: convert DP, HDMI and LVDS to drm_edid

Convert all the connectors that use cached connector edid and detect_edid to drm_edid. Since drm_get_edid() calls drm_connector_update_edid_property() while drm_edid_read*() do not, we need to call drm_edid_connector_update() separately, in part due to the EDID caching behaviour in HDMI and DP. Es

[PATCH v4 0/2] drm/i915: switch DP, HDMI and LVDS to drm_edid

The remaining patches to add HF-EEODB support to i915 by switching to using drm_edid in certain encoders. This depends on the drm_edid work in drm-misc-next, and either needs to be merged via drm-misc-next, or we'll need the dependencies merged to drm-intel-next via drm-misc-next pull request -> dr

[PATCH v4 2/2] drm/i915/bios: convert intel_bios_init_panel() to drm_edid

Try to use struct drm_edid where possible, even if having to fall back to looking into struct edid down low via drm_edid_raw(). v2: Rebase Signed-off-by: Jani Nikula Reviewed-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/intel_bios.c | 19 ++- drivers/gpu/drm/i915/display/

Re: [PATCH v4 1/2] drm/i915/edid: convert DP, HDMI and LVDS to drm_edid

On Fri, 01 Jul 2022, Jani Nikula wrote: > Convert all the connectors that use cached connector edid and > detect_edid to drm_edid. > > Since drm_get_edid() calls drm_connector_update_edid_property() while > drm_edid_read*() do not, we need to call drm_edid_connector_update() > separately, in part

[PATCH v8 0/2] DRM GEM fixes

This patchset fixes two problems in the common GEM code. First fixed problem is the bogus lockdep splat that complicates debugging of DRM drivers. Second problem is the inconsistency in behaviour and improper handling of mapping the imported GEMs by some drivers, to fix it we will prohibit to map t

[PATCH v8 2/2] drm/gem: Don't map imported GEMs

Drivers that use drm_gem_mmap() and drm_gem_mmap_obj() helpers don't handle imported dma-bufs properly, which results in mapping of something else than the imported dma-buf. On NVIDIA Tegra we get a hard lockup when userspace writes to the memory mapping of a dma-buf that was imported into Tegra's

[PATCH v8 1/2] drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error

Use ww_acquire_fini() in the error code paths. Otherwise lockdep thinks that lock is held when lock's memory is freed after the drm_gem_lock_reservations() error. The ww_acquire_context needs to be annotated as "released", which fixes the noisy "WARNING: held lock freed!" splat of VirtIO-GPU driver

[PATCH -next] drm/amd/display: clean up some inconsistent indenting

Eliminate the follow smatch warning: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:3151 commit_planes_for_stream() warn: inconsistent indenting Signed-off-by: Yang Li --- drivers/gpu/drm/amd/display/dc/core/dc.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a

Re: [PATCH 2/5] fbcon: Fix up user-provided virtual screen size

Hi Geert, On 7/1/22 09:28, Geert Uytterhoeven wrote: > On Thu, Jun 30, 2022 at 10:10 PM Helge Deller wrote: >> On 6/30/22 22:00, Geert Uytterhoeven wrote: >>> On Thu, Jun 30, 2022 at 9:46 PM Helge Deller wrote: On 6/30/22 21:36, Geert Uytterhoeven wrote: > On Thu, Jun 30, 2022 at 9:31 P

Re: (subset) [PATCH v3 00/15] Canaan devicetree fixes

On Wed, 29 Jun 2022 19:43:29 +0100, Conor Dooley wrote: > From: Conor Dooley > > Hey all, > This series should rid us of dtbs_check errors for the RISC-V Canaan k210 > based boards. To make keeping it that way a little easier, I changed the > Canaan devicetree Makefile so that it would build all

Re: [PATCH v6 14/22] dma-buf: Introduce new locking convention

On 6/29/22 00:26, Thomas Hellström (Intel) wrote: > > On 5/30/22 15:57, Dmitry Osipenko wrote: >> On 5/30/22 16:41, Christian König wrote: >>> Hi Dmitry, >>> >>> Am 30.05.22 um 15:26 schrieb Dmitry Osipenko: Hello Christian, On 5/30/22 09:50, Christian König wrote: > Hi Dmitry,

Re: [PATCH 1/3] drm/bridge: fsl-ldb: Fix mode clock rate validation

On 7/1/22 08:56, Liu Ying wrote: With LVDS dual link, up to 160MHz mode clock rate is supported. With LVDS single link, up to 80MHz mode clock rate is supported. Fix mode clock rate validation by swapping the maximum mode clock rates of the two link modes. Fixes: 463db5c2ed4a ("drm: bridge: ldb:

Re: [PATCH 2/3] drm/bridge: fsl-ldb: Enable split mode for LVDS dual link

On 7/1/22 08:56, Liu Ying wrote: When LVDS dual link is used, we have to enable the LDB_CTRL_SPLIT_MODE bit. Fixes: 463db5c2ed4a ("drm: bridge: ldb: Implement simple Freescale i.MX8MP LDB bridge") Cc: Andrzej Hajda Cc: Neil Armstrong Cc: Robert Foss Cc: Laurent Pinchart Cc: Jonas Karlman C

Re: [PATCH 3/3] drm/bridge: fsl-ldb: Drop DE signal polarity inversion

On 7/1/22 08:56, Liu Ying wrote: It's unnecessary to invert input data enable signal polarity according to the output one. Let's drop the inversion. Since ->atomic_check() does nothing more than the inversion, it can be dropped entirely as well. Without this patch, 'koe,tx26d202vm0bwa' LVDS pane

Re: [PATCH v3 00/15] Canaan devicetree fixes

On Fri, Jul 01, 2022 at 06:16:14AM +0900, Damien Le Moal wrote: > On 7/1/22 02:53, Sudeep Holla wrote: > > On Thu, Jun 30, 2022 at 04:28:26PM +, Niklas Cassel wrote: > >> On Wed, Jun 29, 2022 at 07:43:29PM +0100, Conor Dooley wrote: > >>> From: Conor Dooley > >>> > >>> Hey all, > >>> This seri

[PATCH V2 0/5] I2S driver changes for Jadeite platform

Jadeite(JD) platform is Stoney APU varaint which uses I2S MICSP instance and ES8336 Codec. This patch series creates I2S platform devices for JD platform, adds I2S MICSP instance support and Machine driver support This patch set depends on: --checkpatch warnings patch --https://pa

[PATCH V2 1/5] drm/amdgpu: add dmi check for jadeite platform

DMI check is required to distinguish Jadeite platform from Stoney base variant. Add DMI check logic for Jadeite platform. Signed-off-by: Vijendar Mukunda Acked-by: Alex Deucher --- drivers/gpu/drm/amd/amdgpu/amdgpu_acp.c | 36 + 1 file changed, 36 insertions(+) diff --g

[PATCH V2 2/5] drm/amdgpu: create I2S platform devices for Jadeite platform

Jadeite platform uses I2S MICSP instance. Create platform devices for DMA controller and I2S controller for Jadeite platform. Signed-off-by: Vijendar Mukunda Acked-by: Alex Deucher --- drivers/gpu/drm/amd/amdgpu/amdgpu_acp.c | 293 +++- 1 file changed, 184 insertions(+), 109

[PATCH V2 3/5] ASoC: amd: add I2S MICSP instance support

Add I2S MICSP instance support for Stoney variant. Signed-off-by: Vijendar Mukunda --- sound/soc/amd/acp-pcm-dma.c | 50 +++-- sound/soc/amd/acp.h | 13 ++ 2 files changed, 61 insertions(+), 2 deletions(-) diff --git a/sound/soc/amd/acp-pcm-dma.c

[PATCH V2 4/5] ASoC: amd: add Machine driver for Jadeite platform

Add Machine driver for Jadeite platform which uses ES8336 codec. Signed-off-by: Vijendar Mukunda --- sound/soc/amd/acp-es8336.c | 324 + 1 file changed, 324 insertions(+) create mode 100644 sound/soc/amd/acp-es8336.c diff --git a/sound/soc/amd/acp-es8336.c b

[PATCH V2 5/5] ASoC: amd: enable machine driver build for Jadeite platform

Enable machine driver build for Jadeite platform using ES8336 Codec. Signed-off-by: Vijendar Mukunda --- sound/soc/amd/Kconfig | 13 + sound/soc/amd/Makefile | 2 ++ 2 files changed, 15 insertions(+) diff --git a/sound/soc/amd/Kconfig b/sound/soc/amd/Kconfig index 1381aec23048..c3

Re: [PATCH V2 0/5] I2S driver changes for Jadeite platform

On Fri, Jul 01, 2022 at 05:11:02PM +0530, Vijendar Mukunda wrote: > This patch set depends on: > --checkpatch warnings patch > > --https://patchwork.kernel.org/project/alsa-devel/patch/20220627125834.481731-1-vijendar.muku...@amd.com/ That's "drm: amd: amdgpu: fix checkpatch warnin

[PATCH 0/2] drm: A couple of fixes for drm_copy_field() helper function

Hello, Peter Robinson reported me a kernel bug in one of his aarch64 test boards and even though I was not able to reproduce it, I think that figured out what the problem was. It seems the cause is that a DRM driver doesn't set some of the struct drm fields copied to userspace via DRM_IOCTL_VERSIO

[PATCH 2/2] drm: Prevent drm_copy_field() to attempt copying a NULL pointer

The drm_copy_field() helper is used to copy some struct drm_driver fields to userspace through the DRM_IOCTL_VERSION ioctl. But it could be possible that the driver didn't set some of the fields and are instead set to NULL. If that is the case, the drm_copy_field() attempts to copy a NULL pointer:

[PATCH 1/2] drm: Use size_t type for len variable in drm_copy_field()

The strlen() function returns a size_t which is an unsigned int on 32-bit arches and an unsigned long on 64-bit arches. But in the drm_copy_field() function, the strlen() return value is assigned to an 'int len' variable. Later, the len variable is passed as copy_from_user() third argument that is

Re: [PATCH V2 0/5] I2S driver changes for Jadeite platform

On 7/1/22 5:21 PM, Mark Brown wrote: > On Fri, Jul 01, 2022 at 05:11:02PM +0530, Vijendar Mukunda wrote: > >> This patch set depends on: >> --checkpatch warnings patch >> >> --https://patchwork.kernel.org/project/alsa-devel/patch/20220627125834.481731-1-vijendar.muku...@amd.com/ > >

Re: [PATCH v4 1/2] drm/i915/edid: convert DP, HDMI and LVDS to drm_edid

On Fri, Jul 01, 2022 at 11:55:38AM +0300, Jani Nikula wrote: > Convert all the connectors that use cached connector edid and > detect_edid to drm_edid. > > Since drm_get_edid() calls drm_connector_update_edid_property() while > drm_edid_read*() do not, we need to call drm_edid_connector_update() >

Re: [PATCH 4/5] fbmem: Prevent invalid virtual screen sizes in fb_set_var()

Hi Helge, On Thu, Jun 30, 2022 at 9:38 PM Geert Uytterhoeven wrote: > On Thu, Jun 30, 2022 at 9:17 PM Helge Deller wrote: > > On 6/30/22 21:11, Geert Uytterhoeven wrote: > > > On Wed, Jun 29, 2022 at 10:00 PM Helge Deller wrote: > > >> Prevent that drivers configure a virtual screen resolution

Re: [PATCH 2/5] fbcon: Fix up user-provided virtual screen size

Hi Helge, On Fri, Jul 1, 2022 at 11:30 AM Helge Deller wrote: > On 7/1/22 09:28, Geert Uytterhoeven wrote: > > On Thu, Jun 30, 2022 at 10:10 PM Helge Deller wrote: > >> On 6/30/22 22:00, Geert Uytterhoeven wrote: > >>> On Thu, Jun 30, 2022 at 9:46 PM Helge Deller wrote: > On 6/30/22 21:36,

[PATCH 2/2] drm/i915: DG2 and ATS-M device ID updates

Small BAR support has now landed, which allows us to add the PCI IDs that correspond to add-in card designs of DG2 and ATS-M. There's also one additional MB-down PCI ID that recently appeared (0x5698) so we add it too. Cc: Lucas De Marchi Signed-off-by: Matt Roper --- drivers/gpu/drm/i915/i915

[PATCH 1/2] Revert "topic/core-for-CI: Add remaining DG2 and ATS-M device IDs"

This reverts commit f7d7dddaab81eeae4508197b5f38f0b974d97b8c. In reality we'll just rebase this patch out of the topic/core-for-CI branch after landing the "real" copy in drm-intel. But to prevent pre-merge CI from getting confused, we send it as an explicit revert on the mailing list. Cc: Lucas

Re: [PATCH 2/2] drm/i915: DG2 and ATS-M device ID updates

On Fri, Jul 01, 2022 at 08:22:31AM -0700, Matt Roper wrote: Small BAR support has now landed, which allows us to add the PCI IDs that correspond to add-in card designs of DG2 and ATS-M. There's also one additional MB-down PCI ID that recently appeared (0x5698) so we add it too. Cc: Lucas De Mar

Re: [Intel-gfx] [PATCH 1/2] Revert "topic/core-for-CI: Add remaining DG2 and ATS-M device IDs"

On Fri, Jul 01, 2022 at 08:22:30AM -0700, Matt Roper wrote: This reverts commit f7d7dddaab81eeae4508197b5f38f0b974d97b8c. In reality we'll just rebase this patch out of the topic/core-for-CI branch after landing the "real" copy in drm-intel. But to prevent pre-merge CI from getting confused, we

Re: [PATCH v3 1/4] dt-bindings: display: panel-common: allow for additional port node properties

On Tue, Jun 28, 2022 at 08:18:35PM +0200, Max Krummenacher wrote: > From: Max Krummenacher > > Allow bindings which reference panel-common.yaml to add additional > properties under the port node. > I.e. 'panel-dpi' needs to add a new property to 'port/endpoint'. > > Signed-off-by: Max Krummenach

Re: [PATCH 0/2] drm: A couple of fixes for drm_copy_field() helper function

On Fri, Jul 1, 2022 at 1:08 PM Javier Martinez Canillas wrote: > > Hello, > > Peter Robinson reported me a kernel bug in one of his aarch64 test boards > and even though I was not able to reproduce it, I think that figured out > what the problem was. It seems the cause is that a DRM driver doesn't

[Bug 216198] New: uvd page faults on Radeon

https://bugzilla.kernel.org/show_bug.cgi?id=216198 Bug ID: 216198 Summary: uvd page faults on Radeon Product: Drivers Version: 2.5 Kernel Version: 5.15 Hardware: AMD OS: Linux Tree: Mainline Status

[PATCH 01/10] drm/amdgpu: use idr_init_base() to initialize mgr->ctx_handles

From: Danilo Krummrich idr_init_base(), implemented by commit 6ce711f27500 ("idr: Make 1-based IDRs more efficient"), let us set an arbitrary base other than idr_init(), which uses base 0. Since, for this IDR, no ID < 1 is ever requested, using idr_init_base(&idr, 1) avoids unnecessary tree walk

[PATCH 00/10] drm: use idr_init_base() over idr_init() if applicable

From: Danilo Krummrich This patch series initializes IDRs with idr_init_base(&idr, 1) rather than idr_init(&idr) in case for the particular IDR no IDs < 1 are ever requested - this avoids unnecessary tree walks. Danilo Krummrich (10): drm/amdgpu: use idr_init_base() to initialize mgr->ctx_hand

[PATCH 03/10] drm: use idr_init_base() to initialize master->magic_map

From: Danilo Krummrich idr_init_base(), implemented by commit 6ce711f27500 ("idr: Make 1-based IDRs more efficient"), let us set an arbitrary base other than idr_init(), which uses base 0. Since, for this IDR, no ID < 1 is ever requested/allocated, using idr_init_base(&idr, 1) avoids unnecessary

[PATCH 04/10] drm: use idr_init_base() to initialize master->lessee_idr

From: Danilo Krummrich idr_init_base(), implemented by commit 6ce711f27500 ("idr: Make 1-based IDRs more efficient"), let us set an arbitrary base other than idr_init(), which uses base 0. Since, for this IDR, no ID < 1 is ever requested/allocated, using idr_init_base(&idr, 1) avoids unnecessary

[PATCH 02/10] drm/amdgpu: use idr_init_base() to initialize fpriv->bo_list_handles

From: Danilo Krummrich idr_init_base(), implemented by commit 6ce711f27500 ("idr: Make 1-based IDRs more efficient"), let us set an arbitrary base other than idr_init(), which uses base 0. Since, for this IDR, no ID < 1 is ever requested/allocated, using idr_init_base(&idr, 1) avoids unnecessary

[PATCH 06/10] drm: use idr_init_base() to initialize mode_config.tile_idr

From: Danilo Krummrich idr_init_base(), implemented by commit 6ce711f27500 ("idr: Make 1-based IDRs more efficient"), let us set an arbitrary base other than idr_init(), which uses base 0. Since, for this IDR, no ID < 1 is ever requested/allocated, using idr_init_base(&idr, 1) avoids unnecessary

[PATCH 05/10] drm: use idr_init_base() to initialize mode_config.object_idr

From: Danilo Krummrich idr_init_base(), implemented by commit 6ce711f27500 ("idr: Make 1-based IDRs more efficient"), let us set an arbitrary base other than idr_init(), which uses base 0. Since, for this IDR, no ID < 1 is ever requested/allocated, using idr_init_base(&idr, 1) avoids unnecessary

[PATCH 07/10] drm/sis: use idr_init_base() to initialize dev_priv->object_idr

From: Danilo Krummrich idr_init_base(), implemented by commit 6ce711f27500 ("idr: Make 1-based IDRs more efficient"), let us set an arbitrary base other than idr_init(), which uses base 0. Since, for this IDR, no ID < 1 is ever requested/allocated, using idr_init_base(&idr, 1) avoids unnecessary

[PATCH 08/10] drm/v3d: use idr_init_base() to initialize v3d_priv->perfmon.idr

From: Danilo Krummrich idr_init_base(), implemented by commit 6ce711f27500 ("idr: Make 1-based IDRs more efficient"), let us set an arbitrary base other than idr_init(), which uses base 0. Since, for this IDR, no ID < 1 is ever requested/allocated, using idr_init_base(&idr, 1) avoids unnecessary

[PATCH 09/10] drm/via: use idr_init_base() to initialize dev_priv->object_idr

From: Danilo Krummrich idr_init_base(), implemented by commit 6ce711f27500 ("idr: Make 1-based IDRs more efficient"), let us set an arbitrary base other than idr_init(), which uses base 0. Since, for this IDR, no ID < 1 is ever requested/allocated, using idr_init_base(&idr, 1) avoids unnecessary

[PATCH 10/10] drm/todo: remove task for idr_init_base()

From: Danilo Krummrich All IDRs in the DRM core and drivers which are applicable for using idr_init_base() over idr_init() should be set up to use a proper base in order to avoid unnecessary tree walks. Signed-off-by: Danilo Krummrich --- Documentation/gpu/todo.rst | 12 1 file ch

[PATCH v4 00/14] Canaan devicetree fixes

From: Conor Dooley Hey all, This series should rid us of dtbs_check errors for the RISC-V Canaan k210 based boards. To make keeping it that way a little easier, I changed the Canaan devicetree Makefile so that it would build all of the devicetrees in the directory if SOC_CANAAN. I *DO NOT* have

[PATCH v4 01/14] dt-bindings: display: convert ilitek, ili9341.txt to dt-schema

From: Conor Dooley A dt-schema binding for the Ilitek ili9341 was created as panel/ilitek,ili9341.yaml but the txt binding was ignored in the process. Move the remaining items in the txt binding to the yaml one & delete it. The example in the txt binding has a spi-max-frequency which disagrees w

[PATCH v4 02/14] dt-bindings: display: ili9341: document canaan kd233's lcd

From: Conor Dooley The Canaan KD233 development board has a built in LCD. Add a specific compatible for it. Signed-off-by: Conor Dooley --- .../devicetree/bindings/display/panel/ilitek,ili9341.yaml| 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/di

[PATCH v4 03/14] ASoC: dt-bindings: convert designware-i2s to dt-schema

From: Conor Dooley Convert the Synopsys DesignWare I2S controller binding to dt-schema. There was no listed maintainer but Jose Abreu was the last editor of the txt binding so add him as maintainer. Signed-off-by: Conor Dooley --- .../bindings/sound/designware-i2s.txt | 35 --- ...

[PATCH v4 04/14] dt-bindings: dma: dw-axi-dmac: extend the number of interrupts

From: Conor Dooley The Canaan k210 apparently has a Sysnopsys Designware AXI DMA controller, but according to the documentation & devicetree it has 6 interrupts rather than the standard one. Support the 6 interrupt configuration by unconditionally extending the binding to a maximum of 8 per-chann

[PATCH v4 05/14] dt-bindings: memory-controllers: add canaan k210 sram controller

From: Conor Dooley The k210 U-Boot port has been using the clocks defined in the devicetree to bring up the board's SRAM, but this violates the dt-schema. As such, move the clocks to a dedicated node with the same compatible string & document it. Signed-off-by: Conor Dooley --- .../memory-cont

[PATCH v4 06/14] riscv: dts: canaan: fix the k210's memory node

From: Conor Dooley The k210 U-Boot port has been using the clocks defined in the devicetree to bring up the board's SRAM, but this violates the dt-schema. As such, move the clocks to a dedicated node with the same compatible string. The regs property does not fit in either node, so is replaced by

[PATCH v4 07/14] riscv: dts: canaan: fix the k210's timer nodes

From: Conor Dooley The timers on the k210 have non standard interrupt configurations, which leads to dtbs_check warnings: k210_generic.dtb: timer@502d: interrupts: [[14], [15]] is too long >From schema: Documentation/devicetree/bindings/timer/snps,dw-apb-timer.yaml Split the timer nodes in

[PATCH v4 08/14] riscv: dts: canaan: fix mmc node names

From: Conor Dooley The newly-converted-to-dt-schema binding expects the mmc node name to be '^mmc(@.*)?$' so align the devicetree with the schema. Tested-by: Niklas Cassel Signed-off-by: Conor Dooley --- arch/riscv/boot/dts/canaan/canaan_kd233.dts | 2 +- arch/riscv/boot/dts/canaan/sipeed

[PATCH v4 09/14] riscv: dts: canaan: fix kd233 display spi frequency

From: Conor Dooley The binding for the ili9341 specifies a const spi-max-frequency of 10 MHz but the kd233 devicetree entry has it listed at 15 Mhz. Align the devicetree with the value in the binding. Signed-off-by: Conor Dooley --- arch/riscv/boot/dts/canaan/canaan_kd233.dts | 2 +- 1 file ch

[PATCH v4 10/14] riscv: dts: canaan: use custom compatible for k210 i2s

From: Conor Dooley The devicetrees using the Canaan k210 all have a sound-dai-cells value of 1, whereas the standard binding example for the DesignWare i2s and other use cases suggest 0. Use a k210 specific compatible which supports this difference. Signed-off-by: Conor Dooley --- arch/riscv/b

[PATCH v4 11/14] riscv: dts: canaan: remove spi-max-frequency from controllers

From: Conor Dooley spi-max-frequency is a device, not a controller property and should be removed. Link: https://lore.kernel.org/lkml/20220526014141.2872567-1-r...@kernel.org/ Tested-by: Niklas Cassel Signed-off-by: Conor Dooley --- arch/riscv/boot/dts/canaan/k210.dtsi | 5 + 1 file chan

[PATCH v4 12/14] riscv: dts: canaan: fix bus {ranges,reg} warnings

From: Conor Dooley The k210 devicetrees warn about missing/empty reg and/or ranges properties: arch/riscv/boot/dts/canaan/k210.dtsi:408.22-460.5: Warning (unit_address_vs_reg): /soc/bus@5200: node has a unit name, but no reg or ranges property arch/riscv/boot/dts/canaan/k210.dtsi:352.22-406

[PATCH v4 13/14] riscv: dts: canaan: add specific compatible for kd233's LCD

From: Conor Dooley Add the recently introduced compatible for the LCD on the Canaan KD233. Signed-off-by: Conor Dooley --- arch/riscv/boot/dts/canaan/canaan_kd233.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/riscv/boot/dts/canaan/canaan_kd233.dts b/arch/riscv/b

[PATCH v4 14/14] riscv: dts: canaan: build all devicetress if SOC_CANAAN

From: Conor Dooley Testing & checking the Canaan devicetrees is inconvenient as only the devicetree corresponding to SOC_CANAAN_K210_DTB_BUILTIN will be built. Change the Makefile so that all devicetrees are built by default if SOC_CANAAN but only the one specified by SOC_CANAAN_K210_DTB_BUILTIN

Re: [PATCH v3 02/15] dt-bindings: display: ili9341: document canaan kd233's lcd

On Wed, 29 Jun 2022 19:43:31 +0100, Conor Dooley wrote: > From: Conor Dooley > > The Canaan KD233 development board has a built in LCD. > Add a specific compatible for it. > > Signed-off-by: Conor Dooley > --- > .../devicetree/bindings/display/panel/ilitek,ili9341.yaml| 1 + > 1 file c

Re: [PATCH v3 03/15] ASoC: dt-bindings: convert designware-i2s to dt-schema

On Wed, 29 Jun 2022 19:43:32 +0100, Conor Dooley wrote: > From: Conor Dooley > > Convert the Synopsys DesignWare I2S controller binding to dt-schema. > There was no listed maintainer but Jose Abreu was the last editor of the > txt binding so add him as maintainer. > > Signed-off-by: Conor Dooley

Re: [PATCH v3 05/15] dt-bindings: dma: dw-axi-dmac: extend the number of interrupts

On Thu, Jun 30, 2022 at 11:12:53PM +, conor.doo...@microchip.com wrote: > On 30/06/2022 22:55, Serge Semin wrote: > > EXTERNAL EMAIL: Do not click links or open attachments unless you know the > > content is safe > > > > On Wed, Jun 29, 2022 at 07:43:34PM +0100, Conor Dooley wrote: > >> From:

Re: [PATCH 1/7] dt-bindings: msm: dsi: Fix phy-name binding

On Thu, Jun 30, 2022 at 08:59:03PM +0200, Krzysztof Kozlowski wrote: > On 30/06/2022 14:08, Bryan O'Donoghue wrote: > > The driver doesn't care about the name of the phy in DTS. msm8916 has since > > 2016 named the phy "dsi-phy" with later SoCs taking the name "dsi". > > > > There's no reason to h

Re: [PATCH v2 09/15] drm/fbconv: Mode-setting pipeline enable / disable

Hi Thomas, On Mon, May 30, 2022 at 10:34 AM Geert Uytterhoeven wrote: > On Mon, May 30, 2022 at 9:47 AM Thomas Zimmermann wrote: > > Am 28.05.22 um 22:17 schrieb Geert Uytterhoeven: > > > On Mon, Oct 14, 2019 at 4:05 PM Thomas Zimmermann > > > wrote: > > >> The display mode is set by convertin

Re: [PATCH 1/7] dt-bindings: msm: dsi: Fix phy-name binding

On Thu, Jun 30, 2022 at 01:08:39PM +0100, Bryan O'Donoghue wrote: > The driver doesn't care about the name of the phy in DTS. msm8916 has since > 2016 named the phy "dsi-phy" with later SoCs taking the name "dsi". Also, for the subject, it's 'phy-names' not 'phy-name'. > There's no reason to have

  1   2   >