linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Josua Mayer <josua@solid-run.com>
To: Andrew Lunn <andrew@lunn.ch>,
	Gregory Clement <gregory.clement@bootlin.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>, Rob Herring <robh@kernel.org>
Cc: Yazan Shhady <yazan.shhady@solid-run.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 4/4] arm64: dts: add description for solidrun cn9131 solidwan board
Date: Thu, 2 May 2024 17:35:44 +0000	[thread overview]
Message-ID: <d72c7637-e59f-4104-93e9-6faab2da0836@solid-run.com> (raw)
In-Reply-To: <20240502-cn9130-som-v4-4-0a2e2f1c70d8@solid-run.com>

Am 02.05.24 um 14:32 schrieb Josua Mayer:
> Add description for the SolidRun CN9131 SolidWAN, based on CN9130 SoM
> with an extra communication  processor on the carrier board.
>
> This board differentiates itself from CN9130 Clearfog by providing
> additional SoC native network interfaces and pci buses:
> 2x 10Gbps SFP+
> 4x 1Gbps RJ45
> 1x miniPCI-E
> 1x m.2 b-key with sata, usb-2.0 and usb-3.0
> 1x m.2 m-key with pcie and usb-2.0
> 1x m.2 b-key with pcie, usb-2.0, usb-3.0 and 2x sim slots
> 1x mpcie with pcie only
> 2x type-a usb-2.0/3.0
>
> Signed-off-by: Josua Mayer <josua@solid-run.com>
> ---
>  arch/arm64/boot/dts/marvell/Makefile               |   1 +
>  arch/arm64/boot/dts/marvell/cn9131-cf-solidwan.dts | 643 +++++++++++++++++++++
>  2 files changed, 644 insertions(+)
>
cut
> +	/* Type-A port on J53 */
> +	reg_usb_a_vbus0: regulator-usb-a-vbus0 {
> +		compatible = "regulator-fixed";
> +		pinctrl-0 = <&cp0_reg_usb_a_vbus0_pins>;
> +		pinctrl-names = "default";
> +		regulator-name = "vbus0";
> +		regulator-min-microvolt = <5000000>;
> +		regulator-max-microvolt = <5000000>;
> +		regulator-oc-protection-microamp = <1000000>;

Is it correct to specify over-current protection for a regulator-fixed? It causes kernel messages:

[ 7.988337] vbus0: IC does not support requested over-current limits [ 7.994756] vbus0: IC does not support requested over voltage limits [ 7.998796] vbus1: IC does not support requested over-current limits ...

The reason I put the property was that the 1A limit is a property of the regulator component (NCP380-1.0A). Maybe that is the wrong property?

It also generates an interrupt for which I found no suitable description.

> +		gpio = <&cp0_gpio1 27 GPIO_ACTIVE_HIGH>;
> +		enable-active-high;
> +		regulator-always-on;
> +	};
> +
> +	reg_usb_a_vbus1: regulator-usb-a-vbus1 {
> +		compatible = "regulator-fixed";
> +		pinctrl-0 = <&cp0_reg_usb_a_vbus1_pins>;
> +		pinctrl-names = "default";
> +		regulator-name = "vbus1";
> +		regulator-min-microvolt = <5000000>;
> +		regulator-max-microvolt = <5000000>;
> +		regulator-oc-protection-microamp = <1000000>;
same here
> +		gpio = <&cp0_gpio1 28 GPIO_ACTIVE_HIGH>;
> +		enable-active-high;
> +		regulator-always-on;
> +	};
> +
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-05-02 17:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 12:32 [PATCH v4 0/4] arm64: dts: add description for solidrun cn9130 som and clearfog boards Josua Mayer
2024-05-02 12:32 ` [PATCH v4 1/4] dt-bindings: arm64: marvell: add solidrun cn9130 som based boards Josua Mayer
2024-05-02 12:32 ` [PATCH v4 2/4] dt-bindings: arm64: marvell: add solidrun cn9132 CEX-7 evaluation board Josua Mayer
2024-05-02 12:32 ` [PATCH v4 3/4] arm64: dts: add description for solidrun cn9130 som and clearfog boards Josua Mayer
2024-05-02 12:32 ` [PATCH v4 4/4] arm64: dts: add description for solidrun cn9131 solidwan board Josua Mayer
2024-05-02 15:20   ` Rob Herring
2024-05-02 17:24     ` Josua Mayer
2024-05-02 17:35   ` Josua Mayer [this message]
2024-05-03 13:24     ` Rob Herring
2024-05-05 10:27       ` Josua Mayer
2024-05-02 15:08 ` [PATCH v4 0/4] arm64: dts: add description for solidrun cn9130 som and clearfog boards Rob Herring (Arm)

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=d72c7637-e59f-4104-93e9-6faab2da0836@solid-run.com \
    --to=josua@solid-run.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=yazan.shhady@solid-run.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;
as well as URLs for NNTP newsgroup(s).