Do not keep the obsolete EDID around after unplugging the display
form the connector.
Signed-off-by: Thomas Zimmermann
Fixes: 2a2391f857cd ("drm/ast: vga: Transparently handle BMC support")
Cc: Thomas Zimmermann
Cc: Jocelyn Falempe
Cc: Dave Airlie
Cc: dri-devel@lists.freedesktop.org
---
drive
Set bmc_attached for the VGA connector on servers and let DRM's
probe helpers track the physical and logical connector state. Remove
similar logic from mgag200.
Also resolve a design issue, where mgag200 uses the connector's
edid_blob_ptr. It is an internal value that drivers should not access
dir
Set bmc_attached for all connectors and let DRM's probe helpers
track the physical and logical connector state. Remove such logic
and related data structures from ast.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/ast/ast_dp.c | 21 ++---
drivers/gpu/drm/ast/ast_dp501.
Add the bmc_attached flag to struct drm_connector to signal the
presence of a virtual BMC output. The connector reports to be in
status connected even without a physically connected display. Fbcon
or userspace compositors would otherwise stop displaying to the
BMC.
Signed-off-by: Thomas Zimmermann
Move the logic to call the connector's detect helper into a single
internal function. Reduces code duplication.
Signed-off-by: Thomas Zimmermann
Acked-by: Maxime Ripard
---
drivers/gpu/drm/drm_probe_helper.c | 33 +++---
1 file changed, 17 insertions(+), 16 deletions(-)
Do not keep the obsolete EDID around after unplugging the display
form the connector.
Signed-off-by: Thomas Zimmermann
Fixes: d20c2f846428 ("drm/ast: sil164: Transparently handle BMC support")
Cc: Thomas Zimmermann
Cc: Jocelyn Falempe
Cc: Dave Airlie
Cc: dri-devel@lists.freedesktop.org
---
dr
Track the connector's physical status in addition to its logical
status. The latter is directly derived from the former and for most
connectors both values are in sync.
Server chips with BMC, such as Aspeed, Matrox and HiSilicon, often
provide virtual outputs for remote management. Without a conne
Track a connector's physical status separately from the logical status
and implement BMC support for DRM drivers. Connectors with virtual BMC
stay connected even if no display is physically connected. DRM clients
then continue displaying output to the BMC.
Ast and mgag200 have been doing this for
On Fri, 11 Oct 2024 at 09:54, Jun Nie wrote:
>
> Dmitry Baryshkov 于2024年10月10日周四 21:21写道：
> >
> > On Wed, Oct 09, 2024 at 04:50:24PM GMT, Jun Nie wrote:
> > > Share SSPP info for multi-rect case if virtual plane is not enabled.
> > > Otherwise, the 2nd half of DMA content is not displayed due to
Dmitry Baryshkov 于2024年10月10日周四 21:21写道：
>
> On Wed, Oct 09, 2024 at 04:50:24PM GMT, Jun Nie wrote:
> > Share SSPP info for multi-rect case if virtual plane is not enabled.
> > Otherwise, the 2nd half of DMA content is not displayed due to sspp
> > pointer of r_pipe is null.
>
> Fixes?
Yeah. It i
On 10/11/2024, Marek Vasut wrote:
> On 10/10/24 9:15 AM, Liu Ying wrote:
>> On 10/09/2024, Marek Vasut wrote:
>>> The LDB serializer clock operate at either x7 or x14 rate of the input
>>
>> Isn't it either x7 or 3.5x?
>
> Is it 3.5 for the dual-link LVDS ?
Yes.
static unsigned long fsl_ldb_link
Dmitry Baryshkov 于2024年10月10日周四 21:08写道：
>
> On Wed, Oct 09, 2024 at 04:50:18PM GMT, Jun Nie wrote:
> > Store pipes in array with removing dedicated r_pipe. There are
> > 2 pipes in a drm plane at most currently. While 4 pipes are
> > needed for new usage case. This change generalize the handling
Dmitry Baryshkov 于2024年10月10日周四 21:15写道：
>
> On Wed, Oct 09, 2024 at 04:50:22PM GMT, Jun Nie wrote:
> > Blend pipes by set of mixer pair config. The first 2 pipes are for left
> > half screen with the first set of mixer pair config. And the later 2 pipes
> > are for right in quad pipe case.
> >
>
Dmitry Baryshkov 于2024年10月10日周四 21:12写道：
>
> On Wed, Oct 09, 2024 at 04:50:21PM GMT, Jun Nie wrote:
> > Update mixer number info earlier so that the plane nopipe check
> > can have the info to clip the plane. Otherwise, the first nonpipe
> > check will have mixer number as 0 and plane is not check
From: "jesse.zh...@amd.com"
Added ring id schedule to switch scheduling policy when cs submits.
Schedule the ring by setting the ring id.
Signed-off-by: Jesse Zhang
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 +
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 9 +++--
drivers/gpu/drm/amd/amd
From: "jesse.zh...@amd.com"
Added ring ID scheduling.
In some cases, userspace needs to run a job on a specific ring.
Instead of selecting the best ring to run based on the ring score.
For example, The user want to run a bad job on a specific ring to check
whether the ring can recover from a queu
On 10/11/2024, Marek Vasut wrote:
> On 10/10/24 7:22 AM, Liu Ying wrote:
>> On 10/09/2024, Marek Vasut wrote:
>>> The media_ldb_root_clk supply LDB serializer. These clock are usually
>>> shared with the LCDIFv3 pixel clock and supplied by the Video PLL on
>>> i.MX8MP, but the LDB clock run at eith
On Tue, Oct 08, 2024 at 02:39:45PM +0200, Niklas Schnelle wrote:
> In a future patch HAS_IOPORT=n will disable inb()/outb() and friends at
> compile time. We thus need to add HAS_IOPORT as dependency for those
> drivers using them unconditionally. Some 8250 serial drivers support
> MMIO only use, s
Hi all,
On Tue, 1 Oct 2024 13:43:31 +1000 Stephen Rothwell
wrote:
>
> After merging the drm-intel tree, today's linux-next build (htmldocs)
> produced this warning:
>
> drivers/gpu/drm/i915/i915_irq.c:1: warning:
> 'intel_runtime_pm_disable_interrupts' not found
> drivers/gpu/drm/i915/i915_irq
On 10/10/24 9:15 AM, Liu Ying wrote:
On 10/09/2024, Marek Vasut wrote:
The LDB serializer clock operate at either x7 or x14 rate of the input
Isn't it either x7 or 3.5x?
Is it 3.5 for the dual-link LVDS ?
I don't have such a panel right now to test.
[...]
diff --git a/drivers/gpu/drm/brid
On 10/10/24 7:22 AM, Liu Ying wrote:
On 10/09/2024, Marek Vasut wrote:
The media_ldb_root_clk supply LDB serializer. These clock are usually
shared with the LCDIFv3 pixel clock and supplied by the Video PLL on
i.MX8MP, but the LDB clock run at either x7 or x14 rate of the LCDIFv3
pixel clock. Al
On Thu, 10 Oct 2024 11:42:39 -0400, Frank Li wrote:
> Convert device tree binding doc zii,rave-sp-backlight.txt to yaml format.
> Additional Changes:
> - Remove mfd parent node at example.
> - Ref to backlight's common.yaml
>
> Signed-off-by: Frank Li
> ---
> .../leds/backlight/zii,rave-sp-bac
Hi Dave and Simona,
A few drm-xe fixes for 6.12-rc3.
thanks
Lucas De Marchi
drm-xe-fixes-2024-10-10:
Driver Changes:
- Fix error checking with xa_store() (Matthe Auld)
- Fix missing freq restore on GSC load error (Vinay)
- Fix wedged_mode file permission (Matt Roper)
- Fix use-after-free in ct
On Mon, Oct 7, 2024 at 7:52 AM Thorsten Blum wrote:
>
> Since kvfree() already checks if its argument is NULL, an additional
> check before calling kvfree() is unnecessary and can be removed.
>
> Remove both and the following Coccinelle/coccicheck warnings reported by
> ifnullfree.cocci:
>
> WAR
mentation/devicetree/bindings/leds/backlight/zii,rave-sp-backlight.yaml:
Documentation/devicetree/bindings/mfd/zii,rave-sp.yaml
See
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20241010-zii_yaml-v2-2-0ab730607...@nxp.com
The base for the series is generally the latest rc1. A diffe
On 10/11/2024, Marek Vasut wrote:
> On 10/10/24 7:31 AM, Liu Ying wrote:
>
> Hi,
Hi,
>
>>> This Video PLL1 configuration since moved to &media_blk_ctrl {} , but it is
>>> still in the imx8mp.dtsi . Therefore, to make your panel work at the
>>> correct desired pixel clock frequency instead of
On 10/11/2024 12:05 AM, Dan Carpenter wrote:
> The >= ARRAY_SIZE() should be > ARRAY_SIZE() to prevent an out of
> bounds read.
>
> Fixes: 012be6f22c01 ("drm/amdgpu: Add sysfs interfaces for NPS mode")
> Signed-off-by: Dan Carpenter
Reviewed-by: Lijo Lazar
Thanks,
Lijo
> ---
> drivers/gpu
On Thu, Oct 10, 2024 at 12:05:38PM -0700, Mina Almasry wrote:
> On Thu, Oct 10, 2024 at 4:17 AM Lai, Yi wrote:
> >
> > Hi Mina Almasry,
> >
> > Greetings!
> >
> > I used Syzkaller and found that there is BUG: soft lockup inqt in
> > linux-next tree next-20241008
> >
> > After bisection and the fi
The current panel brightness is only 360 nit. Adjust the power and gamma to
optimize the panel brightness. The brightness after adjustment is 390 nit.
Fixes: 3179338750d8 ("drm/panel: Support for IVO t109nw41 MIPI-DSI panel")
Signed-off-by: Cong Yang
---
drivers/gpu/drm/panel/panel-himax-hx83102
This initial part of the panel driver was mostly generated by the
"linux-mdss-dsi-panel-driver-generator" tool [1], reading downstream
Android kernel file "dsi_panel_S6E88A0_AMS427AP24_qhd_octa_video.dtsi" [2].
On top of the generic output of the tool, there were a couple of changes
applied:
- Add
Add bindings for Samsung AMS427AP24 panel with S6E88A0 controller.
Signed-off-by: Jakob Hauser
---
Patch is based on https://gitlab.freedesktop.org/drm/misc/kernel.git
current branch drm-misc-next.
---
.../panel/samsung,s6e88a0-ams427ap24.yaml | 68 +++
1 file changed, 68 ins
The tables for brightness to candela, aid and elvss were taken from downstream
kernel file "dsi_panel_S6E88A0_AMS427AP24_qhd_octa_video.dtsi" [1][2][3].
The gamma table gets generated in "ss_dsi_smart_dimming_S6E88A0_AMS427AP24.c"
[4]
with hard-coded starting values. The function smart_dimming_in
The patchset adds a new driver for Samsung AMS427AP24 panel with S6E88A0
controller. Patches are based on current branch drm-misc-next.
Jakob Hauser (4):
dt-bindings: display: panel: Add Samsung S6E88A0-AMS427AP24 bindings
drm/panel: samsung-s6e88a0-ams427ap24: Add initial driver
drm/panel:
The way of implementing a flip option follows the existing
panel-samsung-s6e8aa0.c [1][2][3].
The value to flip the screen is taken from a downstream kernel file of
a similar but older panel [4]. The mipi clock [5] for the new panel
samsung-s6e88a0-ams427ap24 matches 461 MHz and a hardware read-ou
Use the more robust approach provided by the __free() macro to
automatically call of_node_put() when the device node goes out of scope.
Signed-off-by: Javier Carrasco
---
drivers/gpu/drm/logicvc/logicvc_layer.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/driver
Use the scoped variant of the macro to avoid leaking memory upon early
exits without the required call to of_node_put().
Signed-off-by: Javier Carrasco
---
drivers/gpu/drm/logicvc/logicvc_layer.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/logicvc/logic
Early exits from the for_each_child_of_node() loop require explicit
calls to of_node_put() for the child node.
Add the missing 'of_node_put(layer_node)' in the only error path.
Cc: sta...@vger.kernel.org
Fixes: efeeaefe9be5 ("drm: Add support for the LogiCVC display controller")
Signed-off-by: Ja
() in for_each_child_of_node()
drm: logicvc: switch to for_each_child_of_node_scoped()
drm: logicvc: use automatic cleanup facility for layers_node
drivers/gpu/drm/logicvc/logicvc_layer.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
---
base-commit:
Quoting Dmitry Baryshkov (2024-09-19 03:40:19)
> On Sat, Aug 31, 2024 at 09:06:51PM GMT, Stephen Boyd wrote:
> > diff --git a/Documentation/devicetree/bindings/usb/usb-switch.yaml
> > b/Documentation/devicetree/bindings/usb/usb-switch.yaml
> > index f5dc7e23b134..816f295f322f 100644
> > --- a/Docu
On Thu, Oct 10, 2024 at 12:32:01PM +0200, Michał Winiarski wrote:
> Similar to regular resizable BAR, VF BAR can also be resized.
> The structures are very similar, which means we can reuse most of the
> implementation. See PCIe r4.0, sec 9.3.7.4.
Add blank line between paragraphs.
Add "()" after
On Thu, Oct 10, 2024 at 12:31:59PM +0200, Michał Winiarski wrote:
> Similar to regular resizable BAR, VF BAR can also be resized, e.g. by
> the system firmware, or the PCI subsystem itself.
> Add the capability ID and restore it as a part of IOV state.
> See PCIe r4.0, sec 9.3.7.4.
Add blank line
On Thu, Oct 10, 2024 at 12:32:00PM +0200, Michał Winiarski wrote:
> There are multiple places where special handling is required for IOV
> resources.
> Extract it to a helper and drop a few ifdefs.
Add blank line between paragraphs.
Include name of helper in subject line and commit log, i.e.,
pci
On Thu, Oct 10, 2024 at 12:32:02PM +0200, Michał Winiarski wrote:
> VF MMIO resource reservation, either created by system firmware and
> inherited by Linux PCI subsystem or created by the subsystem itself,
> contains enough space to fit the BAR of all SR-IOV Virtual Functions
> that can potentiall
Hi - how did you send this message? This patch comes out looking quite strange
on my machine, perhaps you don't have the encoding set to UTF-8 or aren't
using git send-email?
On Mon, 2024-09-23 at 22:18 +0200, Szőke Benjamin wrote:
> s=20181004; d=freemail.hu;
>
> h=Message-ID:Date:MI
From: "Dr. David Alan Gilbert"
Commit c2c2ce1e9623 ("drm/amd/display: Optimize passive update planes.")
removed the last caller of context_timing_trace.
Remove it.
With that gone, no one is now looking at the 'timing_trace' flag, remove
it and all the places that set it.
Signed-off-by: Dr. Davi
patch link:
https://lore.kernel.org/r/20241007-yuv-v12-13-01c1ada6fec8%40bootlin.com
patch subject: [PATCH v12 13/15] drm/vkms: Create KUnit tests for YUV
conversions
config: i386-randconfig-013-20241010
(https://download.01.org/0day-ci/archive/20241011/202410110407.ehvadsaf-...@intel.com/config
On Fri, Oct 4, 2024 at 4:50 PM Arnd Bergmann wrote:
>
> From: Arnd Bergmann
>
> The older version of the vmwgfx driver requires port I/O in order to work:
>
> In file included from arch/arm64/include/asm/io.h:298,
> from drivers/gpu/drm/vmwgfx/vmwgfx_kms.c:28:
> drivers/gpu/drm/v
On Wed, Oct 2, 2024 at 8:26 AM Nikolay Kuratov wrote:
>
> Currently if condition (!bo and !vmw_kms_srf_ok()) was met
> we go to err_out with ret == 0.
> err_out dereferences vfb if ret == 0, but in our case vfb is still NULL.
>
> Fix this by assigning sensible error to ret.
>
> Found by Linux Veri
On Tue, Oct 08, 2024 at 10:33:44PM +0300, Ville Syrjälä wrote:
> On Mon, Oct 07, 2024 at 09:36:13AM +0200, Thomas Zimmermann wrote:
> > Hi
> >
> > Am 03.10.24 um 13:33 schrieb Ville Syrjala:
> > > From: Ville Syrjälä
> > >
> > > drm_client_firmware_config() is currently picking up the current
> >
On Thu, Oct 10, 2024 at 4:17 AM Lai, Yi wrote:
>
> Hi Mina Almasry,
>
> Greetings!
>
> I used Syzkaller and found that there is BUG: soft lockup inqt in linux-next
> tree next-20241008
>
> After bisection and the first bad commit is:
> "
> 678f6e28b5f6 net: add SO_DEVMEM_DONTNEED setsockopt to re
The >= ARRAY_SIZE() should be > ARRAY_SIZE() to prevent an out of
bounds read.
Fixes: 012be6f22c01 ("drm/amdgpu: Add sysfs interfaces for NPS mode")
Signed-off-by: Dan Carpenter
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/driver
On Thu, 10 Oct 2024 11:42:42 -0400, Frank Li wrote:
> Convert device binding doc zii,rave-sp.txt to yaml format.
> Additional change:
> - ref to other zii yaml files.
> - remove rave-sp-hwmon and rave-sp-leds.
>
> Signed-off-by: Frank Li
> ---
> .../devicetree/bindings/mfd/zii,rave-sp.txt
On Thu, 10 Oct 2024 11:42:41 -0400, Frank Li wrote:
> Convert device binding doc zii,rave-sp-wdt.txt to yaml format.
> Additional changes:
> - Ref to watchdog.yaml.
> - Remove mfd node in example.
> - Remove eeprom part in example.
>
> Signed-off-by: Frank Li
> ---
> .../bindings/watchdog/zii,
On Thu, 10 Oct 2024 11:42:40 -0400, Frank Li wrote:
> Convert device tree binding doc zii,rave-sp-eeprom.txt to yaml format.
> Additional changes:
> - Add ref to nvme.yaml.
> - Add reg property.
> - Remove mfd at example.
>
> Signed-off-by: Frank Li
> ---
> .../bindings/nvmem/zii,rave-sp-eepro
On Thu, 10 Oct 2024 11:42:38 -0400, Frank Li wrote:
> Convert device tree binding doc zii,rave-sp-pwrbutton.txt to yaml format.
> Additional changes:
> - add ref to input.yaml.
> - remove mfd node in example.
>
> Signed-off-by: Frank Li
> ---
> .../bindings/input/zii,rave-sp-pwrbutton.txt
Apologies. The trace below isn't the first place where things went wrong. I dug
up the full serial log
and found some earlier mgag errors. Actual first one is:
[ OK ] Reached target Basic System.
[ 32.366479] fbcon: mgag200drmfb (fb0) is primary device
[ 32.405678] mpt2sas_cm0: sense pool(0
tion/devicetree/bindings/watchdog/zii,rave-sp-wdt.yaml:
Documentation/devicetree/bindings/mfd/zii,rave-sp.yaml
See
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20241010-zii_yaml-v2-4-0ab730607...@nxp.com
The base for the series is generally the latest rc1. A different dependency
shou
bindings/nvmem/zii,rave-sp-eeprom.yaml:
Documentation/devicetree/bindings/mfd/zii,rave-sp.yaml
See
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20241010-zii_yaml-v2-3-0ab730607...@nxp.com
The base for the series is generally the latest rc1. A different dependency
shou
i,rave-sp-pwrbutton.yaml:
Documentation/devicetree/bindings/mfd/zii,rave-sp.yaml
See
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20241010-zii_yaml-v2-1-0ab730607...@nxp.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* pat
The current VKMS driver uses non-managed function to create
writeback connectors. It is not an issue yet, but in order
to support multiple devices easily, convert this code to
use drm and device managed helpers.
Signed-off-by: Louis Chauvet
---
drivers/gpu/drm/vkms/vkms_writeback.c | 13 ++--
Currently drm_writeback_connector are created by
drm_writeback_connector_init or drm_writeback_connector_init_with_encoder.
Both of the function uses drm_connector_init and drm_encoder_init, but
there is no way to properly clean those structure from outside. By using
drm managed variants, we can en
The current VKMS driver uses managed function to create crtc, but
don't use it to properly clean the crtc workqueue. It is not an
issue yet, but in order to support multiple devices easily,
convert this code to use drm and device managed helpers.
Signed-off-by: Louis Chauvet
---
drivers/gpu/drm/
The current VKMS driver uses non-managed function to create encoders. It
is not an issue yet, but in order to support multiple devices easily,
convert this code to use drm and device managed helpers.
Signed-off-by: Louis Chauvet
---
drivers/gpu/drm/vkms/vkms_output.c | 14 --
1 file
The current VKMS driver uses non-managed function to create connectors. It
is not an issue yet, but in order to support multiple devices easily,
convert this code to use drm and device managed helpers.
Signed-off-by: Louis Chauvet
---
drivers/gpu/drm/vkms/vkms_output.c | 19 +++
m
[2]:https://lore.kernel.org/all/20241010-vkms-remove-index-v2-1-6b8d6cfd5...@bootlin.com/
For the drmm_writeback helpers, you can find some discussions here [3].
[3]:https://lore.kernel.org/all/20240906-writeback-drmm-v1-1-01ede3281...@bootlin.com/
Signed-off-by: Louis Chauvet
---
Changes
On 10/10/24 7:31 AM, Liu Ying wrote:
Hi,
This Video PLL1 configuration since moved to &media_blk_ctrl {} , but it is
still in the imx8mp.dtsi . Therefore, to make your panel work at the correct
desired pixel clock frequency instead of some random one inherited from
imx8mp.dtsi, add the follo
VKMS currently supports only one CRTC, so it make no sense to have this
index configurable. To avoid issues, replace this hardcoded index by
drm_crtc_mask when applicable.
There is no need to manually set a crtc mask on primary and cursor plane
as it is automatically set by drmm_crtc_alloc_with_pl
On Thu, 10 Oct 2024, Manikandan Muralidharan wrote:
> In sam9x7 SoC where XLCDC IP is used,add support to bypass the LCDC pixel
> clock divider when LCDC Generic clock is enabled.Used to match
> and drive the panel requested Pixel clock.
>
> Signed-off-by: Manikandan Muralidharan
> ---
> driver
> Thanks for testing. Here's another patch to try Ville's suggestion. It
> should disable HW vblank IRQs on your system. Could you please test it
> and report on the results?
Thomas,
Thanks for keeping working on this. Output is different, but still dies with
vblank problems.
[ OK ] Started
On Thu, 2024-10-10 at 16:54 +0100, Isaac Scott wrote:
To be clear, my reply applies to the patch referenced by [1]
Tested-by: Isaac Scott
> On Thu, 2024-10-10 at 13:31 +0800, Liu Ying wrote:
> > On 10/09/2024, Marek Vasut wrote:
> > > On 10/8/24 12:07 PM, Isaac Scott wrote:
> > > > On Mon, 2024
On Thu, 2024-10-10 at 13:31 +0800, Liu Ying wrote:
> On 10/09/2024, Marek Vasut wrote:
> > On 10/8/24 12:07 PM, Isaac Scott wrote:
> > > On Mon, 2024-10-07 at 20:06 +0200, Marek Vasut wrote:
> > > > On 10/7/24 7:01 PM, Isaac Scott wrote:
> > > > > Hi Marek,
> > > >
> > > > Hi,
> > > >
> > > > > O
Convert device binding doc zii,rave-sp.txt to yaml format.
Additional change:
- ref to other zii yaml files.
- remove rave-sp-hwmon and rave-sp-leds.
Signed-off-by: Frank Li
---
.../devicetree/bindings/mfd/zii,rave-sp.txt| 39 --
.../devicetree/bindings/mfd/zii,rave-sp.yaml
Convert device tree binding doc zii,rave-sp-eeprom.txt to yaml format.
Additional changes:
- Add ref to nvme.yaml.
- Add reg property.
- Remove mfd at example.
Signed-off-by: Frank Li
---
.../bindings/nvmem/zii,rave-sp-eeprom.txt | 40
.../bindings/nvmem/zii,rave-sp-eep
Convert device binding doc zii,rave-sp-wdt.txt to yaml format.
Additional changes:
- Ref to watchdog.yaml.
- Remove mfd node in example.
- Remove eeprom part in example.
Signed-off-by: Frank Li
---
.../bindings/watchdog/zii,rave-sp-wdt.txt | 39 --
.../bindings/watchdog/
Convert device tree binding doc zii,rave-sp-backlight.txt to yaml format.
Additional Changes:
- Remove mfd parent node at example.
- Ref to backlight's common.yaml
Signed-off-by: Frank Li
---
.../leds/backlight/zii,rave-sp-backlight.txt | 23 --
.../leds/backlight/zii,rave-sp-b
Fixed below warnings:
arch/arm64/boot/dts/freescale/imx8mq-zii-ultra-rmb3.dtb:
/soc@0/bus@3080/serial@3089/mcu: failed to match any schema with
compatible: ['zii,rave-sp-rdu2']
arch/arm64/boot/dts/freescale/imx8mq-zii-ultra-rmb3.dtb:
/soc@0/bus@3080/serial@3089/mcu/watchdog: fai
Convert device tree binding doc zii,rave-sp-pwrbutton.txt to yaml format.
Additional changes:
- add ref to input.yaml.
- remove mfd node in example.
Signed-off-by: Frank Li
---
.../bindings/input/zii,rave-sp-pwrbutton.txt | 22 -
.../bindings/input/zii,rave-sp-pwrbutton.yaml
Le 27/09/24 - 16:39, Lyude Paul a écrit :
> Currently, there's nothing actually stopping a driver from only registering
> vblank support for some of it's CRTCs and not for others. As far as I can
> tell, this isn't really defined behavior on the C side of things - as the
> documentation explicitly
On Thu, Oct 10, 2024 at 05:26:43PM GMT, Liu Ying wrote:
> drm_hdmi_avi_infoframe_from_display_mode() called from
> it66121_bridge_mode_set() already calls hdmi_avi_infoframe_init() to
> initialize an HDMI AVI infoframe. So, drop the redundant
> hdmi_avi_infoframe_init() function call from it66121_
On Wed, Oct 09, 2024 at 08:41:13PM GMT, Jessica Zhang wrote:
> Don't set the merge_3d pending flush bits if the mode_3d is
> BLEND_3D_NONE.
>
> Always flushing merge_3d can cause timeout issues when there are
> multiple commits with concurrent writeback enabled.
>
> This is because the video phys
On Mon, 30 Sep 2024, shiyongbang wrote:
From: baihan li
Add dp aux read/write functions. They are basic functions
and will be used later.
You're supposed to use struct drm_dp_aux, add a .transfer function,
initialize it with intel_dp_aux_init(), and register with
intel_dp_aux_register(). Then
Hi Baihan，
At 2024-10-01 15:26:23, "shiyongbang" wrote:
From: baihan li
Add dp aux read/write functions. They are basic functions
and will be used later.
Signed-off-by: baihan li
---
drivers/gpu/drm/hisilicon/hibmc/Makefile | 3 +-
drivers/gpu/drm/hisilicon/hibmc/dp/dp_aux.c | 227 +++
On Mon, 30 Sep 2024, shiyongbang wrote:
From: baihan li
Add link training process functions in this moduel.
Lots of duplication of drm_dp_helper.[ch] stuff here too. I'll mention a
few inline, but there's more.
BR,
Jani.
Ok. thanks.
Baihan Li.
On 10/10/2024 2:45 PM, Thomas Hellström wrote:
> Add a missing colon.
>
> Cc: dri-devel@lists.freedesktop.org
> Reported-by: Stephen Rothwell
> Closes:
> https://lore.kernel.org/linux-next/20241010160942.192ca...@canb.auug.org.au/
> Fixes: fc5d96670eb2 ("drm/ttm: Move swapped objects off the ma
On Wed, Oct 09, 2024 at 04:50:27PM GMT, Jun Nie wrote:
> Request 4 mixers and 4 DSC for the case that both dual-DSI and DSC are
> enabled. We prefer to use 4 pipes for dual DSI case for it is power optimal
> for DSC.
>
> Signed-off-by: Jun Nie
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c
On Wed, Oct 09, 2024 at 04:50:26PM GMT, Jun Nie wrote:
> Support SSPP assignment for quad-pipe case with unified method.
> The first 2 pipes can share a set of mixer config and enable
> multi-rect mode if condition is met. It is also the case for
> the later 2 pipes.
>
> Signed-off-by: Jun Nie
>
Hello,
Somewhere between 6.11-rc4 and 6.11-rc5 the following error message is displayed
when trying to initialize a nvc0_screen on the Tegra X1's GM20B:
[ 34.431210] nouveau 5700.gpu: pmu:hpq: timeout waiting for queue ready
[ 34.438145] nouveau 5700.gpu: gr: init failed, -110
nvc0_screen
Hi Dave, Sima,
here's drm-misc-fixes for this week.
Best regards
Thomas
drm-misc-fixes-2024-10-10:
Short summary of fixes pull:
fbdev-dma:
- Only clean up deferred I/O if instanciated
nouveau:
- dmem: Fix privileged error in copy engine channel; Fix possible
data leak in migrate_to_ram()
- gsp
Hi Dave & Maxime,
On 10/10/24 04:36, Maxime Ripard wrote:
On Wed, Oct 09, 2024 at 04:13:01PM GMT, Dave Stevenson wrote:
Hi Maíra
On Wed, 9 Oct 2024 at 15:12, Maíra Canal wrote:
VC4 has two relevant mailing list: kernel-l...@raspberrypi.com and
dri-devel@lists.freedesktop.org. Therefore, lis
Am 10.10.24 um 13:22 schrieb Colin Ian King:
The left shift of int 32 bit integer constant 1 is evaluated using 32 bit
arithmetic and then assigned to and operated upon using a 64 bit unsigned
integer. In the case where the shift is 32 or more this can lead to an
overflow. Avoid this by shifting
On Wed, Oct 09, 2024 at 04:50:25PM GMT, Jun Nie wrote:
> Clip plane into pipes per left and right half screen ROI if topology
> is quad pipe.
Why? Please provide an explanation for the reviewers not knowing the
details.
> Then split the clipped rectangle by half if the rectangle
> width still exc
On Wed, Oct 09, 2024 at 04:50:24PM GMT, Jun Nie wrote:
> Share SSPP info for multi-rect case if virtual plane is not enabled.
> Otherwise, the 2nd half of DMA content is not displayed due to sspp
> pointer of r_pipe is null.
Fixes?
>
> Signed-off-by: Jun Nie
> ---
> drivers/gpu/drm/msm/disp/dp
1 - 100 of 149 matches
Mail list logo
