DMA Engine development
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: linux-arm-msm@vger.kernel.org, luca.weiss@fairphone.com
Cc: vkoul@kernel.org, dmaengine@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	linux-kernel@vger.kernel.org, konrad.dybcio@somainline.org,
	phone-devel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: (subset) [PATCH 0/3] Add GPI DMA support for SM6350
Date: Mon, 29 Aug 2022 18:46:01 -0500	[thread overview]
Message-ID: <166181675978.322065.10581898444404760964.b4-ty@kernel.org> (raw)
In-Reply-To: <20220812082721.1125759-1-luca.weiss@fairphone.com>

On Fri, 12 Aug 2022 10:27:18 +0200, Luca Weiss wrote:
> This series hooks up GPI DMA support for the SM6350 I2C.
> 
> It has been tested using himax,hxcommon driver that I forward-ported
> from the original vendor kernel on fairphone-fp4 - previously I have
> used i2c-gpio bitbang in my tree.
> 
> This also requires the fix from Robin[0] that has already been
> accepted into linux-next, otherwise I2C communication fails to work.
> 
> [...]

Applied, thanks!

[3/3] arm64: dts: qcom: sm6350: Add GPI DMA nodes
      commit: 9f0149caf0dc1c1261a612b0653d31d998f80596

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

  parent reply	other threads:[~2022-08-29 23:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12  8:27 [PATCH 0/3] Add GPI DMA support for SM6350 Luca Weiss
2022-08-12  8:27 ` [PATCH 1/3] dt-bindings: dmaengine: qcom: gpi: add compatible " Luca Weiss
2022-08-12 10:05   ` Krzysztof Kozlowski
2022-08-29 21:42   ` Bjorn Andersson
2022-08-12  8:27 ` [PATCH 2/3] dmaengine: qcom: gpi: Add SM6350 support Luca Weiss
2022-08-29 21:42   ` Bjorn Andersson
2022-08-29 23:46 ` Bjorn Andersson [this message]
2022-09-04 16:23 ` [PATCH 0/3] Add GPI DMA support for SM6350 Vinod Koul

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=166181675978.322065.10581898444404760964.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.weiss@fairphone.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=vkoul@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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