mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Karumanchi, Vineeth" <vineeth.karumanchi@amd.com>
To: claudiu beznea <claudiu.beznea@tuxon.dev>,
	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: Tue, 6 Feb 2024 21:14:21 +0530	[thread overview]
Message-ID: <70a44ceb-2d52-4189-af42-b56e8f60d0f2@amd.com> (raw)
In-Reply-To: <d8c48839-8b22-47ad-b270-e96a1ad1adee@tuxon.dev>

Hi Claudiu,


On 2/3/2024 9:08 PM, claudiu beznea wrote:
<...>
>> +		for (q = 0, queue = bp->queues; q < bp->num_queues;
>> +		     ++q, ++queue) {
>> +			/* Disable RX queues */
> Operation in this for loop could be moved in the the above IRQ disable
> loop. Have you tried it? are there any issues with it?

OK. I haven't tried it. I will try and update.

> 
>> +			if (bp->caps & MACB_CAPS_QUEUE_DISABLE) {
>> +				queue_writel(queue, RBQP, GEM_RBQP_DISABLE);
>> +			} else {
>> +				/* Tie off RX queues */
>> +				queue_writel(queue, RBQP,
>> +					     lower_32_bits(bp->rx_ring_tieoff_dma));
> I think this should be guarded by:
> #ifdef CONFIG_ARCH_DMA_ADDR_T_64BIT
>> +				queue_writel(queue, RBQPH,
>> +					     upper_32_bits(bp->rx_ring_tieoff_dma));
>> +			}
>> +		}
>> +		/* Enable Receive engine */
>> +		ctrlmask = macb_readl(bp, NCR);
> Is this needed?

Yes, not needed, we can use earlier value directly.

> 
>> +		ctrlmask |= MACB_BIT(RE);
<...>
-- 
🙏 vineeth

  reply	other threads:[~2024-02-06 15:44 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 [this message]
2024-02-15  5:43     ` Karumanchi, Vineeth
2024-02-15 10:19       ` claudiu beznea
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=70a44ceb-2d52-4189-af42-b56e8f60d0f2@amd.com \
    --to=vineeth.karumanchi@amd.com \
    --cc=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 \
    /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

Powered by JetHome