From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-185.mta0.migadu.com (out-185.mta0.migadu.com [91.218.175.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7514F13AD22 for ; Thu, 6 Feb 2025 19:48:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.185 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1738871328; cv=none; b=qbvzXYQOFARzyPJEtYoSX3cYjC1DQjs1GOEOe5E6NOFBgFlBXXy+tQk9ATzSai6QSVflepGekSS/zHHTMIPlaFc6vpS1HjaLyHurlSb9P78d5+0gNfaETJ1xK9ZjL48grc5jghOXc35O141nIbtDOQOA02oVbMV5VRWIsBh+jeM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1738871328; c=relaxed/simple; bh=PH8f+I6CIwrUYvKrHucDBzZuxlOxqdDG+0hnKmbnfhY=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=mwzmGk+KV2chCfDdv/f2c+eO1Bx+8hVV8FDny0n53WlqFD7TBQ6HN2uqZ0WXu0l+KBw4bzL/olRNNVOaN6xO0A1K8UCDMjYVa1VQxUq8T019QkhliHgUKKsmOtxH4xVF4WBP425GaH3hQQKJXw8SdwSLrDvhsYC9FtppmgacAUw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=L56l4iRE; arc=none smtp.client-ip=91.218.175.185 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="L56l4iRE" Message-ID: <487916d8-da54-4932-81dd-f139870a734a@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1738871319; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=OwPDbQEyAXc77Q5C6257jMdBP0ZXb8K4s1MUTLeX9mA=; b=L56l4iREX7uPZFdUgfZLgCzh+xM4hGXE8xVUwHTzHq/M4h9cgKCj0VvxDO+QWay4IX2nLe Vb2cd+2xlmJQtlFFhEDjZJdIZSjc7mDU62eRinjTmqy25wlmTHhkCYPzjdV13rvFRAxbvf dJB1IKw0+uN99W2fs7DxKemlUZtnAt0= Date: Thu, 6 Feb 2025 14:48:35 -0500 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH v2 10/10] drm: xlnx: zynqmp: Fix max dma segment size To: Tomi Valkeinen , Vishal Sagar , Anatoliy Klymenko , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Laurent Pinchart , Michal Simek Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org References: <20250115-xilinx-formats-v2-0-160327ca652a@ideasonboard.com> <20250115-xilinx-formats-v2-10-160327ca652a@ideasonboard.com> Content-Language: en-US X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Sean Anderson In-Reply-To: <20250115-xilinx-formats-v2-10-160327ca652a@ideasonboard.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT 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 > Tested-by: Sean Anderson > Signed-off-by: Tomi Valkeinen > --- > 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. --Sean