On 24/12/2021 19:24, David Heidelberg wrote:
Convert Qualcomm HDMI binding into HDMI TX and PHY yaml bindings.
Other changes:
- fixed reg-names numbering to match 0..3 instead 0,1,3,4
Reviewed-by: Dmitry Baryshkov
Signed-off-by: David Heidelberg
---
.../devicetree/bindings/display/msm
Enable port inside panel bindings.
Fixes warnings generated by `make qcom-apq8064-asus-nexus7-flo.dtb` as:
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dt.yaml: panel@0: 'port' does
not match any of the regexes: 'pinctrl-[0-9]+'
From schema:
Documentation/devicetree/bindings/display/pa
Link is no longer functional and web.archive.org doesn't provide PDF
with detail information.
Some informations can be found from web.archive.org here:
https://web.archive.org/web/20170629205602/http://panelone.net/en/7-0-inch/JDI_LT070ME05000_7.0_inch-datasheet
Signed-off-by: David Heidelberg
-
Convert Qualcomm HDMI binding into HDMI TX and PHY yaml bindings.
Other changes:
- fixed reg-names numbering to match 0..3 instead 0,1,3,4
Signed-off-by: David Heidelberg
---
.../devicetree/bindings/display/msm/hdmi.txt | 99 -
.../bindings/display/msm/qcom,hdmi-phy.yaml | 119
From: Kuogee Hsieh
Signed-off-by: Kuogee Hsieh
Reviewed-by: Stephen Boyd
Signed-off-by: Sankeerth Billakanti
---
arch/arm64/boot/dts/qcom/sc7280.dtsi | 90 +++-
1 file changed, 88 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sc7280.dtsi
Add edp controller and phy DT nodes for sc7280.
Signed-off-by: Sankeerth Billakanti
Signed-off-by: Krishna Manikandan
Reviewed-by: Stephen Boyd
---
arch/arm64/boot/dts/qcom/sc7280.dtsi | 107 ++-
1 file changed, 105 insertions(+), 2 deletions(-)
diff --git a/ar
From: Rajeev Nandan
Add DSI controller and PHY nodes for sc7280.
Signed-off-by: Rajeev Nandan
Signed-off-by: Krishna Manikandan
Reviewed-by: Matthias Kaehlcke
Reviewed-by: Stephen Boyd
Signed-off-by: Sankeerth Billakanti
---
arch/arm64/boot/dts/qcom/sc7280.dtsi | 111 ++
From: Krishna Manikandan
Add mdss and mdp DT nodes for sc7280.
Signed-off-by: Krishna Manikandan
Reviewed-by: Stephen Boyd
Signed-off-by: Sankeerth Billakanti
---
arch/arm64/boot/dts/qcom/sc7280.dtsi | 90
1 file changed, 90 insertions(+)
diff --git a/ar
Add display devicetree support for sc7280 platform.
Krishna Manikandan (1):
arm64: dts: qcom: sc7280: add display dt nodes
Kuogee Hsieh (1):
arm64: dts: qcom: sc7280: Add Display Port node
Rajeev Nandan (1):
arm64: dts: qcom: sc7280: Add DSI display nodes
Sankeerth Billakanti (1):
arm6
platform_get_resource() may fail and return NULL, so check it's value
before using it.
'drm' could be null in sprd_drm_shutdown, and drm_warn maybe dereference
it, remove this warning log.
Cc: Orson Zhai
Cc: Chunyan Zhang
Signed-off-by: Kevin Tang
---
drivers/gpu/drm/sprd/sprd_dpu.c | 3 +++
On linux-next, commit 43531edd53f0 ("drm/sprd: add Unisoc's drm kms master")
adds the config DRM_SPRD,
which selects DRM_KMS_CMA_HELPER.
However, commit 09717af7d13d ("drm: Remove CONFIG_DRM_KMS_CMA_HELPER option")
just removed the
DRM_KMS_CMA_HELPER. So, the select DRM_KMS_CMA_HELPER refers to
v1:
remove the selected DRM_KMS_CMA_HELPER in kconfig
drm-sprd-fix-potential-NULL-dereference
Kevin Tang (2):
drm/sprd: remove the selected DRM_KMS_CMA_HELPER in kconfig
drm/sprd: fix potential NULL dereference
drivers/gpu/drm/sprd/Kconfig| 1 -
drivers/gpu/drm/sprd/sprd_dpu.c | 3 ++
On 2021-12-23 11:06, asheplya...@basealt.ru wrote:
From: Alexey Sheplyakov
T62x/T60x GPUs are known to not work with panfrost as of now.
One of the reasons is wrong/incomplete memory attributes which
the panfrost driver sets in the page tables:
- MEMATTR_IMP_DEF should be 0x48ULL, not 0x88ULL.
On 23/12/2021 17:35, John Harrison wrote:
[snip]
On the other hand, the GuC log is useful for debugging certain issues
and it is included automatically in the sysfs error capture along
with all the other hardware and software state that we save.
There is intended to be a publicly released
Hi Melissa,
Thank you very much for your review.
> On Thu, Dec 23, 2021 at 07:35:48PM -0100, Melissa Wen wrote:
> What test did you run? Indeed, not all kms tests are passing and fixes
> are welcome :)
>
> Last time, I used these testcases for overlay: kms_plane_cursor,
> kms_atomic; and these t
I do agree with shaoyun, if the host find the gpu engine hangs first, and do
the flr, guest side thread may not know this and still try to access HW(e.g.
kfd is using a lot of amdgpu_in_reset and reset_sem to identify the reset
status). And this may lead to very bad result.
On 2021/12/24 下午4:58
Il 24/12/21 09:21, Miaoqian Lin ha scritto:
The of_device_get_match_data() function may return NULL.
Add check to prevent potential null dereference.
Signed-off-by: Miaoqian Lin
Reviewed-by: AngeloGioacchino Del Regno
These patches look good to me. JingWen will pull these patches and do some
basic TDR test on sriov environment, and give feedback.
Best wishes
Emily Deng
>-Original Message-
>From: Liu, Monk
>Sent: Thursday, December 23, 2021 6:14 PM
>To: Koenig, Christian ; Grodzovsky, Andrey
>; dri-
This issue happens in an error path of igt_dmabuf_export_vmap(). When
dma_buf_vmap() succeeds and memchr_inv() returns nonzero, the function
forgets to decrement `vmapping_counter` of the dma_buf object, which
may result in refcount leaks.
Fix it by calling dma_buf_vunmap() under label `out_dma_ma
Add the missing lvds0 node for the R-Car M3-W+ SoC.
Signed-off-by: Nikita Yushchenko
---
arch/arm64/boot/dts/renesas/r8a77961.dtsi | 27 +++
1 file changed, 27 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a77961.dtsi
b/arch/arm64/boot/dts/renesas/r8a77961.dtsi
i
platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
allocation of IRQ resources in DT core code, this causes an issue
when using hierarchical interrupt domains using "interrupts" property
in the node as this bypassed the hierarchical setup and messed up the
irq chaining.
In preparatio
Hi All,
This patch series aims to drop using platform_get_resource() for IRQ types
in preparation for removal of static setup of IRQ resource from DT core
code.
Dropping usage of platform_get_resource() was agreed based on
the discussion [0].
[0] https://patchwork.kernel.org/project/linux-renesa
From: Alexey Sheplyakov
Hello,
these patches address some problems which prevent panfrost from
working with Mali T628 GPUs:
- incomplete/incorrect mmu memory attributes
- wrong jobs affinity on dual core group GPUs
With these patches panfrost is able to drive mali T628 (r1p0) GPU
on some armv8
platform_get_resource_byname(pdev, IORESOURCE_IRQ, ..) relies on static
allocation of IRQ resources in DT core code, this causes an issue
when using hierarchical interrupt domains using "interrupts" property
in the node as this bypassed the hierarchical setup and messed up the
irq chaining.
In pre
From: Alexey Sheplyakov
On a dual core group GPU it's not OK to run some jobs on any core.
For such jobs the following affinity rule must be satisfied: job
slot 2 must target the core group 1, and slots 0, 1 - the core
group 0, respectively.
The kernel driver itself can't guess which jobs need a
platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
allocation of IRQ resources in DT core code, this causes an issue
when using hierarchical interrupt domains using "interrupts" property
in the node as this bypassed the hierarchical setup and messed up the
irq chaining.
In preparatio
From: Alexey Sheplyakov
T62x/T60x GPUs are known to not work with panfrost as of now.
One of the reasons is wrong/incomplete memory attributes which
the panfrost driver sets in the page tables:
- MEMATTR_IMP_DEF should be 0x48ULL, not 0x88ULL.
0x88ULL is MEMATTR_OUTER_IMP_DEF
- MEMATTR_FORCE_C
platform_get_resource_byname(pdev, IORESOURCE_IRQ, ..) relies on static
allocation of IRQ resources in DT core code, this causes an issue
when using hierarchical interrupt domains using "interrupts" property
in the node as this bypassed the hierarchical setup and messed up the
irq chaining.
In pre
platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
allocation of IRQ resources in DT core code, this causes an issue
when using hierarchical interrupt domains using "interrupts" property
in the node as this bypassed the hierarchical setup and messed up the
irq chaining.
In preparatio
Document the R-Car M3-W+ (R8A77961) SoC in the R-Car LVDS encoder
bindings.
Signed-off-by: Nikita Yushchenko
---
.../devicetree/bindings/display/bridge/renesas,lvds.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/display/bridge/renesas,lvds.yaml
The M3-W+ SoC has the same LVDS encoder as other R-Car Gen3 chips.
Add support for M3-W+ (R8A77961) SoC to the LVDS encoder driver.
Signed-off-by: Nikita Yushchenko
---
drivers/gpu/drm/rcar-du/rcar_lvds.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/rcar-du/rcar_lvds.c
b/
This patchset adds support for the LVDS encoder inside R-Car M3-W+ SoC.
Hardware is the same as on other R-Car Gen-3 chips.
Nikita Yushchenko (3):
drm: rcar-du: lvds: Add r8a77961 support
arm64: dts: renesas: r8a77961: Add lvds0 device node
dt-bindings: display: bridge: renesas,lvds: Documen
The of_device_get_match_data() function may return NULL.
Add check to prevent potential null dereference.
Signed-off-by: Miaoqian Lin
---
drivers/phy/mediatek/phy-mtk-mipi-dsi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/phy/mediatek/phy-mtk-mipi-dsi.c
b/drivers/phy/mediatek/
33 matches
Mail list logo
