linux-kernel - Re: [PATCH v3 0/6] soc: qcom: add support for the I2C Master Hub

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y4kvcXTdwImZpaU1@shikoro>
Date:   Thu, 1 Dec 2022 23:49:21 +0100
From:   Wolfram Sang <wsa@...nel.org>
To:     Neil Armstrong <neil.armstrong@...aro.org>
Cc:     Bjorn Andersson <andersson@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Andy Gross <agross@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        linux-i2c@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/6] soc: qcom: add support for the I2C Master Hub

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?


Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)