From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Sean Anderson <sean.anderson@linux.dev>,
Vishal Sagar <vishal.sagar@amd.com>,
Anatoliy Klymenko <anatoliy.klymenko@amd.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Michal Simek <michal.simek@amd.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 10/10] drm: xlnx: zynqmp: Fix max dma segment size
Date: Tue, 11 Feb 2025 15:00:28 +0200 [thread overview]
Message-ID: <78d22bdf-8a0c-4881-b648-3afe2b02d158@ideasonboard.com> (raw)
In-Reply-To: <487916d8-da54-4932-81dd-f139870a734a@linux.dev>
Hi,
On 06/02/2025 21:48, Sean Anderson wrote:
> Hi Tomi,
>
> On 1/15/25 04:03, Tomi Valkeinen wrote:
>> Fix "mapping sg segment longer than device claims to support" warning by
>> setting the max segment size.
>>
>> Fixes: d76271d22694 ("drm: xlnx: DRM/KMS driver for Xilinx ZynqMP DisplayPort Subsystem")
>> Reviewed-by: Sean Anderson <sean.anderson@linux.dev>
>> Tested-by: Sean Anderson <sean.anderson@linux.dev>
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
>> ---
>> drivers/gpu/drm/xlnx/zynqmp_dpsub.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/xlnx/zynqmp_dpsub.c b/drivers/gpu/drm/xlnx/zynqmp_dpsub.c
>> index f5781939de9c..a25b22238e3d 100644
>> --- a/drivers/gpu/drm/xlnx/zynqmp_dpsub.c
>> +++ b/drivers/gpu/drm/xlnx/zynqmp_dpsub.c
>> @@ -231,6 +231,8 @@ static int zynqmp_dpsub_probe(struct platform_device *pdev)
>> if (ret)
>> return ret;
>>
>> + dma_set_max_seg_size(&pdev->dev, DMA_BIT_MASK(32));
>> +
>> /* Try the reserved memory. Proceed if there's none. */
>> of_reserved_mem_device_init(&pdev->dev);
>>
>>
>
> Can you apply this patch? I ran into this warning again today and I think this change
> is independent from the rest of the series.
Yes, I'll push this.
Tomi
next prev parent reply other threads:[~2025-02-11 13:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 9:03 [PATCH v2 00/10] drm: Add new pixel formats for Xilinx Zynqmp Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 01/10] drm/fourcc: Add warning for bad bpp Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 02/10] drm/fourcc: Add DRM_FORMAT_XV15/XV20 Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 03/10] drm/fourcc: Add DRM_FORMAT_Y8 Tomi Valkeinen
2025-01-15 10:30 ` Geert Uytterhoeven
2025-01-15 11:12 ` Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 04/10] drm/fourcc: Add DRM_FORMAT_Y10_LE32 Tomi Valkeinen
2025-01-15 10:33 ` Geert Uytterhoeven
2025-01-15 11:11 ` Tomi Valkeinen
2025-01-15 12:33 ` Geert Uytterhoeven
2025-01-15 12:42 ` Tomi Valkeinen
2025-01-15 12:52 ` Geert Uytterhoeven
2025-01-15 13:46 ` Tomi Valkeinen
2025-01-15 14:08 ` Geert Uytterhoeven
2025-01-15 14:34 ` Tomi Valkeinen
2025-01-15 14:49 ` Geert Uytterhoeven
2025-01-15 16:07 ` Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 05/10] drm/fourcc: Add DRM_FORMAT_X403 Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 06/10] drm: xlnx: zynqmp: Use drm helpers when calculating buffer sizes Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 07/10] drm: xlnx: zynqmp: Add support for XV15 & XV20 Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 08/10] drm: xlnx: zynqmp: Add support for Y8 and Y10_LE32 Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 09/10] drm: xlnx: zynqmp: Add support for X403 Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 10/10] drm: xlnx: zynqmp: Fix max dma segment size Tomi Valkeinen
2025-02-06 19:48 ` Sean Anderson
2025-02-11 13:00 ` Tomi Valkeinen [this message]
2025-01-15 11:13 ` [PATCH v2 00/10] drm: Add new pixel formats for Xilinx Zynqmp Dmitry Baryshkov
2025-01-15 12:11 ` Tomi Valkeinen
2025-02-12 16:37 ` Tomi Valkeinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=78d22bdf-8a0c-4881-b648-3afe2b02d158@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=anatoliy.klymenko@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=michal.simek@amd.com \
--cc=mripard@kernel.org \
--cc=sean.anderson@linux.dev \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=vishal.sagar@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox