On 12/28/22 02:40, yang.yan...@zte.com.cn wrote:
From: Xu Panda
The implementation of strscpy() is more robust and safer.
That's now the recommended way to copy NUL-terminated strings.
Signed-off-by: Xu Panda
Signed-off-by: Yang Yang
---
drivers/video/fbdev/omap/omapfb_main.c | 5 ++---
https://bugzilla.kernel.org/show_bug.cgi?id=216855
Artem S. Tashkinov (a...@gmx.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
On Mon, Dec 12, 2022 at 10:33:13AM +0100, Konrad Dybcio wrote:
> Years after the SoC support has been added, it's high time for it to
> get dispcc going. Add the node to ensure that.
>
> Signed-off-by: Konrad Dybcio
> ---
> arch/arm64/boot/dts/qcom/sm8150.dtsi | 26 ++
>
On Mon, Dec 12, 2022 at 10:33:14AM +0100, Konrad Dybcio wrote:
> Add required nodes for MDSS and hook up provided clocks in DISPCC.
> This setup is almost identical to 8[23]50.
>
> Signed-off-by: Konrad Dybcio
> ---
> arch/arm64/boot/dts/qcom/sm8150.dtsi | 271 ++-
> 1
There are 3 possible interrupt sources are handled by DP controller,
HPDstatus, Controller state changes and Aux read/write transaction.
At every irq, DP controller have to check isr status of every interrupt
sources and service the interrupt if its isr status bits shows interrupts
are pending.
dp_display_irq_handler() is the main isr handler with the helps
of two sub isr, dp_aux_isr and dp_ctrl_isr, to service all DP
interrupts on every irq triggered. Current all three isr does
not return IRQ_HANDLED if there are any interrupts it had
serviced. This patch fix this ambiguity by having
ignore spuriors isr at dp_aux_isr() to fixed eDP edid read failed
Kuogee Hsieh (2):
drm/msm/dp: do not complete dp_aux_cmd_fifo_tx() if irq is not for aux
transfer
drm/msm/dp: enhance dp controller isr
drivers/gpu/drm/msm/dp/dp_aux.c | 97 ++---
On 12/6/2022 10:59 PM, Miaoqian Lin wrote:
of_icc_get() alloc resources for path1, we should release it when not
need anymore. Early return when IS_ERR_OR_NULL(path0) may leak path1.
Defer getting path1 to fix this.
Fixes: b9364eed9232 ("drm/msm/dpu: Move min BW request and full BW disable
On 11/16/2022 8:32 AM, Konrad Dybcio wrote:
On some SoCs (hello SM6350) vdds-supply is not wired to any smd-rpm
or rpmh regulator, but instead powered by the VDD_MX/mx.lvl line,
which is voted for in the DSI ctrl node.
Signed-off-by: Konrad Dybcio
Fixes: 8fc939e72ff8 ("dt-bindings: msm:
There is a macro for this already in the header, use
that instead and delete the custom DSI write macro defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
.../panel/panel-sony-tulip-truly-nt35521.c| 348 +-
1 file changed, 170 insertions(+), 178
There are macros for these already in the header, use
that instead and delete the custom DSI write macros defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
drivers/gpu/drm/panel/panel-jdi-fhd-r63452.c | 50 +++-
1 file changed, 17 insertions(+), 33
There is a macro for this already in the header, use
that instead and delete the custom DSI write macro defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
.../gpu/drm/panel/panel-xinpeng-xpp055c272.c | 44 ---
1 file changed, 18 insertions(+), 26 deletions(-)
There is a macro for this already in the header, use
that instead and delete the custom DSI write macro defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
.../gpu/drm/panel/panel-sharp-ls060t1sx01.c | 19 ++-
1 file changed, 2 insertions(+), 17 deletions(-)
There is a macro for this already in the header, use
that instead and delete the custom DSI write macro defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
.../panel/panel-samsung-s6e88a0-ams452ef01.c | 24 +++
1 file changed, 8 insertions(+), 16 deletions(-)
There is a macro for this already in the header, use
that instead and delete the custom DSI write macro defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
.../gpu/drm/panel/panel-mantix-mlaf057we51.c | 24 +++
1 file changed, 8 insertions(+), 16 deletions(-)
There are macros for these already in the header, use
that instead and delete the custom DSI write macros defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
drivers/gpu/drm/panel/panel-sitronix-st7703.c | 83 ---
1 file changed, 33 insertions(+), 50
There is a macro for this already in the header, use
that instead and delete the custom DSI write macro defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
drivers/gpu/drm/panel/panel-novatek-nt35950.c | 14 +++---
1 file changed, 3 insertions(+), 11 deletions(-)
diff
There is a macro for this already in the header, use
that instead and delete the custom DSI write macro defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
drivers/gpu/drm/panel/panel-samsung-sofef00.c | 24 +++
1 file changed, 8 insertions(+), 16 deletions(-)
There is a macro for this already in the header, use
that instead and delete the custom DSI write macro defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
drivers/gpu/drm/panel/panel-elida-kd35t133.c | 34
1 file changed, 13 insertions(+), 21 deletions(-)
Many panel drivers define dsi_dcs_write_seq() and dsi_generic_write_seq()
macros to send DCS commands and generic write packets respectively, with
the payload specified as a list of parameters instead of using arrays.
There's already a macro for the former, introduced by commit 2a9e9daf75231
There is a macro for this already in the header, use
that instead and delete the custom DSI write macro defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
.../drm/panel/panel-leadtek-ltk050h3146w.c| 64 ---
1 file changed, 28 insertions(+), 36 deletions(-)
There is a macro for this already in the header, use
that instead and delete the custom DSI write macro defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
.../gpu/drm/panel/panel-boe-bf060y8m-aj0.c| 28 +++
1 file changed, 10 insertions(+), 18 deletions(-)
There are macros for these already in the header, use
that instead and delete the custom DSI write macros defined in the driver.
Signed-off-by: Javier Martinez Canillas
---
.../drm/panel/panel-asus-z00t-tm5p5-n35596.c | 96 ---
1 file changed, 40 insertions(+), 56
Hello,
This series contains cleanups for DRM panel drivers that define their own
DSI write macros instead of using what's already in .
The changes are quite trivial but I've only tested this with allmodconfig
and `make M=drivers/gpu/drm/panel/` so please review and testing would be
highly
From: Xu Panda
The implementation of strscpy() is more robust and safer.
That's now the recommended way to copy NUL-terminated strings.
Signed-off-by: Xu Panda
Signed-off-by: Yang Yang
---
drivers/video/fbdev/aty/atyfb_base.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff
From: Xu Panda
The implementation of strscpy() is more robust and safer.
That's now the recommended way to copy NUL-terminated strings.
Signed-off-by: Xu Panda
Signed-off-by: Yang Yang
---
drivers/video/fbdev/omap/omapfb_main.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff
On 11/30/2022 5:58 AM, Konrad Dybcio wrote:
On some SoCs (hello SM6115) vcca-supply is not wired to any smd-rpm
or rpmh regulator, but instead powered by the VDD_MX line, which is
voted for in the DSI ctrl node.
Signed-off-by: Konrad Dybcio
Fixes: 8fc939e72ff8 ("dt-bindings: msm: dsi: add
On Tue, Dec 27, 2022 at 8:37 PM Jagan Teki wrote:
>
> On Wed, Dec 28, 2022 at 12:58 AM Javier Martinez Canillas
> wrote:
> >
> > Hello Jagan,
> >
> > On Tue, Dec 27, 2022 at 7:16 PM Jagan Teki
> > wrote:
> >
> > [...]
> >
> > > > +allOf:
> > > > + - $ref: panel-common.yaml#
> > > > +
> > > >
https://bugzilla.kernel.org/show_bug.cgi?id=216855
Bug ID: 216855
Summary: drivers/gpu/drm/nouveau/dispnv50/wndw.c:696:1:
warning: conflicting types
Product: Drivers
Version: 2.5
Kernel Version: 6.2-rc1
Hardware: All
On 12/27/22 19:48, Nathan Chancellor wrote:
On Sat, Dec 10, 2022 at 05:35:06PM +0100, Helge Deller wrote:
On 11/26/22 14:40, Thomas Zimmermann wrote:
Am 26.11.22 um 01:04 schrieb Randy Dunlap:
Make the offb (Open Firmware frame buffer) driver tristate,
i.e., so that it can be built as a
As v3d_submit_tfu_ioctl() performs the same steps as drm_gem_object_lookup(),
replace the open-code implementation in v3d with its DRM core equivalent.
Signed-off-by: Maíra Canal
---
drivers/gpu/drm/v3d/v3d_gem.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git
On Wed, Dec 28, 2022 at 12:58 AM Javier Martinez Canillas
wrote:
>
> Hello Jagan,
>
> On Tue, Dec 27, 2022 at 7:16 PM Jagan Teki wrote:
>
> [...]
>
> > > +allOf:
> > > + - $ref: panel-common.yaml#
> > > +
> > > +properties:
> > > + compatible:
> > > +enum:
> > > + # HannStar
Hi Dmitry / Christian, thanks for the fix!
(And thanks Melissa for pointing that, saving me lots of time in
research heh)
Is this fix planned to be released on 6.2-rc cycle? I've just tested it
on Steam Deck, and it resolved a lockup observed (since v6.2-rc1) -
exactly the same thing mentioned
Hello Jagan,
On Tue, Dec 27, 2022 at 7:16 PM Jagan Teki wrote:
[...]
> > +allOf:
> > + - $ref: panel-common.yaml#
> > +
> > +properties:
> > + compatible:
> > +enum:
> > + # HannStar HSD060BHW4 5.99" 720x1440 TFT LCD panel
> > + - hannstar,hsd060bhw4
>
> Parent controller can
Hello Alex,
On 12/27/22 18:04, Alex Deucher wrote:
[...]
>
> I think something like this would do the trick:
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> index 2017b3466612..45aee27ab6b1 100644
> ---
On Sat, Dec 10, 2022 at 05:35:06PM +0100, Helge Deller wrote:
> On 11/26/22 14:40, Thomas Zimmermann wrote:
> > Am 26.11.22 um 01:04 schrieb Randy Dunlap:
> > > Make the offb (Open Firmware frame buffer) driver tristate,
> > > i.e., so that it can be built as a loadable module.
> > >
> > >
kfree() & vfree() internally performs NULL check on the pointer handed
to it and take no action if it indeed is NULL. Hence there is no need
for a pre-check of the memory pointer before handing it to
kfree()/vfree().
Issue reported by ifnullfree.cocci Coccinelle semantic patch script.
kfree() & vfree() internally performs NULL check on the pointer handed
to it and take no action if it indeed is NULL. Hence there is no need
for a pre-check of the memory pointer before handing it to
kfree()/vfree().
Issue reported by ifnullfree.cocci Coccinelle semantic patch script.
On 12/26/2022 2:32 PM, Oded Gabbay wrote:
Move the habanalabs.h uapi file from include/uapi/misc to
include/uapi/drm, and rename it to habanalabs_accel.h.
This is required before moving the actual driver to the accel
subsystem.
Update MAINTAINERS file accordingly.
Signed-off-by: Oded Gabbay
On Mon, Dec 12, 2022 at 04:39:09PM +0100, Ulf Hansson wrote:
> On Fri, 9 Dec 2022 at 18:36, Ulf Hansson wrote:
> >
> > On Thu, 8 Dec 2022 at 22:06, Bjorn Andersson wrote:
> > >
> > > On Thu, Dec 08, 2022 at 02:40:55PM +0100, Ulf Hansson wrote:
> > > > On Wed, 7 Dec 2022 at 17:55, Bjorn Andersson
On Tue, Dec 27, 2022 at 4:33 PM Javier Martinez Canillas
wrote:
>
> Add device tree bindings for panels based on the Himax HX8394 controller,
> such as the HannStar HSD060BHW4 720x1440 TFT LCD panel that is connected
> through a MIPI-DSI video interface.
>
> Signed-off-by: Javier Martinez
On Tue, Dec 27, 2022 at 12:03:34PM +0100, Javier Martinez Canillas wrote:
> Add myself as maintainer for the driver and devicetree bindings schema.
>
> Signed-off-by: Javier Martinez Canillas
Acked-by: Sam Ravnborg
> ---
>
> (no changes since v1)
>
> MAINTAINERS | 7 +++
> 1 file
On Tue, Dec 27, 2022 at 12:13:56PM -0500, Rodrigo Vivi wrote:
> On Tue, Dec 27, 2022 at 01:30:53PM +0530, Deepak R Varma wrote:
> > Using DEFINE_SIMPLE_ATTRIBUTE macro with the debugfs_create_file()
> > function adds the overhead of introducing a proxy file operation
> > functions to wrap the
Is there a better place for this check higher up the intel specific
atomic-check? (so the check won't be skl specific - i notice that
intel_adjusted_rate is also called by
ilk_foo as well and non-backend-specific functions). Else, perhaps
intel_adjusted_rate should add a check + WARN? (if we
On Tue, 27 Dec 2022 11:39:25 -0500
Rodrigo Vivi wrote:
> On Sun, Dec 25, 2022 at 09:55:08PM +0300, Alexey Lukyanchuk wrote:
> > dell wyse 3040 doesn't peform poweroff properly, but instead remains in
> > turned power on state.
>
> okay, the motivation is explained in the commit msg..
>
> >
By default, HBR2 (5.4G) is the max link rate be supported. This patch
uses the actual limit specified by DT and removes the artificial
limitation to 5.4 Gbps. Supporting HBR3 is a consequence of that.
Changes in v2:
-- add max link rate from dtsi
Changes in v3:
-- parser max_data_lanes and
Add capability to parser data-lanes as property of dp_out endpoint.
Also retain the original capability to parser data-lanes as property
of mdss_dp node to handle legacy case.
Changes in v6:
-- first patch after split parser patch into two
Changes in v7:
-- check "data-lanes" from endpoint first
Changes in v6:
-- second patch after split parser patch into two patches
Changes in v7:
-- without checking cnt against DP_MAX_NUM_DP_LANES to retrieve link rate
Changes in v9:
-- separate parser link-frequencies out of data-lanes
Changes in v10:
-- add dp_parser_link_frequencies()
Changes in
To increase the flexibility of supporting different DP main link configuration
at different platform, add both data-lanes and link-frequencies property
into endpoint so that different platform can specify its own main link
combination of both data lanes and max supported link rate.
Changes in v7:
Move data-lanes property from mdss_dp node to dp_out endpoint. Also
add link-frequencies property into dp_out endpoint as well. The last
frequency specified at link-frequencies will be the max link rate
supported by DP.
Changes in v5:
-- revert changes at sc7180.dtsi and sc7280.dtsi
-- add _out
Add DP both data-lanes and link-frequencies property to dp_out endpoint and
support
functions to DP driver.
Kuogee Hsieh (5):
arm64: dts: qcom: add data-lanes and link-freuencies into dp_out
endpoint
dt-bindings: msm/dp: add data-lanes and link-frequencies property
drm/msm/dp: parse
kfree() & vfree() internally perform NULL check on the pointer handed
to it and take no action if it indeed is NULL. Hence there is no need
for a pre-check of the memory pointer before handing it to
kfree()/vfree().
Issue reported by ifnullfree.cocci Coccinelle semantic patch script.
On Tue, Dec 27, 2022 at 01:30:53PM +0530, Deepak R Varma wrote:
> Using DEFINE_SIMPLE_ATTRIBUTE macro with the debugfs_create_file()
> function adds the overhead of introducing a proxy file operation
> functions to wrap the original read/write inside file removal protection
> functions. This adds
On Tue, Dec 27, 2022 at 10:40 AM Alex Deucher wrote:
>
> On Sun, Dec 25, 2022 at 10:31 AM Christian König
> wrote:
> >
> > Am 24.12.22 um 10:34 schrieb Thomas Zimmermann:
> > > Hi
> > >
> > > Am 22.12.22 um 19:30 schrieb Mario Limonciello:
> > >> One of the first thing that KMS drivers do during
https://bugzilla.kernel.org/show_bug.cgi?id=216840
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
On Sun, Dec 25, 2022 at 09:55:08PM +0300, Alexey Lukyanchuk wrote:
> dell wyse 3040 doesn't peform poweroff properly, but instead remains in
> turned power on state.
okay, the motivation is explained in the commit msg..
> Additional mutex_lock and
> intel_crtc_wait_for_next_vblank
> feature
On Fri, 23 Dec 2022, Tvrtko Ursulin wrote:
> On 23/12/2022 12:18, Andi Shyti wrote:
>> From: Chris Wilson
>>
>> On Haswell, in particular, we see an issue where resets fails because
>> the engine resumes from an incorrect RING_HEAD. Since the RING_HEAD
>> doesn't point to the remaining requests
Use macros for 64-bit divisions and shifts. This allows compile-testing
this driver on 32-bit arches, so enable it.
Signed-off-by: Sean Anderson
---
Changes in v2:
- Use BIT_ULL
drivers/gpu/drm/hisilicon/kirin/Kconfig | 2 +-
drivers/gpu/drm/hisilicon/kirin/dw_drm_dsi.c| 10
On Sun, Dec 25, 2022 at 10:31 AM Christian König
wrote:
>
> Am 24.12.22 um 10:34 schrieb Thomas Zimmermann:
> > Hi
> >
> > Am 22.12.22 um 19:30 schrieb Mario Limonciello:
> >> One of the first thing that KMS drivers do during initialization is
> >> destroy the system firmware framebuffer by means
On Thu, Dec 8, 2022 at 1:08 PM Jacek Lawrynowicz
wrote:
>
> The IPC driver is used to send and receive messages to/from firmware
> running on the VPU.
>
> The only supported IPC message format is Job Submission Model (JSM)
> defined in vpu_jsm_api.h header.
>
> Co-developed-by: Andrzej Kacprowski
Hi, Nathan:
nathan.lu 於 2022年12月6日 週二 上午10:01寫道：
>
> From: Nathan Lu
>
> modify VDOSYS0 display device tree Documentations for MT8188.
Applied to mediatek-drm-next [1], thanks.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/chunkuang.hu/linux.git/log/?h=mediatek-drm-next
Regards,
On Tue, Dec 27, 2022 at 3:46 PM Greg KH wrote:
>
> On Tue, Dec 27, 2022 at 02:04:14PM +0200, Oded Gabbay wrote:
> > On Tue, Dec 27, 2022 at 9:26 AM Greg KH wrote:
> > >
> > > On Mon, Dec 26, 2022 at 11:32:26PM +0200, Oded Gabbay wrote:
> > > > Move the habanalabs.h uapi file from
On Tue, Dec 27, 2022 at 02:04:14PM +0200, Oded Gabbay wrote:
> On Tue, Dec 27, 2022 at 9:26 AM Greg KH wrote:
> >
> > On Mon, Dec 26, 2022 at 11:32:26PM +0200, Oded Gabbay wrote:
> > > Move the habanalabs.h uapi file from include/uapi/misc to
> > > include/uapi/drm, and rename it to
On Tue, Dec 27, 2022 at 9:26 AM Greg KH wrote:
>
> On Mon, Dec 26, 2022 at 11:32:26PM +0200, Oded Gabbay wrote:
> > Move the habanalabs.h uapi file from include/uapi/misc to
> > include/uapi/drm, and rename it to habanalabs_accel.h.
> >
> > This is required before moving the actual driver to the
Hello,
On Fri, Dec 23, 2022 at 03:33:40PM +, Rayyan Ansari wrote:
> On 25/10/2022 16:37, Diogo Ivo wrote:
> > +config DRM_PANEL_JDI_LPM102A188A
> > + tristate "JDI LPM102A188A DSI panel"
> > + depends on OF && GPIOLIB
> > + depends on DRM_MIPI_DSI
> > + depends on
From: Kamil Trzciński
The driver is for panels based on the Himax HX8394 controller, such as the
HannStar HSD060BHW4 720x1440 TFT LCD panel that uses a MIPI-DSI interface.
Signed-off-by: Kamil Trzciński
Co-developed-by: Ondrej Jirman
Signed-off-by: Ondrej Jirman
Co-developed-by: Javier
Add myself as maintainer for the driver and devicetree bindings schema.
Signed-off-by: Javier Martinez Canillas
---
(no changes since v1)
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2e832cf29bec..175d72203fb6 100644
--- a/MAINTAINERS
From: Ondrej Jirman
The phone's display is using Hannstar LCD panel, and Goodix based
touchscreen. Support it.
Signed-off-by: Ondrej Jirman
Co-developed-by: Martijn Braam
Signed-off-by: Martijn Braam
Co-developed-by: Kamil Trzciński
Signed-off-by: Kamil Trzciński
Signed-off-by: Javier
This series add support for the display present in the PinePhone Pro.
Patch #1 adds a driver for panels using the Himax HX8394 panel controller,
such as the HSD060BHW4 720x1440 TFT LCD panel present in the PinePhone Pro.
Patch #2 adds a devicetree binding schema for this driver and patch #3 adds
Add device tree bindings for panels based on the Himax HX8394 controller,
such as the HannStar HSD060BHW4 720x1440 TFT LCD panel that is connected
through a MIPI-DSI video interface.
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Krzysztof Kozlowski
---
Changes in v3:
- Fix example
Hello Krzysztof,
On 12/27/22 08:44, Krzysztof Kozlowski wrote:
[...]
>> +required:
>> + - compatible
>> + - vcc-supply
>> + - iovcc-supply
>> + - port
>
> Does not look like you tested the bindings. Please run `make
> dt_binding_check` (see
>
https://bugzilla.kernel.org/show_bug.cgi?id=205089
--- Comment #52 from milasud...@gmail.com ---
I should mention that disabling disabling AMP/DOCP does not solve the issue.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=205089
milasud...@gmail.com changed:
What|Removed |Added
CC||milasud...@gmail.com
--- Comment
MT8195 have two mmsys. Modify drm for MT8195 multi-mmsys support.
The two mmsys (vdosys0 and vdosys1) will bring up two drm drivers,
only one drm driver register as the drm device.
Each drm driver binds its own component. The last bind drm driver
allocates and registers the drm device to drm core.
Add driver data of mt8195 vdosys1 to mediatek-drm.
Signed-off-by: Nancy.Lin
Reviewed-by: AngeloGioacchino Del Regno
Reviewed-by: CK Hu
Tested-by: AngeloGioacchino Del Regno
Tested-by: Bo-Chen Chen
---
drivers/gpu/drm/mediatek/mtk_drm_drv.c | 17 -
1 file changed, 16
This is a preparation for adding support for the ovl_adaptor sub driver
Ovl_adaptor is a DRM sub driver, which doesn't have dma dev. Add
dma_dev_get function for getting representative dma dev in ovl_adaptor.
Signed-off-by: Nancy.Lin
Reviewed-by: AngeloGioachino Del Regno
Reviewed-by: CK Hu
Add ovl_adaptor driver for MT8195.
Ovl_adaptor is an encapsulated module and designed for simplified
DRM control flow. This module is composed of 8 RDMAs, 4 MERGEs and
an ETHDR. Two RDMAs merge into one layer, so this module support 4
layers.
Signed-off-by: Nancy.Lin
Reviewed-by: Chun-Kuang Hu
Add drm ovl_adaptor sub driver. Bring up ovl_adaptor sub driver if
the component exists in the path.
Signed-off-by: Nancy.Lin
Reviewed-by: AngeloGioacchino Del Regno
Reviewed-by: CK Hu
Tested-by: AngeloGioacchino Del Regno
Tested-by: Bo-Chen Chen
Tested-by: Nícolas F. R. A. Prado
---
The hardware path of vdosys1 with DPTx output need to go through by several
modules, such as, OVL_ADAPTOR and MERGE.
Add DRM and these modules support by the patches below:
Changes in v29:
- rebase to next-20221226
- fix reviewer comment in v28
- keep original flow if comp node not found in
Add vdosys1 ETHDR definition.
Signed-off-by: Nancy.Lin
Reviewed-by: Chun-Kuang Hu
Reviewed-by: AngeloGioacchino Del Regno
Reviewed-by: Krzysztof Kozlowski
Tested-by: AngeloGioacchino Del Regno
---
.../display/mediatek/mediatek,ethdr.yaml | 188 ++
1 file changed, 188
ETHDR is a part of ovl_adaptor.
ETHDR is designed for HDR video and graphics conversion in the external
display path. It handles multiple HDR input types and performs tone
mapping, color space/color format conversion, and then combine
different layers, output the required HDR or SDR signal to the
Using DEFINE_SIMPLE_ATTRIBUTE macro with the debugfs_create_file()
function adds the overhead of introducing a proxy file operation
functions to wrap the original read/write inside file removal protection
functions. This adds significant overhead in terms of introducing and
managing the proxy
82 matches
Mail list logo
