From: Wolfram Sang <wsa@kernel.org>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] soc: qcom: add support for the I2C Master Hub
Date: Mon, 5 Dec 2022 09:31:49 +0100 [thread overview]
Message-ID: <Y42sdXiCIpj2iaag@ninjato> (raw)
In-Reply-To: <Y4kvcXTdwImZpaU1@shikoro>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
On Thu, Dec 01, 2022 at 11:49:21PM +0100, Wolfram Sang wrote:
> On Tue, Nov 29, 2022 at 03:47:00PM +0100, Neil Armstrong wrote:
> > The I2C Master Hub is a stripped down version of the GENI Serial Engine
> > QUP Wrapper Controller but only supporting I2C serial engines without
> > DMA support.
> >
> > The I2C Master Hub only supports a variant of the I2C serial engine with:
> > - a separate "core" clock
> > - no DMA support
> > - non discoverable fixed FIFO size
> >
> > Since DMA isn't supported, the wrapper doesn't need the Master AHB clock
> > and the iommus property neither.
> >
> > This patchset adds the bindings changes to the QUPv3 wrapper and I2C serial
> > element bindings to reflect the different resources requirements.
> >
> > In order to reuse the QUPv3 wrapper and I2C serial element driver support,
> > the I2C Master Hub requirements are expressed in new desc structs passed
> > as device match data.
>
> Is everyone fine if I take all this via the I2C tree?
I did this now.
All applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-05 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 14:47 [PATCH v3 0/6] soc: qcom: add support for the I2C Master Hub Neil Armstrong
2022-11-29 14:47 ` [PATCH v3 1/6] dt-bindings: qcom: geni-se: document I2C Master Hub wrapper variant Neil Armstrong
2022-11-29 14:47 ` [PATCH v3 2/6] dt-bindings: i2c: qcom-geni: document I2C Master Hub serial I2C engine Neil Armstrong
2022-11-29 14:47 ` [PATCH v3 3/6] soc: qcom: geni-se: add desc struct to specify clocks from device match data Neil Armstrong
2022-11-29 14:47 ` [PATCH v3 4/6] soc: qcom: geni-se: add support for I2C Master Hub wrapper variant Neil Armstrong
2022-11-29 14:47 ` [PATCH v3 5/6] i2c: qcom-geni: add desc struct to prepare support for I2C Master Hub variant Neil Armstrong
2022-11-29 14:47 ` [PATCH v3 6/6] i2c: qcom-geni: add " Neil Armstrong
2022-12-01 22:49 ` [PATCH v3 0/6] soc: qcom: add support for the I2C Master Hub Wolfram Sang
2022-12-05 8:31 ` Wolfram Sang [this message]
2022-12-05 8:37 ` Neil Armstrong
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=Y42sdXiCIpj2iaag@ninjato \
--to=wsa@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@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 NNTP newsgroup(s).