Enable the supporting of wide sscreen on AST2600, so that the resolution
of 16:9 and 16:10 are able to be selected on Display Settings.
Signed-off-by: KuoHsiang Chou
---
drivers/gpu/drm/ast/ast_main.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/ast/ast_main.c b/drivers/
sn65dsi83_parse_dt() takes a reference on 'ctx->host_node' that must be
released in the error handling path of this function and of the probe.
This is only done in the remove function up to now.
Fixes: ceb515ba29ba ("drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 and SN65DSI84
driver")
Signed-off-by:
On Tue, 14 Dec 2021, Matthew Brost wrote:
> Increment composite fence seqno on each fence creation.
For future reference, this commit message is not enough. Both the
subject line and the commit message just repeat what I can see from the
code, i.e. *what* is being done, but there is not a hint on
Hi Dave & Daniel -
Final i915 fixes for v5.16.
BR,
Jani.
The following changes since commit fc74e0a40e4f9fd0468e34045b0c45bba11dcbb2:
Linux 5.16-rc7 (2021-12-26 13:17:17 -0800)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-fixes-2021-
Hi Dave & Daniel -
A lone FBC fix for drm-next for the merge window.
BR,
Jani.
The following changes since commit 040bf2a9446f6ba267225d34dc4a9b14d11e5092:
Merge tag 'drm-misc-next-fixes-2021-12-23' of
git://anongit.freedesktop.org/drm/drm-misc into drm-next (2021-12-24 06:24:06
+1000)
a
Em Wed, 29 Dec 2021 12:45:38 +0100
Niklas Schnelle escreveu:
> On Tue, 2021-12-28 at 18:12 +0100, Mauro Carvalho Chehab wrote:
> > Em Tue, 28 Dec 2021 16:06:44 +0100
> > Niklas Schnelle escreveu:
> >
> > (on a side note: the c/c list of this patch is too long. I would try to
> > avoid using a t
https://bugzilla.kernel.org/show_bug.cgi?id=215436
Bug ID: 215436
Summary: admgpu: suspend and resuming from suspend don't work
Product: Drivers
Version: 2.5
Kernel Version: 5.16-rc{1-7}
Hardware: All
OS: Linux
On 29/12/2021 04:04, miles.c...@mediatek.com wrote:
Hi,
On 28/12/2021 10:25, Miles Chen wrote:
Fix unused-but-set variable warning:
drivers/gpu/drm/mediatek/mtk_cec.c:85:6: warning: variable 'tmp' set but not
used [-Wunused-but-set-variable]
Actually we ignore the value passed to mtk_ce
https://bugzilla.kernel.org/show_bug.cgi?id=215436
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
https://bugzilla.kernel.org/show_bug.cgi?id=215436
--- Comment #2 from Alex Deucher (alexdeuc...@gmail.com) ---
Could you please help add some prints and confirm that the commit doesn't
change the code sequence in rn_update_clocks() especially for the following
part in suspend and wake sequence:
i
Hi Dave, Daniel,
Fixes for 5.16. A little bigger than usual since it's two weeks worth of
fixes. We have a fix for the runtime pm regression with efifb, but we
are currently testing some less invasive changes. See:
https://gitlab.freedesktop.org/drm/amd/-/issues/1840
https://bugzilla.kernel.org
On Wed, Dec 29, 2021 at 01:12:07PM +0100, Mauro Carvalho Chehab wrote:
> Em Wed, 29 Dec 2021 12:45:38 +0100
> Niklas Schnelle escreveu:
> > ...
> > I do think we agree that once done correctly there is value in
> > such an option independent of HAS_IOPORT only gating inb() etc uses.
I'm not sure
Hi Christophe,
Thank you for the patch.
On Wed, Dec 29, 2021 at 09:58:44AM +0100, Christophe JAILLET wrote:
> sn65dsi83_parse_dt() takes a reference on 'ctx->host_node' that must be
> released in the error handling path of this function and of the probe.
> This is only done in the remove function
Hi Dave, Daniel,
Fixes for 5.17.
The following changes since commit a342655865b2f14d1fbf346356d3b3360e63e872:
drm/radeon: Fix syntax errors in comments (2021-12-14 16:11:02 -0500)
are available in the Git repository at:
https://gitlab.freedesktop.org/agd5f/linux.git
tags/amd-drm-next-5.17
Hi Nikita,
Thank you for the patch.
On Fri, Dec 24, 2021 at 08:23:09AM +0300, Nikita Yushchenko wrote:
> 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 |
Hi Nikita,
Thank you for the patch.
On Fri, Dec 24, 2021 at 08:23:07AM +0300, Nikita Yushchenko wrote:
> 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
Reviewed-by: Laure
Hi Nikita,
Thank you for the patch.
On Fri, Dec 24, 2021 at 08:23:08AM +0300, Nikita Yushchenko wrote:
> 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
Add and enable PM6150L wled which is used for controlling the display
backlight on Fairphone 4.
This series depends on the recent wled series by Marijn Suijten,
currently applied in the for-backlight-next branch of
kernel/git/lee/backlight.git (or linux-next).
Luca Weiss (4):
dt-bindings: backl
Document the compatible for the wled block found in PM6150L.
Signed-off-by: Luca Weiss
---
Documentation/devicetree/bindings/leds/backlight/qcom-wled.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/leds/backlight/qcom-wled.yaml
b/Documentation/devicetr
PM6150L contains WLED of version 5. Add support ofr it to the driver.
Signed-off-by: Luca Weiss
---
drivers/video/backlight/qcom-wled.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/video/backlight/qcom-wled.c
b/drivers/video/backlight/qcom-wled.c
index 306bcc6ccb92..527210e85795
Hi Nikita,
On Wed, Dec 29, 2021 at 08:04:18PM +0300, Nikita Yushchenko wrote:
> Hi.
>
> Thank you for looking at this.
>
> >> + port@1 {
> >> + reg = <1>;
> >> + lvds0_out: endpoint {
> >>
From: Kuogee Hsieh
Some DP sinkers prefer to use tps4 instead of tps3 during training #2.
This patch will use tps4 to perform link training #2 if sinker's DPCD
supports it.
Changes in V2:
-- replace dp_catalog_ctrl_set_pattern() with
dp_catalog_ctrl_set_pattern_state_bit()
Signed-off-by: Kuo
[Why]
Creating the prop uses UNKNOWN as the initial value, which is not a
supported value if the prop is to be supported.
[How]
Set the panel orientation default value to NORMAL right after creating
the prop if no DSI panel exists.
Panels have their own orientations, and panel orientation can't be
[Why]
Creating the prop uses UNKNOWN as the initial value, which is not a
supported value if the prop is to be supported.
[How]
Set the panel orientation default value to NORMAL right after creating
the prop if no DSI panel exists.
Panels have their own orientations, and panel orientation can't be
There is kernel crashed due to unable to handle kernel NULL
pointer dereference of dp_panel->connector while running DP link
layer compliance test case 4.2.2.6 (EDID Corruption Detection).
This patch fixes this problem by populating connector of dp_panel.
[drm:dp_panel_read_sink_caps] *ERROR* pane
hey - uploaded v2 that takes care of the panel:
https://patchwork.kernel.org/project/linux-mediatek/patch/20211229184420.793234-1-markyac...@chromium.org/
Thanks!
On Tue, Dec 14, 2021 at 10:26 AM Mark Yacoub wrote:
>
> Thank you so much!
>
> On Mon, Dec 13, 2021 at 6:27 PM Chun-Kuang Hu wrote:
Hi Nikita,
On Wed, Dec 29, 2021 at 08:19:10PM +0300, Nikita Yushchenko wrote:
> >> If this approach is not appropriate, then perhaps need to fix it in
> >> files for all SoCs, to make it possible for extension board dtsi to be
> >> compatible with all of them.
> >
> > I'm writing a patch to drop
On 12/28/2021 4:29 PM, Dmitry Baryshkov wrote:
Kuogee,
Some time ago you volonteered to check these two patches on a DP
hosts. Any progress?
On 26/11/2021 05:35, Dmitry Baryshkov wrote:
In order to simplify DP code, drop hand-coded loops over clock arrays,
replacing them with clk_bulk_* fu
Hi Nikito,
On Thu, Dec 30, 2021 at 12:12:04AM +0300, Nikita Yushchenko wrote:
> Endpoints are meant to model a link between two ports, so an endpoint
> > shouldn't exist in isolation. The issue with creating named endpoints in
> > SoC files is that you can't tell there what remote devices may ex
This patch series is for making the GPD Win Max display usable with
Linux.
The GPD Win Max is a small laptop, and its eDP panel does not send an
EDID over DPCD; the EDID is instead available in the intel opregion, in
mailbox #5 [1]
The second patch is just to fix the orientation of the panel.
Ch
Panel is 800x1280, but mounted on a laptop form factor, sideways.
Signed-off-by: Anisse Astier
Reviewed-by: Hans de Goede
---
drivers/gpu/drm/drm_panel_orientation_quirks.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/gpu/drm/drm_panel_orientation_quirks.c
b/drivers/gpu/dr
The ACPI OpRegion Mailbox #5 ASLE extension may contain an EDID to be
used for the embedded display. Add support for using it via by adding
the EDID to the list of available modes on the connector, and use it for
eDP when available.
If a panel's EDID is broken, there may be an override EDID set in
Hi Nikita,
Thank you for the patch.
On Sat, Dec 25, 2021 at 09:31:51AM +0300, Nikita Yushchenko wrote:
> Hotplug events reported by bridge drivers over drm_bridge_hpd_notify()
> get ignored unless somebody calls drm_bridge_hpd_enable(). When the
> connector for the bridge is bridge_connector, suc
On Fri, 2021-12-24 at 08:21 +, Miaoqian Lin wrote:
> 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
Actual hardware state of CRTC is controlled by the member 'active' in
struct drm_crtc_state instead of the member 'enable', according to the
kernel doc of the member 'enable'. In fact, the drm client modeset
and atomic helpers are using the member 'active' to do the control.
Referencing the membe
Hi All,
I am working on a platform based on the Renesas RZ/G2 SoC family. This
chip uses the rcar-du driver for the display. I would like to submit a patch to
address the fact that the driver does not check/honor the flag
DRM_BUS_FLAG_PIXDATA_DRIVE_POSEDGE. My issue is that I would like t
Hey,
dim: 3be2709660dc ("drm/amdgpu: Call amdgpu_device_unmap_mmio() if
device is unplugged to prevent crash in GPU initialization failure"):
committer Signed-off-by missing.
is missing your sob as you committed it. Please fix it up.
Thanks,
Dave.
On Thu, 30 Dec 2021 at 01:51, Alex Deucher wrote:
>
> Hi Dave, Daniel,
Just FYI on merging this into tip I got a conflict I'm not sure what
answer is right.
fixes has:
ee2698cf79cc759a397c61086c758d4cc85938bf
Author: Angus Wang
Date: Thu Dec 9 17:27:01 2021 -0500
drm/amd/display: Changed
If of_find_device_by_node() succeeds, dsi_get_phy() doesn't
a corresponding put_device(). Thus add put_device() to fix the exception
handling.
Fixes: ec31abf ("drm/msm/dsi: Separate PHY to another platform device")
Signed-off-by: Miaoqian Lin
---
drivers/gpu/drm/msm/dsi/dsi.c | 7 ++-
1 file
39 matches
Mail list logo
