All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Dragan Simic <dsimic@manjaro.org>, Andy Yan <andyshrk@163.com>
Cc: krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 3/4] arm64: dts: rockchip: rename vcc5v0_usb30_host regulator for Cool Pi CM5 EVB
Date: Wed, 31 Jan 2024 15:24:16 +0100	[thread overview]
Message-ID: <2179538.KUTt5R2Mg1@diego> (raw)
In-Reply-To: <1e98352e.2dd2.18d5f780043.Coremail.andyshrk@163.com>

Am Mittwoch, 31. Januar 2024, 13:21:56 CET schrieb Andy Yan:
> 
> Hi Heiko:
> 
> 在 2024-01-27 21:09:46,"Dragan Simic" <dsimic@manjaro.org> 写道:
> >On 2024-01-27 13:15, Andy Yan wrote:
> >> At 2024-01-27 18:36:40, "Heiko Stübner" <heiko@sntech.de> wrote:
> >>> Am Samstag, 27. Januar 2024, 10:20:33 CET schrieb Andy Yan:
> >>>> According to the schematic, this regulator is used both for USB30 and
> >>>> USB20, so give it a more appropriate name.
> >>> 
> >>> I don't have the schematics, so I'll need you to answer this, but what
> >>> is the regulator called _in_ the schematics?
> >> 
> >> There are two regulators called VCC50_USB_HOST1 and VCC50_USB_HOST2,
> >> and they are both controlled by GPIO1_D5
> >> They both for two usb 2.0 hosts,  not usb 30, the schematics make
> >> me a bit confused.
> >
> >In that case, I'd say that renaming the regulator to vcc5v0_usb_host is
> >fine, but there should also be a comment in the board dts file that it's
> >actually two separate regulators.
> 
> How do you feel about this ? Or some other style like:
> vcc5v0_usb_host1: vcc5v0_usb_host2:vcc5v0-usb-host-regulator {

I think we're using such a scheme in some places already, and
yes I really like going this way. So that the phandles follow the
schematic names and we can still grep for things.


Heiko





_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Dragan Simic <dsimic@manjaro.org>, Andy Yan <andyshrk@163.com>
Cc: krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 3/4] arm64: dts: rockchip: rename vcc5v0_usb30_host regulator for Cool Pi CM5 EVB
Date: Wed, 31 Jan 2024 15:24:16 +0100	[thread overview]
Message-ID: <2179538.KUTt5R2Mg1@diego> (raw)
In-Reply-To: <1e98352e.2dd2.18d5f780043.Coremail.andyshrk@163.com>

Am Mittwoch, 31. Januar 2024, 13:21:56 CET schrieb Andy Yan:
> 
> Hi Heiko:
> 
> 在 2024-01-27 21:09:46,"Dragan Simic" <dsimic@manjaro.org> 写道:
> >On 2024-01-27 13:15, Andy Yan wrote:
> >> At 2024-01-27 18:36:40, "Heiko Stübner" <heiko@sntech.de> wrote:
> >>> Am Samstag, 27. Januar 2024, 10:20:33 CET schrieb Andy Yan:
> >>>> According to the schematic, this regulator is used both for USB30 and
> >>>> USB20, so give it a more appropriate name.
> >>> 
> >>> I don't have the schematics, so I'll need you to answer this, but what
> >>> is the regulator called _in_ the schematics?
> >> 
> >> There are two regulators called VCC50_USB_HOST1 and VCC50_USB_HOST2,
> >> and they are both controlled by GPIO1_D5
> >> They both for two usb 2.0 hosts,  not usb 30, the schematics make
> >> me a bit confused.
> >
> >In that case, I'd say that renaming the regulator to vcc5v0_usb_host is
> >fine, but there should also be a comment in the board dts file that it's
> >actually two separate regulators.
> 
> How do you feel about this ? Or some other style like:
> vcc5v0_usb_host1: vcc5v0_usb_host2:vcc5v0-usb-host-regulator {

I think we're using such a scheme in some places already, and
yes I really like going this way. So that the phandles follow the
schematic names and we can still grep for things.


Heiko





_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Dragan Simic <dsimic@manjaro.org>, Andy Yan <andyshrk@163.com>
Cc: krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 3/4] arm64: dts: rockchip: rename vcc5v0_usb30_host regulator for Cool Pi CM5 EVB
Date: Wed, 31 Jan 2024 15:24:16 +0100	[thread overview]
Message-ID: <2179538.KUTt5R2Mg1@diego> (raw)
In-Reply-To: <1e98352e.2dd2.18d5f780043.Coremail.andyshrk@163.com>

