From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: <agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<sboyd@kernel.org>, <mturquette@baylibre.com>, <mani@kernel.org>,
<lpieralisi@kernel.org>, <bhelgaas@google.com>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-pci@vger.kernel.org>
Subject: Re: [PATCH 1/4] pcie: qcom: Fix the macro PARF_SLV_ADDR_SPACE_SIZE_2_3_3
Date: Fri, 30 Jun 2023 10:52:13 +0530 [thread overview]
Message-ID: <c226d063-a8e9-d9b8-e070-bc15f7c7ec47@quicinc.com> (raw)
In-Reply-To: <20230623180026.GA181743@bhelgaas>
Hi Bjorn,
On 6/23/2023 11:30 PM, Bjorn Helgaas wrote:
> On Fri, Jun 23, 2023 at 03:04:42PM +0530, Sricharan Ramabadhran wrote:
>> PARF_SLV_ADDR_SPACE_SIZE_2_3_3 macro used for IPQ8074
>> pcie slave addr size was initially set to 0x358, but
>> was wrongly changed to 0x168 as a part of
>> 'PCI: qcom: Sort and group registers and bitfield definitions'
>> Fixing it back to right value here.
>
> 1) Make your subject line match the history. For example, you're
> fixing 769e49d87b15 ("PCI: qcom: Sort and group registers ..."), so
> your subject line should start with "PCI: qcom: ...".
>
ok, will fix.
> 2) It doesn't look like 769e49d87b15 changed
> PARF_SLV_ADDR_SPACE_SIZE_2_3_3:
>
> $ git show 769e49d87b15 | grep PARF_SLV_ADDR_SPACE_SIZE_2_3_3
> +#define PARF_SLV_ADDR_SPACE_SIZE_2_3_3 0x16C /* Register offset specific to IP ver 2.3.3 */
> -#define PARF_SLV_ADDR_SPACE_SIZE_2_3_3 0x16C /* Register offset specific to IP rev 2.3.3 */
>
> What am I missing here? Do you have another out-of-tree patch that
> broke this?
39171b33f652 ("PCI: qcom: Remove PCIE20_ prefix from
register definitions") broke it. Will change and post .
Regards,
Sricharan
next prev parent reply other threads:[~2023-06-30 5:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 9:34 [PATCH 0/4] IPQ8074 pcie/wcss fixes Sricharan Ramabadhran
2023-06-23 9:34 ` [PATCH 1/4] pcie: qcom: Fix the macro PARF_SLV_ADDR_SPACE_SIZE_2_3_3 Sricharan Ramabadhran
2023-06-23 17:42 ` Bjorn Helgaas
2023-06-23 18:00 ` Bjorn Helgaas
2023-06-30 5:22 ` Sricharan Ramabadhran [this message]
2023-06-24 6:32 ` Manivannan Sadhasivam
2023-06-30 5:24 ` Sricharan Ramabadhran
2023-06-23 9:34 ` [PATCH 2/4] dt-bindings: clock: qcom: Add reset for WCSSAON Sricharan Ramabadhran
2023-06-23 9:34 ` [PATCH 3/4] clk: qcom: Add WCSSAON reset Sricharan Ramabadhran
2023-06-24 6:34 ` [PATCH 0/4] IPQ8074 pcie/wcss fixes Manivannan Sadhasivam
2023-06-30 5:23 ` Sricharan Ramabadhran
-- strict thread matches above, loose matches on Subject: below --
2023-06-23 9:43 Sricharan Ramabadhran
2023-06-23 9:44 ` [PATCH 1/4] pcie: qcom: Fix the macro PARF_SLV_ADDR_SPACE_SIZE_2_3_3 Sricharan Ramabadhran
2023-06-23 10:22 ` Konrad Dybcio
2023-06-23 10:41 ` Sricharan Ramabadhran
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=c226d063-a8e9-d9b8-e070-bc15f7c7ec47@quicinc.com \
--to=quic_srichara@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=helgaas@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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