public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Acayan <mailingradian@gmail.com>
To: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>,
	Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Richard Acayan <mailingradian@gmail.com>,
	Melody Olvera <quic_molvera@quicinc.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH 2/5] dmaengine: qcom: gpi: document preferred SM6350 binding
Date: Mon, 17 Oct 2022 18:00:04 -0400	[thread overview]
Message-ID: <20221017220004.6234-1-mailingradian@gmail.com> (raw)
In-Reply-To: <801c902d-4e1a-6ddc-e050-afdc2514e687@linaro.org>

> On 17/10/2022 17:23, Richard Acayan wrote:
>>> Devices with ee offset of 0x10000 should rather bind with SM6350
>>> compatible, so the list will not unnecessarily grow for compatible
>>> devices.
>>>
>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>> ---
>>>  drivers/dma/qcom/gpi.c | 7 ++++---
>>>  1 file changed, 4 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/dma/qcom/gpi.c b/drivers/dma/qcom/gpi.c
>>> index f8e19e6e6117..061add832295 100644
>>> --- a/drivers/dma/qcom/gpi.c
>>> +++ b/drivers/dma/qcom/gpi.c
>>> @@ -2286,13 +2286,14 @@ static int gpi_probe(struct platform_device *pdev)
>>>  }
>>>  
>>>  static const struct of_device_id gpi_of_match[] = {
>>> -	{ .compatible = "qcom,sc7280-gpi-dma", .data = (void *)0x10000 },
>>>  	{ .compatible = "qcom,sdm845-gpi-dma", .data = (void *)0x0 },
>>>  	{ .compatible = "qcom,sm6350-gpi-dma", .data = (void *)0x10000 },
>>>  	/*
>>> -	 * Deprecated, devices with ee_offset = 0 should use sdm845-gpi-dma as
>>> -	 * fallback and not need their own entries here.
>> 
>> This comment is from the dependency series [1]. Why would we need to add it just
>> to remove it here? I was not notified that the dependency was applied anywhere
>> (except as a base for other series) so it's not set in stone. Let's just drop
>> the original patch that this comment originates from to prevent needlessly
>> adding and removing the same lines at once.
> 
> I don't remove the comment, I re-phrase it to be better suited for final
> code.

Yes, I didn't word that exactly right. I still think the patch that adds this is
now useless if it's just going to be replaced. Do you think I should keep the
patch that this comment originates from, even though we already know exactly how
its substantial contents will be replaced?

We can't modify history and drop commits on kernel trees, but I can still send
a v6 series that drops the original comment.

> 
> Best regards,
> Krzysztof
> 

  reply	other threads:[~2022-10-17 22:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-15 14:04 [PATCH 0/5] dma/arm64: qcom: use one compatible also for 0x10000 offset Krzysztof Kozlowski
2022-10-15 14:04 ` [PATCH 1/5] dt-bindings: dma: qcom: gpi: use sm6350 fallback Krzysztof Kozlowski
2022-10-17 10:37   ` Vinod Koul
2022-10-17 21:35     ` Krzysztof Kozlowski
2022-10-17 18:33   ` Rob Herring
2022-10-17 21:10   ` Richard Acayan
2022-10-17 21:34     ` Krzysztof Kozlowski
2022-10-15 14:04 ` [PATCH 2/5] dmaengine: qcom: gpi: document preferred SM6350 binding Krzysztof Kozlowski
2022-10-17 21:23   ` Richard Acayan
2022-10-17 21:36     ` Krzysztof Kozlowski
2022-10-17 22:00       ` Richard Acayan [this message]
2022-10-17 22:12         ` Krzysztof Kozlowski
2022-10-18  0:37           ` Richard Acayan
2022-10-15 14:04 ` [PATCH 3/5] arm64: dts: qcom: sc7280: Add GPI DMA compatible fallback Krzysztof Kozlowski
2022-10-18 13:45   ` Neil Armstrong
2022-10-15 14:04 ` [PATCH 4/5] arm64: dts: qcom: sm8350: " Krzysztof Kozlowski
2022-10-18 13:45   ` Neil Armstrong
2022-10-15 14:04 ` [PATCH 5/5] arm64: dts: qcom: sm8450: " Krzysztof Kozlowski
2022-10-18 13:45   ` 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=20221017220004.6234-1-mailingradian@gmail.com \
    --to=mailingradian@gmail.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_molvera@quicinc.org \
    --cc=robh+dt@kernel.org \
    --cc=vkoul@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