Am Mittwoch, 31. Januar 2024, 13:21:56 CET schrieb Andy Yan:
> 
> Hi Heiko:
> 
> 在 2024-01-27 21:09:46,"Dragan Simic" <dsimic@manjaro.org> 写道:
> >On 2024-01-27 13:15, Andy Yan wrote:
> >> At 2024-01-27 18:36:40, "Heiko Stübner" <heiko@sntech.de> wrote:
> >>> Am Samstag, 27. Januar 2024, 10:20:33 CET schrieb Andy Yan:
> >>>> According to the schematic, this regulator is used both for USB30 and
> >>>> USB20, so give it a more appropriate name.
> >>> 
> >>> I don't have the schematics, so I'll need you to answer this, but what
> >>> is the regulator called _in_ the schematics?
> >> 
> >> There are two regulators called VCC50_USB_HOST1 and VCC50_USB_HOST2,
> >> and they are both controlled by GPIO1_D5
> >> They both for two usb 2.0 hosts,  not usb 30, the schematics make
> >> me a bit confused.
> >
> >In that case, I'd say that renaming the regulator to vcc5v0_usb_host is
> >fine, but there should also be a comment in the board dts file that it's
> >actually two separate regulators.
> 
> How do you feel about this ? Or some other style like:
> vcc5v0_usb_host1: vcc5v0_usb_host2:vcc5v0-usb-host-regulator {

I think we're using such a scheme in some places already, and
yes I really like going this way. So that the phandles follow the
schematic names and we can still grep for things.


Heiko





  reply	other threads:[~2024-01-31 14:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27  9:20 [PATCH 1/4] arm64: dts: rockchip: aliase sdmmc as mmc1 for Cool Pi 4B Andy Yan
2024-01-27  9:20 ` Andy Yan
2024-01-27  9:20 ` Andy Yan
2024-01-27  9:20 ` [PATCH 2/4] arm64: dts: rockchip: aliase sdmmc as mmc1 for Cool Pi CM5 EVB Andy Yan
2024-01-27  9:20   ` Andy Yan
2024-01-27  9:20   ` Andy Yan
2024-01-27 13:07   ` Dragan Simic
2024-01-27 13:07     ` Dragan Simic
2024-01-27 13:07     ` Dragan Simic
2024-01-27  9:20 ` [PATCH 3/4] arm64: dts: rockchip: rename vcc5v0_usb30_host regulator " Andy Yan
2024-01-27  9:20   ` Andy Yan
2024-01-27  9:20   ` Andy Yan
2024-01-27 10:36   ` Heiko Stübner
2024-01-27 10:36     ` Heiko Stübner
2024-01-27 10:36     ` Heiko Stübner
2024-01-27 12:15     ` Andy Yan
2024-01-27 12:15       ` Andy Yan
2024-01-27 12:15       ` Andy Yan
2024-01-27 13:09       ` Dragan Simic
2024-01-27 13:09         ` Dragan Simic
2024-01-27 13:09         ` Dragan Simic
2024-01-31 12:21         ` Andy Yan
2024-01-31 12:21           ` Andy Yan
2024-01-31 12:21           ` Andy Yan
2024-01-31 14:24           ` Heiko Stübner [this message]
2024-01-31 14:24             ` Heiko Stübner
2024-01-31 14:24             ` Heiko Stübner
2024-01-27  9:20 ` [PATCH 4/4] arm64: dts: rockchip: Fix the num-lanes of pcie3x4 on " Andy Yan
2024-01-27  9:20   ` Andy Yan
2024-01-27  9:20   ` Andy Yan
2024-01-27 13:07 ` [PATCH 1/4] arm64: dts: rockchip: aliase sdmmc as mmc1 for Cool Pi 4B Dragan Simic
2024-01-27 13:07   ` Dragan Simic
2024-01-27 13:07   ` Dragan Simic

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=2179538.KUTt5R2Mg1@diego \
    --to=heiko@sntech.de \
    --cc=andyshrk@163.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --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 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.