This is a reminder that the membership renewal period ends in 2 days,
and elections will start after that. Please register as an X.Org
Foundation member to be able to vote in the upcoming elections. Thanks!
-Ricardo Garcia, on behalf of the X.Org elections committee.
On Tue, 2024-03-26 at 11:42
Output Resource (dcb->or) value is not guaranteed to be non-zero (i.e.
in drivers/gpu/drm/nouveau/nouveau_bios.c, in 'fabricate_dcb_encoder_table()'
'dcb->or' is assigned value '0' in call to 'fabricate_dcb_output()').
Add check to validate 'dcb->or' before it's used.
Found by Linux Verification
This is an effort to get rid of all multiplications from allocation
functions in order to prevent integer overflows [1] [2].
In this case, the memory allocated to store RADEONFB_CONN_LIMIT pointers
to "drm_connector" structures can be avoided. This is because this
memory area is never accessed.
virtio core already sets the .owner, so driver does not need to.
Reviewed-by: Mathieu Poirier
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/rpmsg/virtio_rpmsg_bus.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/net/wireless/virtual/mac80211_hwsim.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/wireless/virtual/mac80211_hwsim.c
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
fs/fuse/virtio_fs.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/fuse/virtio_fs.c b/fs/fuse/virtio_fs.c
index 322af827a232..ca7b64f9c3c7 100644
---
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
sound/virtio/virtio_card.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/sound/virtio/virtio_card.c b/sound/virtio/virtio_card.c
index
virtio core already sets the .owner, so driver does not need to.
>
> Acked-by: Dave Jiang
> Signed-off-by: Krzysztof Kozlowski
>
Reviewed-by: Pankaj Gupta
> Depends on the first patch.
> ---
> drivers/nvdimm/virtio_pmem.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git
Changes in v2:
- Three new patches: virtio mem+input+balloon
- Minor commit msg adjustments
- Add tags
- Link to v1:
https://lore.kernel.org/r/20240327-module-owner-virtio-v1-0-0feffab77...@linaro.org
Merging
===
All further patches depend on the first virtio patch, therefore please ack
and
virtio core already sets the .owner, so driver does not need to.
Acked-by: Johannes Berg
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
arch/um/drivers/virt-pci.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/um/drivers/virt-pci.c b/arch/um/drivers/virt-pci.c
Modules registering driver with register_virtio_driver() might forget to
set .owner field. i2c-virtio.c for example has it missing. The field
is used by some of other kernel parts for reference counting
(try_module_get()), so it is expected that drivers will set it.
Solve the problem by moving
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Changes in v2:
1. New patch
---
drivers/virtio/virtio_balloon.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c
index
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/char/hw_random/virtio-rng.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/char/hw_random/virtio-rng.c
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/char/virtio_console.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c
index
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/block/virtio_blk.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
index
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/bluetooth/virtio_bt.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/bluetooth/virtio_bt.c b/drivers/bluetooth/virtio_bt.c
index
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Changes in v2:
1. New patch
---
drivers/virtio/virtio_mem.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/virtio/virtio_mem.c b/drivers/virtio/virtio_mem.c
index
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Changes in v2:
1. New patch
---
drivers/virtio/virtio_input.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/virtio/virtio_input.c b/drivers/virtio/virtio_input.c
index
virtio core already sets the .owner, so driver does not need to.
Acked-by: Dave Jiang
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/nvdimm/virtio_pmem.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/nvdimm/virtio_pmem.c
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/scsi/virtio_scsi.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c
index
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
net/9p/trans_virtio.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/net/9p/trans_virtio.c b/net/9p/trans_virtio.c
index e305071eb7b8..0b8086f58ad5
virtio core already sets the .owner, so driver does not need to.
Acked-by: Stefano Garzarella
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
net/vmw_vsock/virtio_transport.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/net/vmw_vsock/virtio_transport.c
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/firmware/arm_scmi/virtio.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/firmware/arm_scmi/virtio.c
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/crypto/virtio/virtio_crypto_core.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/crypto/virtio/virtio_crypto_core.c
virtio core already sets the .owner, so driver does not need to.
Acked-by: Bartosz Golaszewski
Acked-by: Viresh Kumar
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/gpio/gpio-virtio.c | 1 -
1 file changed, 1 deletion(-)
diff --git
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/gpu/drm/virtio/virtgpu_drv.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/virtio/virtgpu_drv.c
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/iommu/virtio-iommu.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/iommu/virtio-iommu.c b/drivers/iommu/virtio-iommu.c
index
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/net/caif/caif_virtio.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/caif/caif_virtio.c b/drivers/net/caif/caif_virtio.c
index
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/misc/nsm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/misc/nsm.c b/drivers/misc/nsm.c
index 0eaa3b4484bd..ef7b32742340 100644
---
virtio core already sets the .owner, so driver does not need to.
Signed-off-by: Krzysztof Kozlowski
---
Depends on the first patch.
---
drivers/net/virtio_net.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
index
On Wed, Mar 27, 2024 at 01:40:54PM +0100, Krzysztof Kozlowski wrote:
> Modules registering driver with register_virtio_driver() might forget to
> set .owner field. i2c-virtio.c for example has it missing. The field
> is used by some of other kernel parts for reference counting
>
On sobota 20. ledna 2024 7:44:45, CEST Randy Dunlap wrote:
>
> On 1/19/24 02:22, Oleksandr Natalenko wrote:
> > While studying the code I've bumped into a small typo within the
> > kernel-doc for two functions, apparently, due to copy-paste.
> >
> > This commit fixes "sizo" word to be "size".
>
Bindings for the imx-ldb never allowed specifying the EDID in DT. None
of the existing DT files use it. Drop it now in favour of using debugfs
overrides or the drm.edid_firmware support.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/imx/ipuv3/imx-ldb.c | 27 ++-
1
Use the imx_legacy bridge driver instead of handlign display modes via
the connector node.
All existing usecases already support attaching using
the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag, while the imx_legacy bridge
doesn't support creating connector at all. Switch to
drm_bridge_connector at the
Use the imx_legacy bridge driver instead of handlign display modes via
the connector node.
All existing usecases already support attaching using
the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag, while the imx_legacy bridge
doesn't support creating connector at all. Switch to
drm_bridge_connector at the
The imx-tve driver is the only remaining user of
imx_drm_connector_destroy(). Move the function to imx-tve.c
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/imx/ipuv3/imx-drm-core.c | 7 ---
drivers/gpu/drm/imx/ipuv3/imx-drm.h | 2 --
drivers/gpu/drm/imx/ipuv3/imx-tve.c | 8
i.MX DRM DT bindings allow using either a proper panel / bridge graph to
provide information about connected panels, or just a display-timings DT
node, describing just the timings and the flags. Add helper bridge
driver supporting the latter usecase. It will be used by both LDB and
The in-kernel DT files do not use ddc-i2c-bus property with the iMX LVDS
Display Bridge. If in future a need arises to support such usecase, the
panel-simple should be used, which is able to handle the DDC bus.
Acked-by: Rob Herring
Signed-off-by: Dmitry Baryshkov
---
Defer panel handling to drm_panel_bridge, unifying codepaths for the
panel and bridge cases.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/imx/ipuv3/Kconfig | 2 ++
drivers/gpu/drm/imx/ipuv3/imx-ldb.c | 44 -
2 files changed, 16 insertions(+), 30
Defer panel handling to drm_panel_bridge, unifying codepaths for the
panel and bridge cases.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/imx/ipuv3/Kconfig| 2 ++
drivers/gpu/drm/imx/ipuv3/parallel-display.c | 35 +++-
2 files changed, 10
Drop unused defines and obsolete prototypes from the imx-drm.h header.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/imx/ipuv3/imx-drm.h | 12
1 file changed, 12 deletions(-)
diff --git a/drivers/gpu/drm/imx/ipuv3/imx-drm.h
b/drivers/gpu/drm/imx/ipuv3/imx-drm.h
index
Hi Rob, Helge
We already have for_each_endpoint_of_node(), but some drivers are
not using it. This patch-set replace it.
This patch-set is related to "OF" (= Rob), but many driveres are for
"MultiMedia" (= Helge). I'm not sure who handle these.
[o] done
[*] this patch-set
[o] tidyup
None of the in-kernel DT files ever used edid override with the
fsl-imx-drm driver. In case the EDID needs to be specified manually, DRM
core allows one to either override it via the debugfs or to load it via
request_firmware by using DRM_LOAD_EDID_FIRMWARE. In all other cases
EDID and/or modes
None of the boards ever supported by the upstream kernel used the custom
DDC bus support with the LDB connector. If a need arises to do so, one
should use panel-simple and its DDC bus code. Drop ddc-i2c-bus support
from the imx-ldb driver.
Signed-off-by: Dmitry Baryshkov
---
None of the in-kernel DT files ever used edid override with the
fsl-imx-drm driver. In case the EDID needs to be specified manually, DRM
core allows one to either override it via the debugfs or to load it via
request_firmware by using DRM_LOAD_EDID_FIRMWARE. In all other cases
EDID and/or modes
The IPUv3 DRM i.MX driver contains several codepaths for different
usescases: both LDB and paralllel-display drivers handle next-bridge,
panel and the legacy display-timings DT node on their own.
Drop unused ddc-i2c-bus and edid handling (none of the DT files merged
upstream ever used these
We already have for_each_endpoint_of_node(), don't use
of_graph_get_next_endpoint() directly. Replace it.
Signed-off-by: Kuninori Morimoto
---
drivers/media/platform/ti/am437x/am437x-vpfe.c | 12 +---
drivers/media/platform/ti/davinci/vpif_capture.c | 12 ++--
2 files changed,
We already have for_each_endpoint_of_node(), don't use
of_graph_get_next_endpoint() directly. Replace it.
Signed-off-by: Kuninori Morimoto
---
drivers/media/platform/xilinx/xilinx-vipp.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git
We already have for_each_endpoint_of_node(), don't use
of_graph_get_next_endpoint() directly. Replace it.
Signed-off-by: Kuninori Morimoto
---
drivers/staging/media/deprecated/atmel/atmel-sama5d2-isc.c | 6 +-
drivers/staging/media/deprecated/atmel/atmel-sama7g5-isc.c | 6 +-
2 files
We already have for_each_endpoint_of_node(), don't use
of_graph_get_next_endpoint() directly. Replace it.
Signed-off-by: Kuninori Morimoto
---
drivers/video/fbdev/omap2/omapfb/dss/omapdss-boot-init.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
We already have of_graph_get_remote_port(), Let's use it.
Signed-off-by: Kuninori Morimoto
---
drivers/video/fbdev/omap2/omapfb/dss/dss-of.c | 15 +--
1 file changed, 1 insertion(+), 14 deletions(-)
diff --git a/drivers/video/fbdev/omap2/omapfb/dss/dss-of.c
We already have for_each_endpoint_of_node(), don't use
of_graph_get_next_endpoint() directly. Replace it.
Signed-off-by: Kuninori Morimoto
---
.../microchip/microchip-sama5d2-isc.c | 19 +++
.../microchip/microchip-sama7g5-isc.c | 19 +++
2 files
We already have for_each_endpoint_of_node(), don't use
of_graph_get_next_endpoint() directly. Replace it.
Signed-off-by: Kuninori Morimoto
---
drivers/gpu/drm/omapdrm/dss/base.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/omapdrm/dss/base.c
We already have for_each_endpoint_of_node(), don't use
of_graph_get_next_endpoint() directly. Replace it.
Signed-off-by: Kuninori Morimoto
Reviewed-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-platform.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
How often will you send this spam again?
> Am 31.03.2024 um 18:46 schrieb Ricardo Garcia :
>
> This is a reminder that the membership renewal period ends in 2 days,
> and elections will start after that. Please register as an X.Org
> Foundation member to be able to vote in the upcoming
On Sun, Mar 31, 2024 at 10:43:58AM +0200, Krzysztof Kozlowski wrote:
> virtio core already sets the .owner, so driver does not need to.
>
Acked-by: Sudeep Holla
--
Regards,
Sudeep
DT bindings for adv7511 and adv7533 bridges specify HDMI output to be
present at the port@1. This allows board DT to add e.g. HDMI connector
nodes or any other next chained bridge. Make adv7511 driver discover
that bridge and attach it to the chain.
Signed-off-by: Dmitry Baryshkov
---
Changes in
Hi Thomas and Jocelyn,
What we do in ast_dp_set_on_off() is a handshake between host driver and
bmc-fw to confirm
the operation, on/off, is completed.
We use some scratch registers in bmc to handshake with host. This handshake
only work if
BMC's scu-lock is opened. If scu-lock is opened too
Generate DRM/MSM headers on the fly during kernel build. This removes a
need to push register changes to Mesa with the following manual
synchronization step. Existing headers will be removed in the following
commits (split away to ease reviews).
Signed-off-by: Dmitry Baryshkov
---
Now as the headers are generated during the build step, drop
pre-generated copies of the Adreno A6xx GMU header.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/adreno/a6xx_gmu.xml.h | 422 --
1 file changed, 422 deletions(-)
diff --git
Import the gen_headers.py script from Mesa, commit b5414e716684
("freedreno/registers: Add license header"). This script will be used to
generate MSM register files on the fly during compilation.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/registers/gen_header.py | 961
As a preparation to removal of a6xx.xml.h, drop the C++ part of the
heder, it is not used by the kernel anyway.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/adreno/a6xx.xml.h | 2478 -
1 file changed, 2478 deletions(-)
diff --git
Currently display-related register headers are generated from XML files
shipped withing Mesa source tree. This is not fully optimal: it requires
multi-stage process of the changes first being landed to Mesa and only
then synced to the kernel tree.
Move original XML files to the kernel tree and
Two core driver files include headers from Adreno subdir, which also
brings dependency on the Adreno register headers. Rework those includes
to remove unnecessary dependency.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/msm_drv.c | 3 ++-
drivers/gpu/drm/msm/msm_gpu.c | 2 +-
2 files
The msm_gpummu.c implementation is used only on A2xx and it is tied to
the A2xx registers. Rename the source file accordingly.
Reviewed-by: Akhil P Oommen
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/Makefile | 2 +-
drivers/gpu/drm/msm/adreno/a2xx_gpu.c
The mmss_cc.xml.h file describes bits of the MMSS clock controller on
APQ8064 / MSM8960 platforms. They are not used by the driver and do not
belong to the DRM MSM driver. Drop the file.
Reviewed-by: Abhinav Kumar
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/dsi/mmss_cc.xml.h | 131
In order to stop patching the mdp5 headers, import definitions for the
writeback blocks. This part is extracted from the old Rob's patch.
Co-developed-by: Rob Clark
Signed-off-by: Rob Clark
Reviewed-by: Abhinav Kumar
Signed-off-by: Dmitry Baryshkov
---
The qfprom.xml.h contains definitions for the nvmem code. They are not
used in the existing code. Also if we were to use them later, we should
have used nvmem cell API instead of using these defs. Drop the file.
Reviewed-by: Abhinav Kumar
Signed-off-by: Dmitry Baryshkov
---
Hi Thomas and Jocelyn,
What we do in ast_dp_set_on_off() is a handshake between host driver
and bmc-fw to confirm
the operation, on/off, is completed.
We use some scratch registers in bmc to handshake with host. This
handshake only work if
BMC's scu-lock is opened. If scu-lock is opened too
From: Jesse Zhang
remove the unsed the paramter in the function
ttm_bo_bounce_temp_buffer and ttm_bo_add_move_fence.
V2:rebase the patch on top of drm-misc-next (Christian)
Signed-off-by: Jesse Zhang
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 8 +++-
1 file changed,
73 matches
Mail list logo