From: Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Vladimir Oltean <olteanv@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: dsa: sja1105: Add rev-rmii support sja1110 devices
Date: Wed, 10 Jun 2026 12:00:28 +0200 [thread overview]
Message-ID: <58a4f1fb-3bae-4d47-9617-d22e3d7e0ef2@prodrive-technologies.com> (raw)
In-Reply-To: <20260609185915.7aa34d8e@kernel.org>
Hi
On 10/06/2026 03:59, Jakub Kicinski wrote:
> On Mon, 8 Jun 2026 16:16:51 +0200 Martijn de Gouw wrote:
>> When a rmii port is used in phy-mode (rev-rmii), the ref_clk is an input on
>> the rx clk pin. Configure both the rx and tx clock source to use the
>> rx_clk as external clock source input.
>
> drivers/net/dsa/sja1105/sja1105_clocking.c:969:5: warning: no previous prototype for function 'sja1110_clocking_setup_port' [-Wmissing-prototypes]
> 969 | int sja1110_clocking_setup_port(struct sja1105_private *priv, int port)
> | ^
> drivers/net/dsa/sja1105/sja1105_clocking.c:969:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
> 969 | int sja1110_clocking_setup_port(struct sja1105_private *priv, int port)
> | ^
> | static
Looking into why sja1105_clocking_setup_port is not declared static as
well reveals that sja1105_clocking_setup_port is called directly from
sja1105_set_port_speed() in sja1105_main.c as well. I think this should
also be handled via the struct sja1105_info. If this port specific
function is available via the info struct, there is also no longer a
need to have a sja1105/sja1110 specific clocking_setup() function.
Unless there are additional comments I'll try to form a patch-series
that implements this.
Regards, Martijn
prev parent reply other threads:[~2026-06-10 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 14:16 Martijn de Gouw
2026-06-10 1:59 ` Jakub Kicinski
2026-06-10 10:00 ` Martijn de Gouw [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=58a4f1fb-3bae-4d47-9617-d22e3d7e0ef2@prodrive-technologies.com \
--to=martijn.de.gouw@prodrive-technologies.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®