From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (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 72FEB26AF5 for ; Wed, 22 Jan 2025 07:21:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737530519; cv=none; b=tuIvK+4brZHv4dSsMhK5CaOPQMEO6v5bHBiZouYyziG1lNUFiULBJWhPcl8EGkBwI0WkT4UcY8Ao6kSgdUAN9HdJNc8FPJGwzTa0AhWaOoKC3YCf7uhhrK4nS6osnoU7qTQ0vtpyvZuOh4ujgfn60nMQ5OJkeytc1vWDxlVA7dk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737530519; c=relaxed/simple; bh=pgxSHx2ys9jK8Ypslvhf7Lhumz5BLoPe+309r5ajS6o=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=QmMHP9Sg5wSH+npcH1iE/qxjDLYk65Q1pPKSMBRvAWSRJYQNq8ptLFK83qVpuaQ3vWOjhi1zk6MFftfX+Pb27S/ob9pJ/QvPrZGBb/1UxEK0Hwpk+p5NBi4v+cVbGXu2EjEZ2DDmm2jDT7F+r6qlLSkSHNvKNjghQVInLx1Fl5Y= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=WG879ojN; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="WG879ojN" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=k1; bh=pgxS Hx2ys9jK8Ypslvhf7Lhumz5BLoPe+309r5ajS6o=; b=WG879ojN90FOF0c5S2E8 Cao8Tgp1oLe+2jzNJ9e9xd4vQ2cPr515e7EEzYyogYUHpMvqkmZpGSvkJdxD8sOT gUNKaWiIjCoRrYRs2PaTAT37Tds99My1dOKhd8vGVe5I4WISkfD8BUWlmZjy2BnZ YTdfmYKZ/1wDOElDYHcGluxVeX2q6Fz+ogffKnKJ27A6Zfxm0MZS1MwT0ke9VsLm DNKvKs+VAuv46oZCYM5mFQJl1/ozHZRuO7qjPAfdv2lemMTkHoAWe+15bT55+uPJ D1hMpggp6E+SfAQzVtMQokXdZADEJUYqDvn7vvuBCDSt68WX6cBUPT34Sw6Dp4DF 1g== Received: (qmail 2764966 invoked from network); 22 Jan 2025 08:21:48 +0100 Received: by mail.zeus03.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 22 Jan 2025 08:21:48 +0100 X-UD-Smtp-Session: l3s3148p1@lFi1WEYsuqcujnvm Date: Wed, 22 Jan 2025 08:21:47 +0100 From: Wolfram Sang To: Mukesh Kumar Savaliya Cc: Billy Tsai , alexandre.belloni@bootlin.com, pgaj@cadence.com, miquel.raynal@bootlin.com, conor.culhane@silvaco.com, aniketmaurya@google.com, Shyam-sundar.S-k@amd.com, jarkko.nikula@linux.intel.com, xiaopei01@kylinos.cn, Guruvendra.Punugupati@amd.com, linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 1/2] i3c: Remove the const qualifier from i2c_msg pointer in i2c_xfers API Message-ID: Mail-Followup-To: Wolfram Sang , Mukesh Kumar Savaliya , Billy Tsai , alexandre.belloni@bootlin.com, pgaj@cadence.com, miquel.raynal@bootlin.com, conor.culhane@silvaco.com, aniketmaurya@google.com, Shyam-sundar.S-k@amd.com, jarkko.nikula@linux.intel.com, xiaopei01@kylinos.cn, Guruvendra.Punugupati@amd.com, linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org References: <20250121110756.214714-1-billy_tsai@aspeedtech.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="WL/IGby9HHcM53NP" Content-Disposition: inline In-Reply-To: --WL/IGby9HHcM53NP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > what we need is only i2c_xfers->buf to be DMA-safe, not the *i2c_xfers. > Right ? Yes. > Also I guess same change is required for all the vendor drivers. But Not > sure if it's feasible with this patch ? I also wondered if the I3C core should maybe provide this, but then I saw that currently only the mipi-hci driver uses DMA and concluded that per-driver is better. At least for now. --WL/IGby9HHcM53NP Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAmeQnIgACgkQFA3kzBSg Kbaifg/7BJfV/+Bivwke0oMwsbIMcBPQcxD0wCNN/0ALq8jU41KIg68JXKdMePN3 79BALPSCiJKkWKxCkeWH1ODtc2JWkw+wKRBNx4fkyAjaC8P3klM9nRywqLbJ1w6i qL3dt4RWxozyb3VV8wpNCEvcSTquZp6B8lON2waEt4J+Z9YfP/QCrZvzHiJtL0Yt j8LJJcN0+e42Ia+NjYXbXl0D3CNkzl1Jd77iYZS6hKUfdnnBngR72KYU98lq0ufT gtAK3OwOZ3NU6lVLmy6H4kWGtZLacPSdw8T2B9LfQytbL4a27P465AzsJMxFEYB5 ItqikJN1OFd1WmtJN/DM2tT3vLUil9LItu5stucp6R5tmqxKk+i/buWmYQtlcRSw i2hwBMxbdSqTym921FzJ8kn9tX8jfZaJxdI6IN54w6+qdm8ejvTDyD/eKfoLqhXZ G4HT2xJtjR3Ebd5X06cTW8ZBSbvlU/w8UBqiby2rRpc83DT+NnfHmPRc6zhvWpQe lRpr1lX7MX8Wy3H8sq0dWj7BvE0uhU8OUtQXpHWvmhrW6NHqcKZ+h+e64iz35Y93 WKHnqYX1yEP6ZW+5zhIrILV58Iwvx68iPnl+MaImJZ34it0MW3YCKGGFw699GmVE d5D0M/+l3MdUUU6egJii34qbWdcThw7H+ubozxSo+g6c0RCxYrQ= =7O/J -----END PGP SIGNATURE----- --WL/IGby9HHcM53NP--