From: Paolo Abeni <pabeni@redhat.com>
To: Parker Newman <parker@finest.io>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Parker Newman <pnewman@connecttech.com>
Subject: Re: [PATCH v1 1/1] net: stmmac: dwmac-tegra: Read iommu stream id from device tree
Date: Fri, 15 Nov 2024 18:17:07 +0100 [thread overview]
Message-ID: <ed2ec1c2-65c7-4768-99f1-987e5fa39a54@redhat.com> (raw)
In-Reply-To: <f2a14edb5761d372ec939ccbea4fb8dfd1fdab91.1731685185.git.pnewman@connecttech.com>
On 11/15/24 17:31, Parker Newman wrote:
> From: Parker Newman <pnewman@connecttech.com>
>
> Read the iommu stream id from device tree rather than hard coding to mgbe0.
> Fixes kernel panics when using mgbe controllers other than mgbe0.
It's better to include the full Oops backtrace, possibly decoded.
> Tested with Orin AGX 64GB module on Connect Tech Forge carrier board.
Since this looks like a fix, you should include a suitable 'Fixes' tag
here, and specify the 'net' target tree in the subj prefix.
> @@ -241,6 +243,12 @@ static int tegra_mgbe_probe(struct platform_device *pdev)
> if (IS_ERR(mgbe->xpcs))
> return PTR_ERR(mgbe->xpcs);
>
> + /* get controller's stream id from iommu property in device tree */
> + if (!tegra_dev_iommu_get_stream_id(mgbe->dev, &mgbe->iommu_sid)) {
> + dev_err(mgbe->dev, "failed to get iommu stream id\n");
> + return -EINVAL;
> + }
I *think* it would be better to fallback (possibly with a warning or
notice) to the previous default value when the device tree property is
not available, to avoid regressions.
Thanks,
Paolo
next prev parent reply other threads:[~2024-11-15 17:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 16:31 [PATCH v1 0/1] " Parker Newman
2024-11-15 16:31 ` [PATCH v1 1/1] " Parker Newman
2024-11-15 17:17 ` Paolo Abeni [this message]
2024-11-15 18:59 ` Parker Newman
2024-11-16 19:22 ` Andrew Lunn
2024-11-18 13:44 ` Parker Newman
2024-11-19 0:50 ` Andrew Lunn
2024-11-19 18:13 ` Parker Newman
2024-11-19 19:18 ` Andrew Lunn
2024-11-19 19:47 ` Parker Newman
2024-12-04 16:23 ` Thierry Reding
2024-12-04 16:53 ` Parker Newman
2024-12-04 18:06 ` Thierry Reding
2024-12-06 13:42 ` Parker Newman
2024-12-06 16:01 ` Thierry Reding
2024-12-10 18:49 ` Parker Newman
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=ed2ec1c2-65c7-4768-99f1-987e5fa39a54@redhat.com \
--to=pabeni@redhat.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=jonathanh@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-tegra@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=parker@finest.io \
--cc=pnewman@connecttech.com \
--cc=thierry.reding@gmail.com \
/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®