From: <Claudiu.Beznea@microchip.com>
To: <Horatiu.Vultur@microchip.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>
Cc: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<richardcochran@gmail.com>, <Nicolas.Ferre@microchip.com>
Subject: Re: [PATCH] ARM: dts: lan966x: Add support for SMA connectors
Date: Mon, 22 May 2023 09:41:26 +0000 [thread overview]
Message-ID: <db4a26f5-2255-f77d-44b2-e1c5fefc0dbf@microchip.com> (raw)
In-Reply-To: <20230421113758.3465678-1-horatiu.vultur@microchip.com>
On 21.04.2023 14:37, Horatiu Vultur wrote:
> The pcb8309 has 2 SMA connectors which are connected to the lan966x
> chip. The lan966x can generate 1PPS output on one of them and it can
> receive 1PPS input on the other one.
>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
Applied to at91-dt, thanks!
> ---
> arch/arm/boot/dts/lan966x-pcb8309.dts | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm/boot/dts/lan966x-pcb8309.dts b/arch/arm/boot/dts/lan966x-pcb8309.dts
> index c436cd20d4b4c..0cb505f79ba1a 100644
> --- a/arch/arm/boot/dts/lan966x-pcb8309.dts
> +++ b/arch/arm/boot/dts/lan966x-pcb8309.dts
> @@ -144,6 +144,18 @@ fc4_b_pins: fc4-b-pins {
> function = "fc4_b";
> };
>
> + pps_out_pins: pps-out-pins {
> + /* 1pps output */
> + pins = "GPIO_38";
> + function = "ptpsync_3";
> + };
> +
> + ptp_ext_pins: ptp-ext-pins {
> + /* 1pps input */
> + pins = "GPIO_39";
> + function = "ptpsync_4";
> + };
> +
> sgpio_a_pins: sgpio-a-pins {
> /* SCK, D0, D1, LD */
> pins = "GPIO_32", "GPIO_33", "GPIO_34", "GPIO_35";
> @@ -212,5 +224,7 @@ gpio@1 {
> };
>
> &switch {
> + pinctrl-0 = <&pps_out_pins>, <&ptp_ext_pins>;
> + pinctrl-names = "default";
> status = "okay";
> };
prev parent reply other threads:[~2023-05-22 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 11:37 [PATCH] ARM: dts: lan966x: Add support for SMA connectors Horatiu Vultur
2023-05-21 15:10 ` Horatiu Vultur
2023-05-22 9:41 ` Claudiu.Beznea [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=db4a26f5-2255-f77d-44b2-e1c5fefc0dbf@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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