Hi Dmitry
Sorry for the late response.
On 10/31/2022 5:20 PM, Dmitry Baryshkov wrote:
On 28/10/2022 01:22, Abhinav Kumar wrote:
On 10/27/2022 10:35 AM, Dmitry Baryshkov wrote:
On 22/09/2022 03:49, Abhinav Kumar wrote:
Re-arrange the dsi_calc_pclk method to two helpers, one to
compute the
Downstream calls this num_enc yet the DSC patches introduced a new
num_dsc struct member, leaving num_enc effectively unused.
Fixes: 7e9cc175b159 ("drm/msm/disp/dpu1: Add support for DSC in topology")
Signed-off-by: Marijn Suijten
---
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 9 -
According to downstream the value to use for WORD_COUNT is
bytes_per_pkt, which denotes the number of bytes in a packet based on
how many slices have been configured by the panel driver times the
width of a slice times the number of bytes per pixel.
The DSC panels seen thus far use one byte per
This preliminary Display Stream Compression support package for
(initially tested on) sm8[12]50 is based on comparing DSC behaviour
between downstream and mainline. Some new callbacks are added (for
binding blocks on active CTLs), logic bugs are corrected, zeroed struct
members are now assigned
Active CTLs have to configure what DSC block(s) have to be enabled, and
what DSC block(s) have to be flushed; this value was initialized to zero
resulting in the necessary register writes to never happen (or would
write zero otherwise). This seems to have gotten lost in the DSC v4->v5
series
These DSC blocks on CTL V1 need to set its corresponding PINGPONG block
index in a hardware register to configure where to send pixel output to,
via the newly-added DPU_DSC_OUTPUT_CTRL feature flag.
Signed-off-by: Marijn Suijten
Reviewed-by: Dmitry Baryshkov
Reviewed-by: Abhinav Kumar
---
All V1 CTL blocks (active CTLs) explicitly bind the pixel output from a
DSC block to a PINGPONG block by setting the PINGPONG index in a DSC
hardware register.
Signed-off-by: Marijn Suijten
Reviewed-by: Dmitry Baryshkov
Reviewed-by: Abhinav Kumar
---
Resource allocation of DSC blocks should behave more like LMs and CTLs
where NULL resources (based on initial hw_blk creation via definitions
in the catalog) are skipped ^1. The current hardcoded mapping of DSC
blocks however means that resource allocation shouldn't succeed at all
when the DSC
According to downstream /and the comment copied from it/ this comparison
should be the other way around. In other words, when the panel driver
requests to use more slices per packet than what could be sent over this
interface, it is bumped down to only use a single slice per packet (and
strangely
In the event that the topology requests resources that have not been
created by the system (because they are typically not represented in
dpu_mdss_cfg ^1), the resource(s) in global_state (in this case DSC
blocks) remain NULL but will still be returned out of
dpu_rm_get_assigned_resources, where
Force PXP configs on for CI testing to trigger full subtests
in IGT's gem_pxp as opposed to the partial "unsupported hw substests".
Signed-off-by: Alan Previn
---
drivers/gpu/drm/i915/Kconfig | 2 +-
drivers/misc/mei/pxp/Kconfig | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git
A driver bug was recently discovered where the security firmware was
receiving internal HW signals indicating that session key expirations
had occurred. Architecturally, the firmware was expecting a response
from the GuC to acknowledge the event with the firmware side.
However the OS was in a
From: Alexander Usyskin
Async runtime resume is not possible while system is suspending.
The power management subsystem resumes device only in the
suspend phase, not in the prepare phase.
Force resume device in prepare to allow drivers on mei bus
to communicate in prepare callbacks.
From: Alexander Usyskin
Add device link with i915 as consumer and mei_pxp as supplier
to ensure proper ordering of power flows.
V2: condition on absence of heci_pxp to filter out DG
Signed-off-by: Alexander Usyskin
---
drivers/gpu/drm/i915/pxp/intel_pxp_tee.c | 7 +++
1 file changed, 7
During suspend flow, i915 currently achors' on the pm_suspend_prepare
callback as the location where we quiesce the entire GPU and perform
all necessary cleanup in order to go into suspend. PXP is also called
during this time to perform the arbitration session teardown (with
the assurance no
A gap was recently discovered where if an application did not
invalidate all of the stream keys (intentionally or not), and the
driver did a full PXP global teardown on the GT subsystem, we
find that future session creation would fail on the security
firmware's side of the equation. i915 is the
From: Alexander Usyskin
Client on bus have only one vtag map slot and should disregard the vtag
value when cleaning pending read flag.
Fixes read flow control message unexpectedly generated when
clent on bus send messages with different vtags.
Signed-off-by: Alexander Usyskin
---
A customer issue was recently discovered and in the process a
gap in i915's PXP interaction with HW+FW architecure was also
realized. This series adds those missing pieces.
This fix includes changes where i915 calls into the mei
component interface in order to submit requests to the security
On Wed, Dec 21, 2022 at 12:22 PM Johan Jonker wrote:
>
> Fix clock properties from the common snps,dw-mipi-dsi.yaml file,
> as they don't match with what is used on the SoCs.
>
> Signed-off-by: Johan Jonker
> ---
> .../display/bridge/snps,dw-mipi-dsi.yaml | 16 +++-
> 1 file
On Wed, Dec 21, 2022 at 12:22 PM Johan Jonker wrote:
>
> Convert dw_mipi_dsi_rockchip.txt to yaml.
>
> Changed:
> add clock-master property
> file name
> requirements
>
> Signed-off-by: Johan Jonker
> ---
> .../display/rockchip/dw_mipi_dsi_rockchip.txt | 94 --
>
On Wed, Dec 21, 2022 at 12:23 PM Johan Jonker wrote:
>
> Convert fcs,fusb302.txt to yaml.
>
> Changed:
> Add vbus-supply property
>
> Signed-off-by: Johan Jonker
> ---
> .../devicetree/bindings/usb/fcs,fusb302.txt | 34 --
> .../devicetree/bindings/usb/fcs,fusb302.yaml | 66
Hi Mark, Sean, (and dri-devel)
On Wed, Dec 14, 2022 at 07:04:37PM -0800, Brian Norris wrote:
> On Tue, Dec 13, 2022 at 04:51:11PM +, Mark Brown wrote:
> > On Tue, Dec 13, 2022 at 05:56:30AM -0800, KernelCI bot wrote:
> >
> > The KernelCI bisection bot found regressions in at least two KMS
Applied. Thanks!
Alex
On Mon, Dec 19, 2022 at 9:22 AM Jiapeng Chong
wrote:
>
> The function dmub_outbox_irq_info_funcs is defined in the
> irq_service_dcn201.c file, but not called elsewhere, so remove this
> unused function.
>
>
Hi Dave, Daniel,
Fixes for 6.2.
The following changes since commit 38624d2c972e7692ca59d0d3b97741a3313addb3:
Merge tag 'drm-intel-next-fixes-2022-12-15' of
git://anongit.freedesktop.org/drm/drm-intel into drm-next (2022-12-20 15:43:14
+1000)
are available in the Git repository at:
On 12/20/22 13:11, Thomas Zimmermann wrote:
> Add dedicated helper to convert from XRGB to ARGB. Sets
> all alpha bits to make pixels fully opaque.
>
> v2:
> * use cpubuf_to_le32()
> * type fixes
>
> Signed-off-by: Thomas Zimmermann
> Reviewed-by: Javier Martinez Canillas
>
On 12/20/22 13:11, Thomas Zimmermann wrote:
> Change the source-buffer type of le32buf_to_cpu() to __le32* to
> reflect endianness. Result buffers are converted to local endianness,
> so instantiate them from regular u8 or u32 types.
>
> Signed-off-by: Thomas Zimmermann
Reviewed-by: Maíra Canal
On Tue, Dec 20, 2022, Jianhua Lu wrote:
>
> Add support for Kinetic KTZ8866 backlight, which is used in
> Xiaomi tablet, Mi Pad 5 series. This driver lightly based on
> downstream implementation [1].
> [1]
>
On 12/20/22 13:11, Thomas Zimmermann wrote:> Fix to-RGB565 conversion
helpers to store the result in little-
> endian byte order. Update test cases as well.
>
> Signed-off-by: Thomas Zimmermann
Reviewed-by: Maíra Canal
Best Regards,
- Maíra Canal
> ---
> drivers/gpu/drm/drm_format_helper.c
Hi,
if i enable PROVE_LOCKING on the Raspberry Pi 3 B+
(arm/multi_v7_defconfig) using v6.1 (didn't test older versions) i'm
getting the following warning:
[ 204.043396] WARNING: CPU: 2 PID: 42 at
drivers/gpu/drm/drm_modeset_lock.c:276 drm_modeset_drop_locks+0x6c/0x70
[ 204.043426] Modules
On 21/12/2022 16:10, Vinod Polimera wrote:
-Original Message-
From: Dmitry Baryshkov
Sent: Wednesday, December 14, 2022 9:05 PM
To: Vinod Polimera (QUIC) ; dri-
de...@lists.freedesktop.org; linux-arm-...@vger.kernel.org;
freedr...@lists.freedesktop.org; devicet...@vger.kernel.org
Cc:
On 12/20/22 13:11, Thomas Zimmermann wrote:
> Convert test input for format helpers from host byte order to
> little-endian order. The current code does it the other way around,
> but there's no effective difference to the result.
>
> Signed-off-by: Thomas Zimmermann
Reviewed-by: Maíra Canal
On 12/20/22 13:11, Thomas Zimmermann wrote:
> RGB888 is different than the other formats as most of its pixels are
> unaligned and therefore helper functions do not use endianness conversion
> helpers. Comment on this in the source code.
>
> Signed-off-by: Thomas Zimmermann
Reviewed-by: Maíra
From: John Harrison
In the case where a firmware file is too large (e.g. someone
downloaded a web page ASCII dump from github...), the firmware object
is released but the pointer is not zerod. If no other firmware file
was found then release would be called again leading to a double kfree.
From: John Harrison
A static analyser was complaining about not checking for null
pointers. However, the location of the complaint can only be reached
in the first place if said pointer is non-null. Basically, if we are
using a v69 GuC then the descriptor pool is guaranteed to be alocated
at
From: John Harrison
The CI results for the 'fast request' patch set (enables error return
codes for fire-and-forget H2G messages) hit an issue with the KMD
sending context submission requests on an invalid context. That was
caused by a fault injection probe failing the context creation of a
From: John Harrison
Fix a bunch of assorted issues with firmware loading and GuC
intialisation.
Signed-off-by: John Harrison
John Harrison (3):
drm/i915/guc: Fix missing return code checks in submission init
drm/i915/guc: Fix a static analysis warning
drm/i915/uc: Fix two issues with
Steven Rostedt writes:
> [
> Linus,
>
> I ran the script against your latest master branch:
> commit b6bb9676f2165d518b35ba3bea5f1fcfc0d969bf
>
> As the timer_shutdown*() code is now in your tree, I figured
> we can start doing the conversions. At least add the trivial ones
>
The hclk is not used in the dw-mipi-dsi-rockchip.c driver,
so remove hclk from the rk356x.dtsi dsi node.
Signed-off-by: Johan Jonker
---
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk356x.dtsi
'vbus-supply' does not match any of the regexes in rk3566-box-demo.dts
in the usb2phy0_otg node, so rename vbus-supply to phy-supply.
Signed-off-by: Johan Jonker
---
arch/arm64/boot/dts/rockchip/rk3566-box-demo.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Use generic node name for rk3399.dtsi dsi node.
With the conversion of rockchip,dw-mipi-dsi.yaml a port@1 node
is required, so add a node with label mipi_out.
Signed-off-by: Johan Jonker
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 12 ++--
1 file changed, 10 insertions(+), 2
With the conversion of rockchip,dw-mipi-dsi.yaml a port@1 node
is required, so add a node with label dsi_out.
Also add label dsi_in to port@0.
Signed-off-by: Johan Jonker
---
arch/arm64/boot/dts/rockchip/px30.dtsi | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
With the conversion of rockchip,lvds.yaml a port@1 node
is required, so add a node with label lvds_out.
Also add label lvds_in to port@0.
Signed-off-by: Johan Jonker
---
Changed V5:
rename title
add label lvds_in
---
arch/arm64/boot/dts/rockchip/px30.dtsi | 6 +-
1 file changed, 5
With the conversion of rockchip,lvds.yaml a port@1 node
is required, so add a node with label lvds_out.
Signed-off-by: Johan Jonker
---
Changed V5:
rename title
---
arch/arm/boot/dts/rk3288.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi
Use generic node name for rk3288.dtsi dsi node.
With the conversion of rockchip,dw-mipi-dsi.yaml a port@1 node
is required, so add a node with label mipi_out.
Signed-off-by: Johan Jonker
---
arch/arm/boot/dts/rk3288.dtsi | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
Convert fcs,fusb302.txt to yaml.
Changed:
Add vbus-supply property
Signed-off-by: Johan Jonker
---
.../devicetree/bindings/usb/fcs,fusb302.txt | 34 --
.../devicetree/bindings/usb/fcs,fusb302.yaml | 66 +++
2 files changed, 66 insertions(+), 34 deletions(-)
delete
Convert dw_mipi_dsi_rockchip.txt to yaml.
Changed:
add clock-master property
file name
requirements
Signed-off-by: Johan Jonker
---
.../display/rockchip/dw_mipi_dsi_rockchip.txt | 94 --
.../rockchip/rockchip,dw-mipi-dsi.yaml| 173 ++
2 files changed, 173
Fix clock properties from the common snps,dw-mipi-dsi.yaml file,
as they don't match with what is used on the SoCs.
Signed-off-by: Johan Jonker
---
.../display/bridge/snps,dw-mipi-dsi.yaml | 16 +++-
1 file changed, 3 insertions(+), 13 deletions(-)
diff --git
Add new converted rockchip,lvds.yaml to grf.yaml file.
Prepare for more SoCs with lvds output.
Signed-off-by: Johan Jonker
Reviewed-by: Rob Herring
---
Changed V5:
Drop the quotes
---
.../devicetree/bindings/soc/rockchip/grf.yaml | 24 +++
1 file changed, 14 insertions(+),
Convert rockchip-lvds.txt to YAML.
Changed:
Add power-domains property.
Requirements between PX30 and RK3288
Signed-off-by: Johan Jonker
Reviewed-by: Rob Herring
---
Changed V3:
Filename matching compatible style
Drop "Regulator phandle for "
Specify properties and requirements per
If PXP arb-session is being attempted on older hardware SKUs or
on hardware with older, unsupported, firmware versions, then don't
report the failure with a drm_error. Instead, look specifically for
the API-version error reply and drm_dbg that reply. In this case, the
user-space will eventually
On Wed, 2022-12-21 at 12:21 +0200, Jani Nikula wrote:
> On Tue, 20 Dec 2022, Alan Previn wrote:
> >
Alan:[snip]
> > +++ b/drivers/gpu/drm/i915/pxp/intel_pxp_tee.c
> > @@ -298,6 +298,11 @@ int intel_pxp_tee_cmd_create_arb_session(struct
> > intel_pxp *pxp,
> >
> > if (ret)
> >
On 12/21/2022 8:13 PM, Ulf Hansson wrote:
> On Tue, 20 Dec 2022 at 08:44, Akhil P Oommen wrote:
>> From: Ulf Hansson
>>
>> Some genpd providers doesn't ensure that it has turned off at hardware.
>> This is fine until the consumer really requires during some special
>> scenarios that the power
As per the recommended recovery sequence of adreno gpu, cx gdsc should
collapse at hardware before it is turned back ON. This helps to clear
out the stale states in hardware before it is reinitialized. Use the
genpd notifier along with the newly introduced
dev_pm_genpd_synced_poweroff() api to
Remove the unused 'reset' interface which was supposed to help to ensure
that cx gdsc has collapsed during gpu recovery. This is was not enabled
so far due to missing gpucc driver support. Similar functionality using
genpd framework will be implemented in the upcoming patch.
This effectively
When a device has multiple power domains, dev->power_domain is left
empty during probe. That didn't cause any issue so far because we are
freeloading on smmu driver's vote on cx gdsc. Instead of that, create
a device_link between cx genpd device and gmu device to keep a vote from
gpu driver.
Add support for the newly added 'synced_poweroff' genpd flag. This allows
some clients (like adreno gpu driver) to request gdsc driver to ensure
a votable gdsc (like gpucc cx gdsc) has collapsed at hardware.
Signed-off-by: Akhil P Oommen
---
(no changes since v3)
Changes in v3:
- Rename the
From: Ulf Hansson
Some genpd providers doesn't ensure that it has turned off at hardware.
This is fine until the consumer really requires during some special
scenarios that the power domain collapse at hardware before it is
turned ON again.
An example is the reset sequence of Adreno GPU which
This is a rework of [1] using genpd instead of 'reset' framework.
As per the recommended reset sequence of Adreno gpu, we should ensure that
gpucc-cx-gdsc has collapsed at hardware to reset gpu's internal hardware states.
Because this gdsc is implemented as 'votable', gdsc driver doesn't poll
https://bugzilla.kernel.org/show_bug.cgi?id=211425
Grigorije (grigorij...@gmail.com) changed:
What|Removed |Added
CC||grigorij...@gmail.com
On Wed, 21 Dec 2022 at 15:52, Luben Tuikov wrote:
>
> On 2022-12-21 10:34, Mike Lothian wrote:
> > On Fri, 14 Oct 2022 at 09:47, Christian König
> > wrote:
> >>
> >> Entirely remove the sync obj in the job.
> >>
> >> Signed-off-by: Christian König
> >> ---
> >>
On 2022-12-21 10:34, Mike Lothian wrote:
> On Fri, 14 Oct 2022 at 09:47, Christian König
> wrote:
>>
>> Entirely remove the sync obj in the job.
>>
>> Signed-off-by: Christian König
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 21 ++---
>>
https://gitlab.freedesktop.org/drm/amd/-/issues/2309
On Wed, 21 Dec 2022 at 15:34, Mike Lothian wrote:
>
> On Fri, 14 Oct 2022 at 09:47, Christian König
> wrote:
> >
> > Entirely remove the sync obj in the job.
> >
> > Signed-off-by: Christian König
> > ---
> >
On Wed, 2022-12-21 at 13:05 +0100, Thomas Zimmermann wrote:
> Hi
>
> Am 21.12.22 um 12:19 schrieb Jouni Högander:
> > Checking if damage clip is valid is common to all fb helpers.
> > Makes more sense to check it in higher level than adding into
> > all helpers.
>
> It was a deliberate decision
On Fri, 14 Oct 2022 at 09:47, Christian König
wrote:
>
> Entirely remove the sync obj in the job.
>
> Signed-off-by: Christian König
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 21 ++---
> drivers/gpu/drm/amd/amdgpu/amdgpu_cs.h | 2 ++
>
On 21/12/2022 16:15, Jianhua Lu wrote:
> On Wed, Dec 21, 2022 at 04:03:44PM +0100, Krzysztof Kozlowski wrote:
>> On 21/12/2022 14:24, Jianhua Lu wrote:
>>> Add Kinetic KTZ8866 backlight binding documentation.
>>>
>>> Signed-off-by: Jianhua Lu
>>
>> Do not resend. You need to fix everything, test
On 19/12/2022 17:10, Rob Clark wrote:
> On Mon, Dec 19, 2022 at 6:02 AM Steven Price wrote:
>>
>> panfrost_gem_create_with_handle() previously returned a BO but with the
>> only reference being from the handle, which user space could in theory
>> guess and release, causing a use-after-free.
Since RoQ size differs between generations, calculate dynamically the
RoQ size while capturing coredump.
Signed-off-by: Akhil P Oommen
---
(no changes since v1)
drivers/gpu/drm/msm/adreno/a6xx_gpu_state.c | 11 ++-
drivers/gpu/drm/msm/adreno/a6xx_gpu_state.h | 17 ++---
2
Update gpu coredump for a660/a650 family of gpus with the extra
information available.
Signed-off-by: Akhil P Oommen
---
(no changes since v1)
drivers/gpu/drm/msm/adreno/a6xx.xml.h | 18 +++
drivers/gpu/drm/msm/adreno/a6xx_gpu_state.c | 50 -
Ensure that we do drm_dev_put() when there is an early return in
msm_drm_init().
Signed-off-by: Akhil P Oommen
---
(no changes since v1)
drivers/gpu/drm/msm/disp/msm_disp_snapshot.c | 3 +++
drivers/gpu/drm/msm/msm_drv.c| 11 +++
2 files changed, 10 insertions(+), 4
Fix the below kernel panic due to null pointer access:
[ 18.504431] Unable to handle kernel NULL pointer dereference at virtual
address 0048
[ 18.513464] Mem abort info:
[ 18.516346] ESR = 0x9605
[ 18.520204] EC = 0x25: DABT (current EL), IL = 32 bits
[
On 21/12/2022 14:24, Jianhua Lu wrote:
> Add Kinetic KTZ8866 backlight binding documentation.
>
> Signed-off-by: Jianhua Lu
Do not resend. You need to fix everything, test and send a new patchset
(entire) with the changelog.
Best regards,
Krzysztof
On Tue, 20 Dec 2022 at 08:44, Akhil P Oommen wrote:
>
> From: Ulf Hansson
>
> Some genpd providers doesn't ensure that it has turned off at hardware.
> This is fine until the consumer really requires during some special
> scenarios that the power domain collapse at hardware before it is
> turned
> -Original Message-
> From: Dmitry Baryshkov
> Sent: Wednesday, December 14, 2022 9:05 PM
> To: Vinod Polimera (QUIC) ; dri-
> de...@lists.freedesktop.org; linux-arm-...@vger.kernel.org;
> freedr...@lists.freedesktop.org; devicet...@vger.kernel.org
> Cc: linux-ker...@vger.kernel.org;
' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Thomas-Zimmermann/drm-Fix-color-format-selection-in-fbdev-emulation/20221221-001529
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link
https://bugzilla.kernel.org/show_bug.cgi?id=216806
--- Comment #4 from Balazs Vinarz (viniba...@gmail.com) ---
Just some more information to share here. I gave it another try, and the
console freezes exactly at the moment when drm enables the kernel modesetting.
[6.329371] [drm] amdgpu
On Wed, 21 Dec 2022 15:02:16 +0800, Jianhua Lu wrote:
> Add device tree bindings for the Kinetic KTZ8866 backlight driver.
>
> Signed-off-by: Jianhua Lu
> ---
> .../leds/backlight/kinetic,ktz8866.yaml | 37 +++
> 1 file changed, 37 insertions(+)
> create mode 100644
>
' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Thomas-Zimmermann/drm-Fix-color-format-selection-in-fbdev-emulation/20221221-001529
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link
Hi
Am 21.12.22 um 12:19 schrieb Jouni Högander:
Checking if damage clip is valid is common to all fb helpers.
Makes more sense to check it in higher level than adding into
all helpers.
It was a deliberate decision to separate damage clipping and dirty
updates; done in [1]. Clipping is an
submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Siddh-Raman-Pant/drm-Remove-usage-of-deprecated-DRM_-macros/20221221-113133
patch link:
https://lore.kernel.org/r
Hi
Am 21.12.22 um 12:19 schrieb Jouni Högander:
After splitting generic drm_fb_helper into it's own file it's left to
helper implementation to have fb_dirty function. Currently intel
fb doesn't have it. This is causing problems to features (PSR, FBC, DRRS)
relying on dirty callback.
Implement
Checking if damage clip is valid is common to all fb helpers.
Makes more sense to check it in higher level than adding into
all helpers.
Cc: Ville Syrjälä
Cc: Thomas Zimmermann
Cc: Jani Nikula
Signed-off-by: Jouni Högander
---
drivers/gpu/drm/drm_fb_helper.c | 4
After splitting generic drm_fb_helper into it's own file it's left to
helper implementation to have fb_dirty function. Currently intel
fb doesn't have it. This is causing problems to features (PSR, FBC, DRRS)
relying on dirty callback.
Implement simple fb_dirty callback to deliver notifications
This patch set is fixing Intel fb console update issues introduced by
splitting generic drm_fb_helper into it's own file.
Also damage clip check moved to higher level to share it between fb
helpers.
Cc: Ville Syrjälä
Cc: Thomas Zimmermann
Cc: Jani Nikula
Jouni Högander (2):
drm/i915/fbdev:
Add early console support for generic linear framebuffer devices.
This driver supports probing from cmdline early parameters
or from the device-tree using information in simple-framebuffer node.
The EFI functionality should be retained in whole.
The driver was disabled on ARM because of a bug in
This would make the next patch in series with this one to
show a clear diff, instead of just removing the previous
driver and creating a new one.
Signed-off-by: Markuss Broks
---
drivers/{firmware/efi => video/console}/earlycon.c | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename
Pass a pointer to device-tree node in case the driver probed from
OF. This makes early console drivers able to fetch options from
device-tree node properties.
Signed-off-by: Markuss Broks
---
drivers/tty/serial/earlycon.c | 3 +++
include/linux/serial_core.h | 1 +
2 files changed, 4
Make the EFI earlycon driver be suitable for any linear framebuffers.
This should be helpful for early porting of boards with no other means of
output, like smartphones/tablets. There seems to be an issue with early_ioremap
function on ARM32, but I am unable to find the exact cause. It appears the
Patch is:
Reviewed-by: Simon Ser
Hello Rob,
On Tue, Dec 20, 2022 at 12:19:48PM -0600, Rob Herring wrote:
> On Sat, Dec 17, 2022 at 07:38:06PM +0100, Uwe Kleine-König wrote:
> > On Fri, Dec 16, 2022 at 05:57:58PM -0600, Rob Herring wrote:
> > > On Fri, Dec 16, 2022 at 06:50:04PM +0100, Uwe Kleine-König wrote:
> > > > Hello,
> > >
On Tue, 20 Dec 2022, Alan Previn wrote:
> If PXP arb-session is being attempted on older hardware SKUs or
> on hardware with older, unsupported, firmware versions, then don't
> report the failure with a drm_error. Instead, look specifically for
> the API-version error reply and drm_dbg that
Hi Tomi,
On Wed, Dec 21, 2022 at 09:48:10AM +0200, Tomi Valkeinen wrote:
> On 19/12/2022 23:01, Laurent Pinchart wrote:
> > On Mon, Dec 19, 2022 at 04:01:35PM +0200, Tomi Valkeinen wrote:
> >> V3U is actually gen4, not gen3. The same IP is also used in the
> >> (not-yet-supported) V4H.
> >>
> >>
Hi, this is your Linux kernel regression tracker. The relevant code here
is not my area of expertise, nevertheless a few questions:
On 21.12.22 03:23, Kaiwan N Billimoria wrote:
> [REGRESSION] ?
> Testing with 6.1, I find the same issue - VirtualBox VMs seem to hang
> on boot, though the kernel
Hi
Am 21.12.22 um 11:00 schrieb Jani Nikula:
On Wed, 21 Dec 2022, Siddh Raman Pant wrote:
drm_print.h says DRM_DEBUG_DRIVER is deprecated.
Thus, use newer drm_dbg_driver().
Also fix the deprecation comment in drm_print.h which
mentions drm_dbg() instead of drm_dbg_driver().
Signed-off-by:
Hi
Am 21.12.22 um 10:49 schrieb Jani Nikula:
On Wed, 21 Dec 2022, Siddh Raman Pant wrote:
drm_print.h says DRM_INFO is deprecated.
Thus, use newer printing macros drm_info() and pr_info().
I think it's a bit odd some of the conversion is to pr_*() and some to
drm_*(NULL, ...) depending on
On Wed, 21 Dec 2022, Thomas Zimmermann wrote:
> Hi
>
> Am 20.12.22 um 21:16 schrieb Siddh Raman Pant:
>> This patchset aims to remove usages of deprecated DRM_* macros from the
>> files residing in drivers/gpu/drm root.
>>
>> In process, I found out that NULL as first argument of drm_dbg_*
On Wed, 21 Dec 2022, Siddh Raman Pant wrote:
> drm_print.h says DRM_DEBUG_DRIVER is deprecated.
> Thus, use newer drm_dbg_driver().
>
> Also fix the deprecation comment in drm_print.h which
> mentions drm_dbg() instead of drm_dbg_driver().
>
> Signed-off-by: Siddh Raman Pant
> ---
>
On Wed, 21 Dec 2022, Siddh Raman Pant wrote:
> drm_print.h says DRM_INFO is deprecated.
> Thus, use newer printing macros drm_info() and pr_info().
I think it's a bit odd some of the conversion is to pr_*() and some to
drm_*(NULL, ...) depending on the logging level etc.
Notably the pr_*()
On 21/12/2022 10:40, jianhua lu wrote:
> Thanks for review, I will resend this path.
Are you going to test it, before sending?
Best regards,
Krzysztof
On Wed, 21 Dec 2022, Siddh Raman Pant wrote:
> Comments say macros DRM_DEBUG_* are deprecated in favor of
> drm_dbg_*(NULL, ...), but they have broken support for it,
> as the macro will result in `(NULL) ? (NULL)->dev : NULL`.
What's wrong with that?
>
> Thus, fix them by casting input drm to
Hi
Am 20.12.22 um 21:16 schrieb Siddh Raman Pant:
This patchset aims to remove usages of deprecated DRM_* macros from the
files residing in drivers/gpu/drm root.
In process, I found out that NULL as first argument of drm_dbg_* wasn't
working, but it was listed as the alternative in deprecation
1 - 100 of 125 matches
Mail list logo
