imx.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
	 dmaengine@vger.kernel.org, festevam@gmail.com,
	imx@lists.linux.dev,  joy.zou@nxp.com, kernel@pengutronix.de,
	krzysztof.kozlowski+dt@linaro.org,
	 linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
	 linux-kernel@vger.kernel.org, robh@kernel.org,
	s.hauer@pengutronix.de,  shawnguo@kernel.org
Subject: Re: [PATCH v5 1/3] dt-bindings: fsl-imx-sdma: Add I2C peripheral types ID
Date: Thu, 25 Apr 2024 14:47:25 +0530	[thread overview]
Message-ID: <171403664527.79852.6338713889977075573.b4-ty@kernel.org> (raw)
In-Reply-To: <20240419150729.1071904-1-Frank.Li@nxp.com>


On Fri, 19 Apr 2024 11:07:27 -0400, Frank Li wrote:
> Add peripheral types ID 27 for I2C because sdma firmware (sdma-6q: v3.6,
> sdma-7d: v4.6) support I2C DMA transfer.
> 
> 

Applied, thanks!

[1/3] dt-bindings: fsl-imx-sdma: Add I2C peripheral types ID
      commit: 458bb56d53c9758ef873b4f373660b1f02b98d86
[2/3] dmaengine: imx-sdma: utilize compiler to calculate ADDRS_ARRAY_SIZE_V<n>
      commit: 1cb49f389d5985bd9ad6ef37f856f368c3120f77
[3/3] dmaengine: imx-sdma: Add i2c dma support
      commit: d850b5bae0f5e435360edf0474ff446622f0d899

Best regards,
-- 
~Vinod



      parent reply	other threads:[~2024-04-25  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 15:07 [PATCH v5 1/3] dt-bindings: fsl-imx-sdma: Add I2C peripheral types ID Frank Li
2024-04-19 15:07 ` [PATCH v5 2/3] dmaengine: imx-sdma: utilize compiler to calculate ADDRS_ARRAY_SIZE_V<n> Frank Li
2024-04-19 15:07 ` [PATCH v5 3/3] dmaengine: imx-sdma: Add i2c dma support Frank Li
2024-04-25  9:17 ` Vinod Koul [this message]

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=171403664527.79852.6338713889977075573.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=joy.zou@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).