From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from codeconstruct.com.au (pi.codeconstruct.com.au [203.29.241.158]) (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 6B2EB2DC32A; Tue, 31 Mar 2026 07:00:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=203.29.241.158 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774940456; cv=none; b=ZjdWqQTzriqSPyI9QAwMxJoHXtP6+5vgGFKB+gIVJCfbVoFUVZE64f60/nJLFnCqUonjcZjaN3/vn6lJDkuMtZaolgpdhd55kFQ+60rlVxWlg+GyVosxFk/ljuRi90RwuENMoo+niqZDsInFtIheSQHeGbRebpXtpSVXiGsRQEM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774940456; c=relaxed/simple; bh=RTmsuImCn3CtzefM7fomAbHA5I/f+UtO2YDEaei1OTI=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=j9wiyoQxEsA/gB1wHN+38snwy8h4Y1sfJlUytcAwpaDzVKdY/I7kpwwBl1RAN2qQ9cOWSq66AsKHRkSuA02OdJGn3VjO0WUfMMPI5FAzYQozdAJnqXR0GjYDqC+WrlX0hXU3dU9xT/LRYPH762f0Xq7dtI7W5wj8BmqYczaroGk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=codeconstruct.com.au; spf=pass smtp.mailfrom=codeconstruct.com.au; dkim=pass (2048-bit key) header.d=codeconstruct.com.au header.i=@codeconstruct.com.au header.b=QteUuSwe; arc=none smtp.client-ip=203.29.241.158 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=codeconstruct.com.au Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=codeconstruct.com.au Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=codeconstruct.com.au header.i=@codeconstruct.com.au header.b="QteUuSwe" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codeconstruct.com.au; s=2022a; t=1774940445; bh=RTmsuImCn3CtzefM7fomAbHA5I/f+UtO2YDEaei1OTI=; h=Subject:From:To:Cc:Date:In-Reply-To:References; b=QteUuSwewXeKt35dLgpxQsZXo5XcyHBW/48b/IrIeozShAmj9VPjbHWDFcv/7wrMN EbUx9muoJkfo62g8yHdbEXleSmEM7DvOFC9FI9c4YM4maKbG5CbivJrN7I9CaVCD/F od6I5UEuh44ELgSAxSMKT4cPTf1mkGetpkyAsp+5QMH5pkKIaJLJD3kudVjLBpwp4y 92WKhncfZ73BaknEFEK/ojuJhc5+qr9ztjoY/aKvdSk1ekZm2uqGCMb7taHI/WOwnj KNmh+i7o7sjAYUZDtqWcP1Wg2GeKoZkRQZCiCI1Qh/5TjAbI/27q+jqbGF9E06udHO 2daLsjmnVJuqw== Received: from [192.168.72.167] (210-10-213-150.per.static-ipl.aapt.com.au [210.10.213.150]) by mail.codeconstruct.com.au (Postfix) with ESMTPSA id 5B5616002E; Tue, 31 Mar 2026 15:00:43 +0800 (AWST) Message-ID: <09cbc12bea5707f794e139ea1bfafac82c2d2c12.camel@codeconstruct.com.au> Subject: Re: [PATCH v28 2/4] dt-bindings: i2c: ast2600-i2c.yaml: Add global-regs and enable-dma properties From: Jeremy Kerr To: Ryan Chen , Krzysztof Kozlowski Cc: "andriy.shevchenko@linux.intel.com" , Andi Shyti , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Joel Stanley , Andrew Jeffery , Benjamin Herrenschmidt , Philipp Zabel , "linux-i2c@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-aspeed@lists.ozlabs.org" , "linux-kernel@vger.kernel.org" , "openbmc@lists.ozlabs.org" Date: Tue, 31 Mar 2026 15:00:43 +0800 In-Reply-To: References: <20260330-upstream_i2c-v28-0-17bdae39c5cb@aspeedtech.com> <20260330-upstream_i2c-v28-2-17bdae39c5cb@aspeedtech.com> <20260331-fanatic-certain-bustard-fb13bc@quoll> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4-2+deb12u1 Precedence: bulk X-Mailing-List: linux-i2c@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Hi Ryan, > All AST2600 I2C controller instances have DMA hardware. > I will remove the aspeed,enable-dma property and instead expose sysfs > attribute in driver to allow users to enable dma/buffer/byte. Sounds reasonable, but before you do so, how are you planning to manage the allocation of DMA channels across multiple i2c peripherals? Cheers, Jeremy