[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0feeb2ae-a332-d645-28b0-e16890b286e1@quicinc.com>
Date: Tue, 4 Oct 2022 15:05:05 -0500
From: Melody Olvera <quic_molvera@...cinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
CC: Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Vinod Koul <vkoul@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
<linux-arm-msm@...r.kernel.org>, <dmaengine@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] dmaengine: qcom: gpi: Add compatible for QDU1000 and
QRU1000
On 10/1/2022 4:30 AM, Krzysztof Kozlowski wrote:
> On 01/10/2022 09:14, Dmitry Baryshkov wrote:
>> On Sat, 1 Oct 2022 at 06:08, Melody Olvera <quic_molvera@...cinc.com> wrote:
>>> Add compatible fields for the Qualcomm QDU1000 and QRU1000 SoCs.
>>>
>>> Signed-off-by: Melody Olvera <quic_molvera@...cinc.com>
>>> ---
>>> drivers/dma/qcom/gpi.c | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/drivers/dma/qcom/gpi.c b/drivers/dma/qcom/gpi.c
>>> index 8f0c9c4e2efd..94f92317979c 100644
>>> --- a/drivers/dma/qcom/gpi.c
>>> +++ b/drivers/dma/qcom/gpi.c
>>> @@ -2292,6 +2292,8 @@ static const struct of_device_id gpi_of_match[] = {
>>> { .compatible = "qcom,sm8250-gpi-dma", .data = (void *)0x0 },
>>> { .compatible = "qcom,sm8350-gpi-dma", .data = (void *)0x10000 },
>>> { .compatible = "qcom,sm8450-gpi-dma", .data = (void *)0x10000 },
>>> + { .compatible = "qcom,qdu1000-gpi-dma", .data = (void *)0x10000 },
>>> + { .compatible = "qcom,qru1000-gpi-dma", .data = (void *)0x10000 },
>> As usual
Will address ordering.
> I would say - drop entire patch and rebase patchset on:
>
> https://patchwork.kernel.org/project/linux-arm-msm/list/?series=680815&state=*
Sure thing; will rebase.
>
> Best regards,
> Krzysztof
Thanks,
Melody
Powered by blists - more mailing lists