From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Suraj Jaiswal <quic_jsuraj@quicinc.com>,
Vinod Koul <vkoul@kernel.org>,
Bhupesh Sharma <bhupesh.sharma@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.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>,
Andrew Halaney <ahalaney@redhat.com>
Cc: kernel@quicinc.com
Subject: Re: [PATCH net-next v3 3/3] net: stmmac: Add driver support for DWMAC5 fault IRQ Support
Date: Thu, 23 Nov 2023 12:55:38 +0100 [thread overview]
Message-ID: <1e02f4f8-ebd3-4f57-98a9-48d7e08c0ad4@linaro.org> (raw)
In-Reply-To: <62eaaace3713751cb1ecac3163e857737107ca0e.1700737841.git.quic_jsuraj@quicinc.com>
On 11/23/23 12:38, Suraj Jaiswal wrote:
> Add IRQ support to listen HW fault like ECC,DPP,FSM
> fault and print the fault information in the kernel
> log.
>
> Signed-off-by: Suraj Jaiswal <quic_jsuraj@quicinc.com>
> ---
> drivers/net/ethernet/stmicro/stmmac/common.h | 1 +
> drivers/net/ethernet/stmicro/stmmac/stmmac.h | 2 ++
> .../net/ethernet/stmicro/stmmac/stmmac_main.c | 18 +++++++++++++++++
> .../ethernet/stmicro/stmmac/stmmac_platform.c | 20 +++++++++++++++++++
> 4 files changed, 41 insertions(+)
>
> diff --git a/drivers/net/ethernet/stmicro/stmmac/common.h b/drivers/net/ethernet/stmicro/stmmac/common.h
> index 6b935922054d..c4821c7ab674 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/common.h
> +++ b/drivers/net/ethernet/stmicro/stmmac/common.h
> @@ -347,6 +347,7 @@ enum request_irq_err {
> REQ_IRQ_ERR_SFTY_UE,
> REQ_IRQ_ERR_SFTY_CE,
> REQ_IRQ_ERR_LPI,
> + REQ_IRQ_ERR_SAFETY,
> REQ_IRQ_ERR_WOL,
> REQ_IRQ_ERR_MAC,
> REQ_IRQ_ERR_NO,
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac.h b/drivers/net/ethernet/stmicro/stmmac/stmmac.h
> index cd7a9768de5f..8893d4b7fa38 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac.h
> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac.h
> @@ -33,6 +33,7 @@ struct stmmac_resources {
> int irq;
> int sfty_ce_irq;
> int sfty_ue_irq;
> + int safety_common_intr;
> int rx_irq[MTL_MAX_RX_QUEUES];
> int tx_irq[MTL_MAX_TX_QUEUES];
> };
> @@ -331,6 +332,7 @@ struct stmmac_priv {
> /* XDP BPF Program */
> unsigned long *af_xdp_zc_qps;
> struct bpf_prog *xdp_prog;
> + int safety_common_intr;
other interrupts use _irq yet you seem to use _intr, plus the
aforementioned "safety" vs "fault" naming
[...]
>
> +int stmmac_get_fault_intr_config(struct platform_device *pdev, struct stmmac_resources *res)
> +{
> + int ret = 0;
get rid of ret and return directly
> +
> + res->safety_common_intr = platform_get_irq_byname(pdev, "safety");
> +
stray newline?
> + if (res->safety_common_intr < 0) {
> + if (res->safety_common_intr != -EPROBE_DEFER)
> + dev_err(&pdev->dev, "safety IRQ configuration information not found\n");
> + ret = 1;
> + }
> +
> + return ret;
> +}
> +
> int stmmac_get_platform_resources(struct platform_device *pdev,
> struct stmmac_resources *stmmac_res)
> {
> + int ret = 0;
Missing newline between declarations and code
Unnecessary initialization
> memset(stmmac_res, 0, sizeof(*stmmac_res));
>
> /* Get IRQ information early to have an ability to ask for deferred
> @@ -702,6 +718,10 @@ int stmmac_get_platform_resources(struct platform_device *pdev,
> if (stmmac_res->irq < 0)
> return stmmac_res->irq;
>
> + ret = stmmac_get_fault_intr_config(pdev, stmmac_res);
> + if (ret)
> + dev_err(&pdev->dev, "Fault interrupt not present\n");
Since you're getting the return value, perhaps the errno should
be propagated
Konrad
next prev parent reply other threads:[~2023-11-23 11:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 11:38 [PATCH net-next v3 0/3] Ethernet DWMAC5 fault IRQ support Suraj Jaiswal
2023-11-23 11:38 ` [PATCH net-next v3 1/3] dt-bindings: net: qcom,ethqos: add binding doc for fault IRQ for sa8775p Suraj Jaiswal
2023-11-23 11:44 ` Konrad Dybcio
2023-11-23 11:53 ` Suraj Jaiswal
2023-11-23 12:04 ` Suraj Jaiswal
2023-11-23 12:36 ` Rob Herring
2023-11-24 8:18 ` Krzysztof Kozlowski
2023-11-24 11:39 ` Suraj Jaiswal
2023-11-23 11:38 ` [PATCH net-next v3 2/3] arm64: dts: qcom: sa8775p: enable Fault IRQ Suraj Jaiswal
2023-11-23 11:53 ` Suraj Jaiswal
2023-11-24 8:19 ` Krzysztof Kozlowski
2023-11-24 8:20 ` Krzysztof Kozlowski
2023-11-24 15:23 ` kernel test robot
2023-11-23 11:38 ` [PATCH net-next v3 3/3] net: stmmac: Add driver support for DWMAC5 fault IRQ Support Suraj Jaiswal
2023-11-23 11:53 ` Suraj Jaiswal
2023-11-23 11:55 ` Konrad Dybcio [this message]
2023-11-23 14:34 ` Simon Horman
2023-11-23 20:02 ` Andrew Lunn
2023-11-24 13:19 ` kernel test robot
2023-11-24 14:39 ` kernel test robot
2023-11-27 20:08 ` Andrew Halaney
2023-11-23 11:53 ` [PATCH net-next v3 0/3] Ethernet DWMAC5 fault IRQ support Suraj Jaiswal
2023-11-23 11:57 ` Konrad Dybcio
2023-11-23 11:57 ` Konrad Dybcio
2023-11-23 19:54 ` Andrew Lunn
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=1e02f4f8-ebd3-4f57-98a9-48d7e08c0ad4@linaro.org \
--to=konrad.dybcio@linaro.org \
--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=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=quic_jsuraj@quicinc.com \
--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
all inboxes | Powered by JetHome®