From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: "Karumanchi, Vineeth" <vineeth.karumanchi@amd.com>,
nicolas.ferre@microchip.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, linux@armlinux.org.uk
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, git@amd.com
Subject: Re: [PATCH net-next 1/3] net: macb: queue tie-off or disable during WOL suspend
Date: Thu, 15 Feb 2024 12:19:56 +0200 [thread overview]
Message-ID: <0815e67c-36b8-4626-90a2-f11607915da2@tuxon.dev> (raw)
In-Reply-To: <6a8d100c-57a5-4c92-b744-453c106352ad@amd.com>
Hi, Vineeth,
On 15.02.2024 07:43, Karumanchi, Vineeth wrote:
> Hi Claudiu,
>
> On 2/3/2024 9:08 PM, claudiu beznea wrote:
> <...>
>>> queue->tx_skb = NULL;
>>> @@ -2568,6 +2574,16 @@ static int macb_alloc_consistent(struct macb *bp)
>>> if (bp->macbgem_ops.mog_alloc_rx_buffers(bp))
>>> goto out_err;
>>> + /* Required for tie off descriptor for PM cases */
>>> + if (!(bp->caps & MACB_CAPS_QUEUE_DISABLE)) {
>>> + bp->rx_ring_tieoff = dma_alloc_coherent(&bp->pdev->dev,
>>> + macb_dma_desc_get_size(bp),
>>> + &bp->rx_ring_tieoff_dma,
>>> + GFP_KERNEL);
>>> + if (!bp->rx_ring_tieoff)
>>> + goto out_err;
>> You also need to free the previously allocated rx buffers.
>
> Are you referring to (bp->macbgem_ops.mog_alloc_rx_buffers(bp)) allocation ?
> It was freed in macb_free_consistent():
> ...
> bp->macbgem_ops.mog_free_rx_buffers(bp);
> ...
You're right, my bad.
>
> Please let me know if you are referring to different buffers.
I was referring to bp->macbgem_ops.mog_alloc_rx_buffers but hat is covered
as you pointed out.
Thank you,
Claudiu Beznea
next prev parent reply other threads:[~2024-02-15 10:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 10:48 [PATCH net-next 0/3] net: macb: WOL enhancements Vineeth Karumanchi
2024-01-30 10:48 ` [PATCH net-next 1/3] net: macb: queue tie-off or disable during WOL suspend Vineeth Karumanchi
2024-02-03 15:38 ` claudiu beznea
2024-02-06 15:44 ` Karumanchi, Vineeth
2024-02-15 5:43 ` Karumanchi, Vineeth
2024-02-15 10:19 ` claudiu beznea [this message]
2024-01-30 10:48 ` [PATCH net-next 2/3] dt-bindings: net: cdns,macb: Add wol-arp-packet property Vineeth Karumanchi
2024-01-30 17:30 ` Conor Dooley
2024-01-31 7:23 ` Vineeth Karumanchi
2024-01-31 1:26 ` Andrew Lunn
2024-01-31 7:39 ` Vineeth Karumanchi
2024-01-31 7:45 ` Krzysztof Kozlowski
2024-01-31 13:18 ` Andrew Lunn
2024-02-01 6:41 ` Vineeth Karumanchi
2024-02-01 13:12 ` Andrew Lunn
2024-02-01 16:32 ` Karumanchi, Vineeth
2024-01-30 10:48 ` [PATCH net-next 3/3] net: macb: Add ARP support to WOL Vineeth Karumanchi
2024-01-30 21:27 ` Vadim Fedorenko
2024-01-31 2:13 ` [PATCH net-next 0/3] net: macb: WOL enhancements Jakub Kicinski
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=0815e67c-36b8-4626-90a2-f11607915da2@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=git@amd.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=vineeth.karumanchi@amd.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;
as well as URLs for NNTP newsgroup(s).