From: Suraj Jaiswal <quic_jsuraj@quicinc.com>
To: Andrew Halaney <ahalaney@redhat.com>
Cc: Vinod Koul <vkoul@kernel.org>,
Bhupesh Sharma <bhupesh.sharma@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
<netdev@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
Prasad Sodagudi <psodagud@quicinc.com>,
Rob Herring <robh@kernel.org>, <kernel@quicinc.com>
Subject: Re: [PATCH net-next v5 1/3] dt-bindings: net: qcom,ethqos: add binding doc for safety IRQ for sa8775p
Date: Tue, 12 Dec 2023 17:34:31 +0530 [thread overview]
Message-ID: <94e4e23c-232d-4b7e-84f3-939d32eed944@quicinc.com> (raw)
In-Reply-To: <2ihncgvnfxgzj5kfm3eedvj3jvru7fokpno5pdzgtnuuy2mpqf@sfuzuugeuxzh>
sure @andrew
Thanks
Suraj
On 12/11/2023 7:22 PM, Andrew Halaney wrote:
> On Mon, Dec 11, 2023 at 01:31:51PM +0530, Suraj Jaiswal wrote:
>> Add binding doc for safety IRQ. The safety IRQ will be
>> triggered for ECC(error correction code), DPP(data path
>> parity), FSM(finite state machine) error.
>>
>> Signed-off-by: Suraj Jaiswal <quic_jsuraj@quicinc.com>
>
> Rob gave you his Reviewed-by over here on the last revision:
>
> https://lore.kernel.org/netdev/170206782161.2661547.16311911491075108498.robh@kernel.org/
>
> in the future if someone gives you a tag you should add it to the patch
> for the next revision you send out (assuming you have to send out
> another version, otherwise the maintainers will collect the tags when
> they merge that version of the series). If the patches change a lot then
> it makes sense to remove the tag since it wasn't what they reviewed, but
> in this case you've only expanded a comment in the commit message so it is
> appropriate to be present.
>
>> ---
>> Documentation/devicetree/bindings/net/qcom,ethqos.yaml | 9 ++++++---
>> Documentation/devicetree/bindings/net/snps,dwmac.yaml | 6 ++++--
>> 2 files changed, 10 insertions(+), 5 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/net/qcom,ethqos.yaml b/Documentation/devicetree/bindings/net/qcom,ethqos.yaml
>> index 7bdb412a0185..93d21389e518 100644
>> --- a/Documentation/devicetree/bindings/net/qcom,ethqos.yaml
>> +++ b/Documentation/devicetree/bindings/net/qcom,ethqos.yaml
>> @@ -37,12 +37,14 @@ properties:
>> items:
>> - description: Combined signal for various interrupt events
>> - description: The interrupt that occurs when Rx exits the LPI state
>> + - description: The interrupt that occurs when HW safety error triggered
>>
>> interrupt-names:
>> minItems: 1
>> items:
>> - const: macirq
>> - - const: eth_lpi
>> + - enum: [eth_lpi, safety]
>> + - const: safety
>>
>> clocks:
>> maxItems: 4
>> @@ -89,8 +91,9 @@ examples:
>> <&gcc GCC_ETH_PTP_CLK>,
>> <&gcc GCC_ETH_RGMII_CLK>;
>> interrupts = <GIC_SPI 56 IRQ_TYPE_LEVEL_HIGH>,
>> - <GIC_SPI 55 IRQ_TYPE_LEVEL_HIGH>;
>> - interrupt-names = "macirq", "eth_lpi";
>> + <GIC_SPI 55 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 782 IRQ_TYPE_LEVEL_HIGH>;
>> + interrupt-names = "macirq", "eth_lpi", "safety";
>>
>> rx-fifo-depth = <4096>;
>> tx-fifo-depth = <4096>;
>> diff --git a/Documentation/devicetree/bindings/net/snps,dwmac.yaml b/Documentation/devicetree/bindings/net/snps,dwmac.yaml
>> index 5c2769dc689a..3b46d69ea97d 100644
>> --- a/Documentation/devicetree/bindings/net/snps,dwmac.yaml
>> +++ b/Documentation/devicetree/bindings/net/snps,dwmac.yaml
>> @@ -107,13 +107,15 @@ properties:
>> - description: Combined signal for various interrupt events
>> - description: The interrupt to manage the remote wake-up packet detection
>> - description: The interrupt that occurs when Rx exits the LPI state
>> + - description: The interrupt that occurs when HW safety error triggered
>>
>> interrupt-names:
>> minItems: 1
>> items:
>> - const: macirq
>> - - enum: [eth_wake_irq, eth_lpi]
>> - - const: eth_lpi
>> + - enum: [eth_wake_irq, eth_lpi, safety]
>> + - enum: [eth_wake_irq, eth_lpi, safety]
>> + - enum: [eth_wake_irq, eth_lpi, safety]
>>
>> clocks:
>> minItems: 1
>> --
>> 2.25.1
>>
>
next prev parent reply other threads:[~2023-12-12 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 8:01 [PATCH net-next v5 0/3] Ethernet DWMAC5 fault IRQ support Suraj Jaiswal
2023-12-11 8:01 ` [PATCH net-next v5 1/3] dt-bindings: net: qcom,ethqos: add binding doc for safety IRQ for sa8775p Suraj Jaiswal
2023-12-11 13:52 ` Andrew Halaney
2023-12-12 12:04 ` Suraj Jaiswal [this message]
2023-12-11 8:01 ` [PATCH net-next v5 2/3] arm64: dts: qcom: sa8775p: enable safety IRQ Suraj Jaiswal
2023-12-11 9:34 ` Konrad Dybcio
2023-12-11 8:01 ` [PATCH net-next v5 3/3] net: stmmac: Add driver support for DWMAC5 safety IRQ support Suraj Jaiswal
2023-12-11 13:55 ` Serge Semin
2023-12-12 12:02 ` Suraj Jaiswal
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=94e4e23c-232d-4b7e-84f3-939d32eed944@quicinc.com \
--to=quic_jsuraj@quicinc.com \
--cc=agross@kernel.org \
--cc=ahalaney@redhat.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=bhupesh.sharma@linaro.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=psodagud@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).