mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <ckeepax@opensource.cirrus.com>, <Nicolas.Ferre@microchip.com>,
	<davem@davemloft.net>, <kuba@kernel.org>
Cc: <andrew@lunn.ch>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v3] net: macb: Correct usage of MACB_CAPS_CLK_HW_CHG flag
Date: Mon, 4 Jan 2021 14:04:06 +0000	[thread overview]
Message-ID: <8f36997b-2310-0579-173d-17f532a54d8d@microchip.com> (raw)
In-Reply-To: <20210104103802.13091-1-ckeepax@opensource.cirrus.com>

Hi Charles,

On 04.01.2021 12:38, Charles Keepax wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> A new flag MACB_CAPS_CLK_HW_CHG was added and all callers of
> macb_set_tx_clk were gated on the presence of this flag.
> 
> -   if (!clk)
> + if (!bp->tx_clk || !(bp->caps & MACB_CAPS_CLK_HW_CHG))
> 
> However the flag was not added to anything other than the new
> sama7g5_gem, turning that function call into a no op for all other
> systems. This breaks the networking on Zynq.
> 
> The commit message adding this states: a new capability so that
> macb_set_tx_clock() to not be called for IPs having this
> capability
> 
> This strongly implies that present of the flag was intended to skip
> the function not absence of the flag. Update the if statement to
> this effect, which repairs the existing users.

Yes, the presence of the flag should involve skipping the calling of
clk_set_rate() since the IP logic would take care of proper clock division
depending on the link speed. I wrongly cherry pick this one from internal
branches. Sorry for this breakage.

> 
> Fixes: daafa1d33cc9 ("net: macb: add capability to not set the clock rate")
> Suggested-by: Andrew Lunn <andrew@lunn.ch>
> Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>

Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>

> ---
> 
> Changes since v1:
>  - Updated flag semantics to skip function, as appears to have been
>    intended by the initial commit.
> 
> Changes since v2:
>  - Adding "net" to the subject line
> 
> Thanks,
> Charles
> 
>  drivers/net/ethernet/cadence/macb_main.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/cadence/macb_main.c b/drivers/net/ethernet/cadence/macb_main.c
> index d5d910916c2e8..814a5b10141d1 100644
> --- a/drivers/net/ethernet/cadence/macb_main.c
> +++ b/drivers/net/ethernet/cadence/macb_main.c
> @@ -467,7 +467,7 @@ static void macb_set_tx_clk(struct macb *bp, int speed)
>  {
>         long ferr, rate, rate_rounded;
> 
> -       if (!bp->tx_clk || !(bp->caps & MACB_CAPS_CLK_HW_CHG))
> +       if (!bp->tx_clk || (bp->caps & MACB_CAPS_CLK_HW_CHG))
>                 return;
> 
>         switch (speed) {
> --
> 2.11.0
> 

  reply	other threads:[~2021-01-04 14:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 10:38 Charles Keepax
2021-01-04 14:04 ` Claudiu.Beznea [this message]
2021-01-04 14:18 ` Andrew Lunn
2021-01-04 21:30   ` 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=8f36997b-2310-0579-173d-17f532a54d8d@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.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®