Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Bjorn Andersson <bjorn.andersson@linaro.org>
To:     linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
        devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
        agross@kernel.org, robh+dt@kernel.org,
        Robert Marko <robimarko@gmail.com>
Subject: Re: (subset) [PATCH] arm64: dts: qcom: ipq6018: correct QUP peripheral labels
Date:   Sat,  2 Jul 2022 22:56:47 -0500
Message-Id: <165682055970.445910.17601664788092675117.b4-ty@linaro.org>
In-Reply-To: <20220604153003.55172-1-robimarko@gmail.com>
References: <20220604153003.55172-1-robimarko@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Sat, 4 Jun 2022 17:30:03 +0200, Robert Marko wrote:
> Current QUP peripheral labels like spi_0 and i2c_0 dont really tell what is
> the exact QUP HW being used as there are actually 6 identical QUP HW blocks
> for UART, SPI and I2C.
> For example current i2c_0 label actually points to the QUP2 I2C HW.
> 
> This style of labeling does not follow what the rest of Qualcomm SoC-s use,
> for example IPQ8074 which has the identical QUP blocks.
> It also makes it really hard to add the missing QUP DT nodes as there are
> multiple missing.
> 
> [...]

Applied, thanks!

[1/1] arm64: dts: qcom: ipq6018: correct QUP peripheral labels
      commit: f82c48d468521cd9d1a31797c6f9e6cac6f7c1b3

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