From: patchwork-bot+netdevbpf@kernel.org
To: Yannick Vignon <yannick.vignon@oss.nxp.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@st.com,
joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, yannick.vignon@nxp.com
Subject: Re: [PATCH net v2 1/2] net: stmmac: fix taprio schedule configuration
Date: Thu, 14 Jan 2021 19:00:11 +0000 [thread overview]
Message-ID: <161065081116.20848.13616158602957995234.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210113131557.24651-1-yannick.vignon@oss.nxp.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Wed, 13 Jan 2021 14:15:56 +0100 you wrote:
> From: Yannick Vignon <yannick.vignon@nxp.com>
>
> When configuring a 802.1Qbv schedule through the tc taprio qdisc on an NXP
> i.MX8MPlus device, the effective cycle time differed from the requested one
> by N*96ns, with N number of entries in the Qbv Gate Control List. This is
> because the driver was adding a 96ns margin to each interval of the GCL,
> apparently to account for the IPG. The problem was observed on NXP
> i.MX8MPlus devices but likely affected all devices relying on the same
> configuration callback (dwmac 4.00, 4.10, 5.10 variants).
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net: stmmac: fix taprio schedule configuration
https://git.kernel.org/netdev/net/c/b76889ff51bf
- [net,v2,2/2] net: stmmac: fix taprio configuration when base_time is in the past
https://git.kernel.org/netdev/net/c/fe28c53ed71d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-01-14 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 13:15 [PATCH net v2 1/2] net: stmmac: fix taprio schedule configuration Yannick Vignon
2021-01-13 13:15 ` [PATCH net v2 2/2] net: stmmac: fix taprio configuration when base_time is in the past Yannick Vignon
2021-01-14 19:00 ` patchwork-bot+netdevbpf [this message]
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=161065081116.20848.13616158602957995234.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=davem@davemloft.net \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=yannick.vignon@nxp.com \
--cc=yannick.vignon@oss.nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.