All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
	Emil Renner Berthing <kernel@esmil.dk>,
	Hal Feng <hal.feng@starfivetech.com>,
	Michael Turquette <mturquette@baylibre.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel@collabora.com,
	Emil Renner Berthing <emil.renner.berthing@canonical.com>,
	Jacob Keller <jacob.e.keller@intel.com>
Subject: Re: [PATCH 1/2] clk: starfive: Add flags argument to JH71X0__MUX macro
Date: Wed, 20 Dec 2023 20:38:12 -0800	[thread overview]
Message-ID: <2c37cada9bb4be59bf06fa9a9df81e07.sboyd@kernel.org> (raw)
In-Reply-To: <20231219232442.2460166-2-cristian.ciocaltea@collabora.com>

Quoting Cristian Ciocaltea (2023-12-19 15:24:39)
> From: Emil Renner Berthing <emil.renner.berthing@canonical.com>
> 
> This flag is needed to add the CLK_SET_RATE_PARENT flag on the gmac_tx
> clock on the JH7100, which in turn is needed by the dwmac-starfive
> driver to set the clock properly for 1000, 100 and 10 Mbps links.
> 
> This change was mostly made using coccinelle:
> 
> @ match @
> expression idx, name, nparents;
> @@
>  JH71X0__MUX(
> -idx, name, nparents,
> +idx, name, 0, nparents,
>  ...)
> 
> Signed-off-by: Emil Renner Berthing <emil.renner.berthing@canonical.com>
> Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
> Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
> ---

Applied to clk-next

  reply	other threads:[~2023-12-21  4:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 23:24 [PATCH 0/2] Clock changes to improve dwmac-starfive ethernet Cristian Ciocaltea
2023-12-19 23:24 ` [PATCH 1/2] clk: starfive: Add flags argument to JH71X0__MUX macro Cristian Ciocaltea
2023-12-21  4:38   ` Stephen Boyd [this message]
2023-12-19 23:24 ` [PATCH 2/2] clk: starfive: jh7100: Add CLK_SET_RATE_PARENT to gmac_tx Cristian Ciocaltea
2023-12-21  4:38   ` Stephen Boyd

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=2c37cada9bb4be59bf06fa9a9df81e07.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=emil.renner.berthing@canonical.com \
    --cc=hal.feng@starfivetech.com \
    --cc=jacob.e.keller@intel.com \
    --cc=kernel@collabora.com \
    --cc=kernel@esmil.dk \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.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.