Hi Liu Ying,
> -Original Message-
> From: Liu Ying
> Sent: 29 October 2024 06:17
> Subject: Re: [PATCH v4 08/13] dt-bindings: display: Document dual-link LVDS
> display common properties
>
> On 10/28/2024, Liu Ying wrote:
> > Dual-link LVDS displays receive odd pixels and even pixels se
Matthew Brost writes:
> On Thu, Oct 17, 2024 at 12:51:08PM +1100, Alistair Popple wrote:
>>
>> Matthew Brost writes:
>>
>> > On Wed, Oct 16, 2024 at 03:00:08PM +1100, Alistair Popple wrote:
>> >>
>> >> Matthew Brost writes:
>> >>
>> >> > Avoid multiple CPU page faults to the same device p
Hi Dmitry,
> Subject: Re: [PATCH v2 2/5] drm/virtio: Add a helper to map and note the
> dma addrs and lengths
> > +long virtgpu_dma_buf_import_sgt(struct virtio_gpu_mem_entry
> >> **ents,
> > + unsigned int *nents,
> > + struc
Thank you for your review, I missed how && work.
I will revise a patch that print only when cond is true.
sincerely,
Gyeyoung baek
On Tue, Oct 29, 2024 at 4:47 AM Lucas De Marchi
wrote:
>
> On Sun, Oct 27, 2024 at 01:57:52PM +0900, Gyeyoung Baek wrote:
> >In the previous code, there is build err
On 10/28/2024, Liu Ying wrote:
> Dual-link LVDS displays receive odd pixels and even pixels separately from
> dual LVDS links. One link receives odd pixels and the other receives even
> pixels. Some of those displays may also use only one LVDS link to receive
> all pixels, being odd and even agno
Add Cadence HDP-TX DisplayPort and HDMI PHY driver for i.MX8MQ.
Cadence HDP-TX PHY could be put in either DP mode or
HDMI mode base on the configuration chosen.
DisplayPort or HDMI PHY mode is configured in the driver.
Signed-off-by: Sandor Yu
Signed-off-by: Alexander Stein
---
v17->v18:
- fix
From: Alexander Stein
Add HDMI connector and connect it to MHDP output. Enable peripherals
for HDMI output.
Signed-off-by: Alexander Stein
---
v17->v18:
- replace lane-mapping with data-lanes
.../dts/freescale/imx8mq-tqma8mq-mba8mx.dts | 21 +++
arch/arm64/boot/dts/freescale
From: Alexander Stein
This adds DCSS + MHDP + MHDP PHY nodes. PHY mode (DP/HDMI) is selected
by the connector type connected to mhdp port@1 endpoint.
Signed-off-by: Alexander Stein
---
v17->v18:
*No change
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 68 +++
1 file changed
Add bindings for Freescale iMX8MQ DP and HDMI PHY.
Signed-off-by: Sandor Yu
Reviewed-by: Rob Herring
---
v9->v18:
*No change.
.../bindings/phy/fsl,imx8mq-dp-hdmi-phy.yaml | 51 +++
1 file changed, 51 insertions(+)
create mode 100644
Documentation/devicetree/bindings/phy/fsl
Add a new DRM DisplayPort and HDMI bridge driver for Candence MHDP8501
used in i.MX8MQ SOC. MHDP8501 could support HDMI or DisplayPort
standards according embedded Firmware running in the uCPU.
For iMX8MQ SOC, the DisplayPort/HDMI FW was loaded and activated by
SOC's ROM code. Bootload binary incl
The patch set initial support Cadence MHDP8501(HDMI/DP) DRM bridge
driver and Cadence HDP-TX PHY(HDMI/DP) driver for Freescale i.MX8MQ.
The patch set compose of DRM bridge drivers and PHY driver.
Both of them need by patch #1 and #2 to pass build.
DRM bridges driver patches:
#1: drm: bridge: C
Add bindings for Cadence MHDP8501 DisplayPort/HDMI bridge.
Signed-off-by: Sandor Yu
---
v17->v18:
- remove lane-mapping and replace it with data-lanes
- remove r-b tag as property changed.
v16->v17:
- Add lane-mapping property
v9->v16:
*No change
.../display/bridge/cdns,mhdp8501.yaml
Allow HDMI PHYs to be configured through the generic
functions through a custom structure added to the generic union.
The parameters added here are based on HDMI PHY
implementation practices. The current set of parameters
should cover the potential users.
Signed-off-by: Sandor Yu
Reviewed-by: D
Mailbox access functions in MHDP8546 will be share to other MHDP driver
and Cadence HDP-TX HDMI/DP PHY drivers.
Create a new MHDP helper driver and move all mailbox access functions into.
According the mailbox access sequence and type of security.
Six mailbox access API functions are introduced.
T
On 10/28/2024, Dmitry Baryshkov wrote:
> On Mon, Oct 28, 2024 at 11:12:00AM +, Biju Das wrote:
>> Hi Dmitry, Liu,
>>
>>> -Original Message-
>>> From: Dmitry Baryshkov
>>> Sent: 28 October 2024 10:20
>>> Subject: Re: [PATCH v4 00/13] Add ITE IT6263 LVDS to HDMI converter support
>>>
>>>
On 10/29/2024 3:48 PM, Li Huafei wrote:
> Fix the potential NULL pointer dereference on mem_ranges in
> amdgpu_discovery_get_nps_info(). Additionally, assign the output
> parameters nps_type and range_cnt after the kvzalloc() call to prevent
> modifying the output parameters in case of an error
On Sat, Oct 26, 2024 at 08:32:36AM +0200, Christophe JAILLET wrote:
> If an error occurs after allocating resources based on which
> "sharp,vcom-mode" is used, then these resources must be released, as
> already done in the .remove() function.
>
> Use 2 new devm_add_action_or_reset() for that and
Fix the potential NULL pointer dereference on mem_ranges in
amdgpu_discovery_get_nps_info(). Additionally, assign the output
parameters nps_type and range_cnt after the kvzalloc() call to prevent
modifying the output parameters in case of an error return.
Fixes: b194d21b9bcc ("drm/amdgpu: Use NPS
On 2024/10/28 22:33, Lazar, Lijo wrote:
>
>
> On 10/29/2024 3:29 AM, Li Huafei wrote:
>> Fix the potential NULL pointer dereference on mem_ranges in
>> amdgpu_discovery_get_nps_info(). Additionally, assign the output
>> parameters nps_type and range_cnt after the kvzalloc() call to prevent
>>
Maíra
- else
- shmem_obj = drm_gem_shmem_create(dev, unaligned_size);
-
if (IS_ERR(shmem_obj))
return ERR_CAST(shmem_obj);
bo = to_v3d_bo(&shmem_obj->base);
---
base-commit: dec9255a128e19c5fcc3bdb18175d78094cc624d
change-id: 20241028-v3d-1d254
Hi Piotr,
在 2024-10-28 14:42:28，"Andy Yan" 写道：
>
>Hi Piotr，
>Tested on top of Linux 6.12-rc5 with rk3566-box-demo in a buildroot +
> weston environment:
>weston --backend=drm-backend.so -i 0 --continue-without-input
>weston-simple-egl
>
> simple-egl will draw a triangle on the des
During GuC reset prepare, interrupt is disabled, if the interrupt
event already happens and is in progress, from interrupt event to
tasklet get running, there is alway some kind of latency. In long
latency case, it might have 2 rare race conditions:
1. Tasklet runs after IRQ flush, add request to q
Both devices lack a DisplayID 2.0 block and therefore do not advertise
themselves as HMDs.
See https://gitlab.freedesktop.org/drm/misc/kernel/-/issues/53
Signed-off-by: Sefa Eyeoglu
---
drivers/gpu/drm/drm_edid.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/drm_edid.c
On Mon, Oct 28, 2024 at 4:53 AM Mostafa Saleh wrote:
>
> Hi Rob,
>
> On Tue, Aug 27, 2024 at 11:17:08AM -0700, Rob Clark wrote:
> > From: Rob Clark
> >
> > This series extends io-pgtable-arm with a method to retrieve the page
> > table entries traversed in the process of address translation, and
From: Rob Clark
In the case of iova fault triggered devcore dumps, include additional
debug information based on what we think is the current page tables,
including the TTBR0 value (which should match what we have in
adreno_smmu_fault_info unless things have gone horribly wrong), and
the pagetabl
From: Rob Clark
This series extends io-pgtable-arm with a method to retrieve the page
table entries traversed in the process of address translation, and then
beefs up drm/msm gpu devcore dump to include this (and additional info)
in the devcore dump.
This is a respin of https://patchwork.freedes
On Mon, Oct 28, 2024 at 3:04 PM Jani Nikula wrote:
>
> drm_dev_register() already prints the same information on successful
> init. Remove the redundant prints.
>
> Signed-off-by: Jani Nikula
Acked-by: Alex Deucher
>
> ---
>
> Note: I prefer to merge this together with the next patch via
> drm
Hi again
On Monday, October 28th, 2024 at 5:40 PM, Piotr Zalewski
wrote:
> On Monday, October 28th, 2024 at 7:42 AM, Andy Yan andys...@163.com wrote:
>
> > Hi Piotr，
>
>
> Hi Andy
>
> > Tested on top of Linux 6.12-rc5 with rk3566-box-demo in a buildroot +
> > weston environment:
> > weston
On Mon, Oct 28, 2024 at 2:52 PM Jani Nikula wrote:
>
> The ivpu struct drm_driver has conditional initialization based on #ifdef
> DRIVER_DATE, which is never defined anywhere. Neither are the macros
> referenced within the block: DRIVER_DATE, DRIVER_MAJOR, DRIVER_MINOR,
> and DRIVER_PATCHLEVEL. W
Hi Gonzalo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-tip/drm-tip linus/master v6.12-rc5
next-20241028]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting
On Mon, Oct 28, 2024 at 1:06 AM Tomi Valkeinen
wrote:
>
> Hi,
>
> On 26/10/2024 07:52, Saravana Kannan wrote:
> > In attempting to optimize fw_devlink runtime, I introduced numerous cycle
> > detection bugs by foregoing cycle detection logic under specific
> > conditions. Each fix has further narr
We replaced our custom list of resolutions with the noedid list, which is
based on the VESA DMT standard, in the referenced fixes commit. The reason
for this was that the user can technically set any resolution they want by
using Autofit or the vmwgfxctl utility.
Unfortunately the Autofit feature
On 10/28/24 2:52 PM, Herve Codina wrote:
Hi Marek,
Hi,
On Sat, 26 Oct 2024 00:53:51 +0200
Marek Vasut wrote:
On 10/24/24 11:55 AM, Herve Codina wrote:
In some cases observed during ESD tests, the TI SN65DSI83 cannot recover
from errors by itself. A full restart of the bridge is needed
On Sun, Oct 27, 2024 at 01:57:52PM +0900, Gyeyoung Baek wrote:
In the previous code, there is build error.
if CONFIG_DRM_USE_DYNAMIC_DEBUG is set,
'drm_dbg' function is replaced with '__dynamic_func_call_cls',
which is replaced with a do while statement.
The problem is that,
XE_IOCTL_DBG uses th
Hi Louis,
On 28/10/24 08:01, Louis Chauvet wrote:
On 28/10/24 - 07:17, Maíra Canal wrote:
Hi Louis,
On 28/10/24 06:50, Louis Chauvet wrote:
On 26/10/24 - 09:10, Maíra Canal wrote:
Hi Louis,
On 14/10/24 05:39, Louis Chauvet wrote:
On 11/10/24 - 10:53, Maira Canal wrote:
Hi Louis,
On 10/11
Hi,
On 2024/10/29 00:05, Sui Jingfeng wrote:
The 'offset' data member of the 'struct scatterlist' denotes the offset
into a SG entry in bytes. The sg_dma_len() macro could be used to get
lengths of SG entries, those lengths are expected to be CPU page size
aligned. Since, at least for now, we c
On 2024-10-25 22:01, Melissa Wen wrote:
On 25/10/2024 16:37, Zaeem Mohamed wrote:
[why]
Prevent index-out-of-bounds due to requiring cursor overlay when
plane_count is MAX_SURFACES.
Hi Zaeem,
Thanks for working on this fix.
[how]
Bounds check on plane_count when requiring overlay curs
Hi Dave, Simona,
This is the main pull for v6.13. Further description below.
The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:
Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/msm.git tags/drm-
Hi,
On Fri, Oct 25, 2024 at 9:00 PM Tejas Vipin wrote:
>
> @@ -418,79 +398,42 @@ static const struct ltk050h3146w_desc ltk050h3146w_data
> = {
> MIPI_DSI_MODE_LPM | MIPI_DSI_MODE_NO_EOT_PACKET,
> };
>
> -static int ltk050h3146w_a2_select_page(struct ltk050h3146w *ctx, int page)
The ivpu struct drm_driver has conditional initialization based on #ifdef
DRIVER_DATE, which is never defined anywhere. Neither are the macros
referenced within the block: DRIVER_DATE, DRIVER_MAJOR, DRIVER_MINOR,
and DRIVER_PATCHLEVEL. With the struct drm_driver date member going away
anyway, just
We stopped using the driver initialized date in commit 7fb8af6798e8
("drm: deprecate driver date") and (eventually) started returning "0"
for drm_version ioctl instead.
Finish the job, and remove the unused date member from struct
drm_driver, its initialization from drivers, along with the common
drm_dev_register() already prints the same information on successful
init. Remove the redundant prints.
Signed-off-by: Jani Nikula
---
Note: I prefer to merge this together with the next patch via
drm-misc-next.
Cc: Oleksandr Andrushchenko
Cc: Maarten Lankhorst
Cc: Maxime Ripard
Cc: Thomas
This shorten the length of code in horizential direction, therefore is
easier to read.
Signed-off-by: Sui Jingfeng
---
lib/scatterlist.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/scatterlist.c b/lib/scatterlist.c
index 473b2646f71c..5bb6b8aff232 100644
--- a/lib
On Mon, 28 Oct 2024 15:47:25 +0100
Marek Vasut wrote:
> On 10/28/24 2:52 PM, Herve Codina wrote:
> > Hi Marek,
>
> Hi,
>
> >>> On Sat, 26 Oct 2024 00:53:51 +0200
> >>> Marek Vasut wrote:
> >>>
> On 10/24/24 11:55 AM, Herve Codina wrote:
> > In some cases observed during ESD
On Thu, Oct 10, 2024 at 11:42:37AM -0400, Frank Li wrote:
> Fixed below warnings:
>
> arch/arm64/boot/dts/freescale/imx8mq-zii-ultra-rmb3.dtb:
> /soc@0/bus@3080/serial@3089/mcu: failed to match any schema with
> compatible: ['zii,rave-sp-rdu2']
> arch/arm64/boot/dts/freescale/imx8mq-zii-
On Mon, 28 Oct 2024 15:31:19 +
Steven Price wrote:
> On 28/10/2024 11:48, Boris Brezillon wrote:
> > Groups can be killed during a reset even though they did nothing wrong.
> > That usually happens when the FW is put in a bad state by other groups,
> > resulting in group suspension failures w
On Mon, Oct 28, 2024 at 03:45:07PM +0200, Jani Nikula wrote:
> On Sun, 27 Oct 2024, Vamsi Krishna Brahmajosyula
> wrote:
> > @@ -6320,19 +6321,20 @@ static void drm_parse_hdmi_deep_color_info(struct
> > drm_connector *connector,
> >
> > /* HDMI Vendor-Specific Data Block (HDMI VSDB, H14b-VSDB
* Ville Syrjälä (ville.syrj...@linux.intel.com) wrote:
> On Wed, Oct 23, 2024 at 12:29:32AM +0100, li...@treblig.org wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > drm_crtc_vblank_count_and_time() was explicitly added by
> > commit cf6483050e9b ("drm/irq: Add drm_crtc_vblank_count_and_time()")
On Fri, Oct 25, 2024 at 11:50:36PM +0200, Michał Winiarski wrote:
> VF MMIO resource reservation, either created by system firmware and
> inherited by Linux PCI subsystem or created by the subsystem itself,
> should contain enough space to fit the BAR of all SR-IOV Virtual
> Functions that can pote
On Fri, Oct 25, 2024 at 11:50:37PM +0200, Michał Winiarski wrote:
> Drivers could leverage the fact that the VF BAR MMIO reservation is
> created for total number of VFs supported by the device by resizing the
> BAR to larger size when smaller number of VFs is enabled.
>
> Add a pci_iov_vf_bar_set
On Monday, October 28th, 2024 at 7:42 AM, Andy Yan wrote:
> Hi Piotr，
Hi Andy
> Tested on top of Linux 6.12-rc5 with rk3566-box-demo in a buildroot + weston
> environment:
> weston --backend=drm-backend.so -i 0 --continue-without-input
> weston-simple-egl
Thank you for testing it!
> simple-e
From: Arnd Bergmann
Compile-testing random configurations leads to failures in
dcss-kms.c from a missing declaration:
drivers/gpu/drm/imx/dcss/dcss-kms.c:95:8: error: use of undeclared identifier
'drm_bridge_attach'
95 | ret = drm_bridge_attach(encoder, bridge, NULL,
|
Hi, Dear reviewers
On 2024/10/29 00:05, Sui Jingfeng wrote:
The 'offset' data member of the 'struct scatterlist' denotes the offset
into a SG entry in bytes. The sg_dma_len() macro could be used to get
lengths of SG entries, those lengths are expected to be CPU page size
aligned. Since, at least
On Wed, Oct 23, 2024 at 12:29:32AM +0100, li...@treblig.org wrote:
> From: "Dr. David Alan Gilbert"
>
> drm_crtc_vblank_count_and_time() was explicitly added by
> commit cf6483050e9b ("drm/irq: Add drm_crtc_vblank_count_and_time()")
> in 2015, but never used.
I see a bunch of places that could t
Hi,
On 2024/10/29 00:01, Lucas Stach wrote:
Hi Sui,
Am Montag, dem 07.10.2024 um 12:20 +0200 schrieb Lucas Stach:
Am Samstag, dem 05.10.2024 um 03:42 +0800 schrieb Sui Jingfeng:
Print an error message to help debug when such an issue happen, since it's
not so obvious.
Signed-off-by: Sui Jing
On Wed, Oct 23, 2024 at 12:29:32AM +0100, li...@treblig.org wrote:
> From: "Dr. David Alan Gilbert"
>
> drm_crtc_vblank_count_and_time() was explicitly added by
> commit cf6483050e9b ("drm/irq: Add drm_crtc_vblank_count_and_time()")
> in 2015, but never used.
>
> Remove it, and rework comments t
On 28/10/2024 11:48, Boris Brezillon wrote:
> If we don't do that, the group is considered usable by userspace, but
> all further GROUP_SUBMIT will fail with -EINVAL.
>
> Changes in v2:
> - New patch
>
> Fixes: de8548813824 ("drm/panthor: Add the scheduler logical block")
> Signed-off-by: Boris B
The 'offset' data member of the 'struct scatterlist' denotes the offset
into a SG entry in bytes. The sg_dma_len() macro could be used to get
lengths of SG entries, those lengths are expected to be CPU page size
aligned. Since, at least for now, we call drm_prime_pages_to_sg() to
convert our variou
The 'iova' variable is invarant within one invoke of the
etnaviv_iommu_unmap()/etnaviv_iommu_unmap(), which means that the
debug log always print the same GPU virtual address while mapping
or unmaping.
Made the GPU virtual address being printed increment with real GPUVA
being mapped or unmapped.
Hi Sui,
Am Montag, dem 07.10.2024 um 12:20 +0200 schrieb Lucas Stach:
> Am Samstag, dem 05.10.2024 um 03:42 +0800 schrieb Sui Jingfeng:
> > Print an error message to help debug when such an issue happen, since it's
> > not so obvious.
> >
> > Signed-off-by: Sui Jingfeng
>
> Reviewed-by: Lucas S
Am Samstag, dem 26.10.2024 um 01:56 +0800 schrieb Sui Jingfeng:
> The etnaviv_cmdbuf.c doesn't reference any functions or data members
> defined in drm_mm.h, remove unneeded headers may reduce kernel compile
> times.
>
> Signed-off-by: Sui Jingfeng
Thanks, applied to etnaviv/next.
> ---
> driv
Am Samstag, dem 26.10.2024 um 01:51 +0800 schrieb Sui Jingfeng:
> Because it is not get used, drop it.
>
> Signed-off-by: Sui Jingfeng
Thanks, applied to etnaviv/next.
> ---
> drivers/gpu/drm/etnaviv/etnaviv_mmu.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/etnaviv
Am Samstag, dem 26.10.2024 um 04:43 +0800 schrieb Sui Jingfeng:
> Etnaviv assumes that GPU page size is 4KiB, however, when using
> softpin capable GPUs on a different CPU page size configuration.
> The userspace allocated GPUVA ranges collision, unable to be
> inserted to the specified address hol
On Sat, 26 Oct 2024 06:10:42 +0200, Marek Vasut wrote:
> The driver configures mostly Pixel PLL from the clock cached in
> local copy of the mode. Make sure the driver uses adjusted mode
> which contains the updated Pixel PLL settings negotiated in
> tc_dpi_atomic_check()/tc_edp_atomic_check().
>
Am Freitag, dem 05.07.2024 um 22:00 +0200 schrieb Lucas Stach:
> The perfmon sampling mutates shared GPU state (e.g. VIVS_HI_CLOCK_CONTROL
> to select the pipe for the perf counter reads). To avoid clashing with
> other functions mutating the same state (e.g. etnaviv_gpu_update_clock)
> the perfmon
Am Sonntag, dem 25.08.2024 um 20:14 +0800 schrieb Sui Jingfeng:
> Currently, the calling of mutex_destroy() is ignored on error handling
> code path. It is safe for now, since mutex_destroy() actually does
> nothing in non-debug builds. But the mutex_destroy() is used to mark
> the mutex uninitiali
Am Sonntag, dem 08.09.2024 um 20:11 +0800 schrieb Sui Jingfeng:
> The drm_prime_pages_to_sg() function takes an 'unsigned int' argument to
> store the length of the page vector. The size of the object in number of
> CPU pages can not be negative, hence, use 'unsigned' variable to store
> the number
Am Mittwoch, dem 02.10.2024 um 07:34 +0800 schrieb Xiaolei Wang:
> Remove __GFP_HIGHMEM when requesting a page from DMA32 zone,
> and since all vivante GPUs in the system will share the same
> DMA constraints, move the check of whether to get a page from
> DMA32 to etnaviv_bind().
>
> Fixes: b72af
On 10/28/24 2:52 PM, Maxime Ripard wrote:
On Mon, Oct 28, 2024 at 01:36:58PM +0100, Marek Vasut wrote:
On 10/28/24 10:25 AM, Maxime Ripard wrote:
On Sat, Oct 26, 2024 at 06:10:01AM +0200, Marek Vasut wrote:
Horizontal Timing Control0 Register 1/2 (HTIM01/HTIM02) Register
bitfields description
On 28/10/2024 11:48, Boris Brezillon wrote:
> Groups can be killed during a reset even though they did nothing wrong.
> That usually happens when the FW is put in a bad state by other groups,
> resulting in group suspension failures when the reset happens.
>
> If we end up in that situation, flag
ints
Regards,
Chun-Kuang.
The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:
Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/chunkuang.hu/linux.git
tags/mediatek-drm-fixes-20241028
for yo
> -Original Message-
> From: Vivi, Rodrigo
> Sent: Monday, October 28, 2024 8:27 PM
> To: Usyskin, Alexander ; Gupta, Anshuman
> ; Deak, Imre
> Cc: Miquel Raynal ; Richard Weinberger
> ; Vignesh Raghavendra ; De Marchi,
> Lucas ; Thomas Hellström
> ; Maarten Lankhorst
> ; Maxime Ripard
Hi,
On 25/10/2024 17:58, Sean Anderson wrote:
Hi Tomi,
On 10/3/24 10:53, Sean Anderson wrote:
On 10/2/24 10:50, Tomi Valkeinen wrote:
Hi,
On 01/10/2024 21:31, Sean Anderson wrote:
On 8/9/24 15:35, Sean Anderson wrote:
This series cleans up the zyqnmp_dp IRQ and locking situation. Once
that
On Tue, Oct 22, 2024 at 01:41:15PM +0300, Alexander Usyskin wrote:
> Enable runtime PM in mtd driver to notify graphics driver that
> whole card should be kept awake while nvm operations are
> performed through this driver.
>
> CC: Lucas De Marchi
> Signed-off-by: Alexander Usyskin
> ---
> driv
On 23.10.24 09:52, Maarten Lankhorst wrote:
The initial version was based roughly on the rdma and misc cgroup
controllers, with a lot of the accounting code borrowed from rdma.
The current version is a complete rewrite with page counter; it uses
the same min/low/max semantics as the memory cgrou
v3d_bo(&shmem_obj->base);
---
base-commit: dec9255a128e19c5fcc3bdb18175d78094cc624d
change-id: 20241028-v3d-1d2546ed92d7
Best regards,
--
Matthias Brugger
On Tue, Oct 22, 2024 at 01:41:18PM +0300, Alexander Usyskin wrote:
> Enable access to internal non-volatile memory on DGFX
> with GSC/CSC devices via a child device.
> The nvm child device is exposed via auxiliary bus.
I looked at all of the i915 and xe patches here and everything looks right.
Jus
On 10/29/2024 3:29 AM, Li Huafei wrote:
> Fix the potential NULL pointer dereference on mem_ranges in
> amdgpu_discovery_get_nps_info(). Additionally, assign the output
> parameters nps_type and range_cnt after the kvzalloc() call to prevent
> modifying the output parameters in case of an error
On Fri, Oct 25, 2024 at 09:39:20PM +0100, li...@treblig.org wrote:
> From: "Dr. David Alan Gilbert"
>
> drm_i2c_encoder_commit(), drm_i2c_encoder_mode_set() and
> drm_i2c_encoder_prepare() have been unused since 2016's
> commit 7bc61cc5df80 ("drm/arcpgu: Accommodate adv7511 switch to DRM
> bridge
On Tue, Oct 22, 2024 at 07:37:01AM -0700, Doug Anderson wrote:
> Hi,
>
> On Tue, Oct 22, 2024 at 12:12 AM Geert Uytterhoeven
> wrote:
> >
> > > > > > > However, using i2c_client->adapter->nr instead of ida_alloc()
> > > > > > > in the TI driver does sound like a good idea to me...
> > > > > >
> >
On Mon, Oct 28, 2024 at 02:55:47PM +0100, Maxime Ripard wrote:
> On Mon, Oct 28, 2024 at 03:28:58PM +0200, Laurent Pinchart wrote:
> > On Mon, Oct 28, 2024 at 01:21:45PM +0100, Maxime Ripard wrote:
> > > On Mon, Oct 28, 2024 at 01:28:57PM +0200, Laurent Pinchart wrote:
> > > > On Mon, Oct 28, 2024
On Mon, Oct 28, 2024 at 01:36:58PM +0100, Marek Vasut wrote:
> On 10/28/24 10:25 AM, Maxime Ripard wrote:
> > On Sat, Oct 26, 2024 at 06:10:01AM +0200, Marek Vasut wrote:
> > > Horizontal Timing Control0 Register 1/2 (HTIM01/HTIM02) Register
> > > bitfields description state "These bits must be mul
On Wed, Oct 23, 2024 at 12:29:34AM +0100, li...@treblig.org wrote:
> From: "Dr. David Alan Gilbert"
>
> drm_client_modeset_check() was explicitly added in 2020 by
> commit 64593f2a6fc9 ("drm/client: Add drm_client_modeset_check()")
> but has never been used.
>
> Remove it.
If you are removing i
Fix the potential NULL pointer dereference on mem_ranges in
amdgpu_discovery_get_nps_info(). Additionally, assign the output
parameters nps_type and range_cnt after the kvzalloc() call to prevent
modifying the output parameters in case of an error return.
Fixes: b194d21b9bcc ("drm/amdgpu: Use NPS
On Mon, Oct 28, 2024 at 03:28:58PM +0200, Laurent Pinchart wrote:
> On Mon, Oct 28, 2024 at 01:21:45PM +0100, Maxime Ripard wrote:
> > On Mon, Oct 28, 2024 at 01:28:57PM +0200, Laurent Pinchart wrote:
> > > On Mon, Oct 28, 2024 at 09:13:31AM +0100, Herve Codina wrote:
> > > > On Sun, 27 Oct 2024 18
On Mon, Oct 28, 2024 at 02:52:09PM +0100, Maxime Ripard wrote:
> On Mon, Oct 28, 2024 at 01:36:58PM +0100, Marek Vasut wrote:
> > On 10/28/24 10:25 AM, Maxime Ripard wrote:
> > > On Sat, Oct 26, 2024 at 06:10:01AM +0200, Marek Vasut wrote:
> > > > Horizontal Timing Control0 Register 1/2 (HTIM01/HTI
Hi Marek,
On Mon, 28 Oct 2024 12:47:14 +0100
Marek Vasut wrote:
> On 10/28/24 9:02 AM, Herve Codina wrote:
> > Hi Marek,
>
> Hi,
>
> > On Sat, 26 Oct 2024 00:53:51 +0200
> > Marek Vasut wrote:
> >
> >> On 10/24/24 11:55 AM, Herve Codina wrote:
> >>> In some cases observed during ESD te
* Dmitry Baryshkov (dmitry.barysh...@linaro.org) wrote:
> On Wed, Oct 23, 2024 at 12:29:34AM +0100, li...@treblig.org wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > drm_client_modeset_check() was explicitly added in 2020 by
> > commit 64593f2a6fc9 ("drm/client: Add drm_client_modeset_check()")
On 16.10.2024 09:07, Tvrtko Ursulin wrote:
>
> On 15/10/2024 20:05, Adrián Larumbe wrote:
> > Hi Tvrtko,
> >
> > On 10.10.2024 10:50, Tvrtko Ursulin wrote:
> > >
> > > On 09/10/2024 23:55, Adrián Larumbe wrote:
> > > > Hi Tvrtko,
> > > >
> > > > On 04.10.2024 14:41, Tvrtko Ursulin wrote:
> > >
On Sun, 27 Oct 2024, Vamsi Krishna Brahmajosyula
wrote:
> @@ -6320,19 +6321,20 @@ static void drm_parse_hdmi_deep_color_info(struct
> drm_connector *connector,
>
> /* HDMI Vendor-Specific Data Block (HDMI VSDB, H14b-VSDB) */
> static void
> -drm_parse_hdmi_vsdb_video(struct drm_connector *co
From: Steffen Dirkwinkel
drm_kms_helper_poll_init needs to be called after zynqmp_dpsub_kms_init.
zynqmp_dpsub_kms_init creates the connector and without it we don't
enable hotplug detection.
Fixes: eb2d64bfcc17 ("drm: xlnx: zynqmp_dpsub: Report HPD through the bridge")
Cc: sta...@vger.kernel.or
From: Steffen Dirkwinkel
layer->info can be null if we have an error on the first layer in
zynqmp_disp_create_layers
Fixes: 1836fd5ed98d ("drm: xlnx: zynqmp_dpsub: Minimize usage of global flag")
Signed-off-by: Steffen Dirkwinkel
---
drivers/gpu/drm/xlnx/zynqmp_disp.c | 3 +++
1 file changed,
On 10/28/24 10:25 AM, Maxime Ripard wrote:
On Sat, Oct 26, 2024 at 06:10:01AM +0200, Marek Vasut wrote:
Horizontal Timing Control0 Register 1/2 (HTIM01/HTIM02) Register
bitfields description state "These bits must be multiple of even
pixel". It is not possible to simply align every bitfield to t
From: Steffen Dirkwinkel
drm_kms_helper_poll_init needs to be called after zynqmp_dpsub_kms_init.
zynqmp_dpsub_kms_init creates the connector and without it we don't
enable hotplug detection.
Fixes: eb2d64bfcc17 ("drm: xlnx: zynqmp_dpsub: Report HPD through the bridge")
Signed-off-by: Steffen Di
On Mon, Oct 28, 2024 at 01:21:45PM +0100, Maxime Ripard wrote:
> On Mon, Oct 28, 2024 at 01:28:57PM +0200, Laurent Pinchart wrote:
> > On Mon, Oct 28, 2024 at 09:13:31AM +0100, Herve Codina wrote:
> > > On Sun, 27 Oct 2024 18:23:50 +0200 Laurent Pinchart wrote:
> > >
> > > [...]
> > > > > +static
On Wed, Oct 23, 2024 at 12:29:31AM +0100, li...@treblig.org wrote:
> From: "Dr. David Alan Gilbert"
>
> drm_class_device_register() and drm_class_device_unregister() have been
> unused since
> commit ed89fff97382 ("drm/ttm: drop sysfs directory")
>
> Remove them.
>
> Signed-off-by: Dr. David Al
1 - 100 of 199 matches
Mail list logo
