devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <mka@chromium.org>
To: Javier Carrasco <javier.carrasco@wolfvision.net>
Cc: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 6/7] ASoC: dt-bindings: xmos,xvf3500: add XMOS XVF3500 voice processor
Date: Tue, 6 Feb 2024 15:22:22 +0000	[thread overview]
Message-ID: <ZcJOrvmbukDubcuM@google.com> (raw)
In-Reply-To: <7b472cb2-6658-446a-ae47-411d08798cca@wolfvision.net>

On Tue, Feb 06, 2024 at 04:05:15PM +0100, Javier Carrasco wrote:
> On 06.02.24 15:32, Mark Brown wrote:
> > On Tue, Feb 06, 2024 at 02:59:34PM +0100, Javier Carrasco wrote:
> > 
> >> The XMOS XVF3500 VocalFusion Voice Processor[1] is a low-latency, 32-bit
> >> multicore controller for voice processing.
> > 
> > Acked-by: Mark Brown <broonie@kernel.org>
> > 
> > though...
> > 
> >> +  vdd-supply:
> >> +    description:
> >> +      Regulator for the 1V0 supply.
> >> +
> >> +  vdd2-supply:
> >> +    description:
> >> +      Regulator for the 3V3 supply.
> > 
> > ...it's a bit weird that the supplies are named like this, usually
> > there'd be some sort of meaningful name (even if it's just VDD_1V0 and
> > VDD_3V3 or something).  Are you sure these are the actual names?
> 
> The names in the datasheet are vdd for the 1V0 supply and vddio for the
> 3V3 supply. I named the latter vdd2 instead because this device does not
> have its own driver and instead it uses the onboard_usb_hub generic
> driver, where the supplies are named vdd and vdd2.
> 
> Those are the names used for devm_regulator_bulk_get(). Is that not the
> right way to match them?

If desired the driver could be extended to support device specific regulator
names through struct onboard_hub/dev_pdata.

  reply	other threads:[~2024-02-06 15:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 13:59 [PATCH v3 0/7] usb: misc: onboard_hub: add support for XMOS XVF3500 Javier Carrasco
2024-02-06 13:59 ` [PATCH v3 1/7] usb: misc: onboard_hub: rename to onboard_dev Javier Carrasco
2024-02-06 17:55   ` Matthias Kaehlcke
2024-02-13 10:36     ` Javier Carrasco
2024-02-21 18:22       ` Matthias Kaehlcke
2024-02-06 13:59 ` [PATCH v3 2/7] usb: misc: onboard_dev: add support for non-hub devices Javier Carrasco
2024-02-06 18:40   ` Matthias Kaehlcke
2024-02-13 10:00     ` Javier Carrasco
2024-02-21 18:33       ` Matthias Kaehlcke
2024-02-06 13:59 ` [PATCH v3 3/7] drm: ci: arm64.config: update ONBOARD_USB_HUB to ONBOARD_USB_DEV Javier Carrasco
2024-02-06 13:59 ` [PATCH v3 4/7] arm64: defconfig: " Javier Carrasco
2024-02-06 13:59 ` [PATCH v3 5/7] ARM: multi_v7_defconfig: update ONBOARD_USB_HUB name Javier Carrasco
2024-02-06 13:59 ` [PATCH v3 6/7] ASoC: dt-bindings: xmos,xvf3500: add XMOS XVF3500 voice processor Javier Carrasco
2024-02-06 14:32   ` Mark Brown
2024-02-06 15:05     ` Javier Carrasco
2024-02-06 15:22       ` Matthias Kaehlcke [this message]
2024-02-06 15:35         ` Javier Carrasco
2024-02-06 16:22           ` Mark Brown
2024-02-06 15:35       ` Mark Brown
2024-02-06 15:38         ` Javier Carrasco
2024-02-06 15:49         ` Matthias Kaehlcke
2024-02-06 16:35           ` Mark Brown
2024-02-06 13:59 ` [PATCH v3 7/7] usb: misc: onboard_hub: add support for XMOS XVF3500 Javier Carrasco

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=ZcJOrvmbukDubcuM@google.com \
    --to=mka@chromium.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=javier.carrasco@wolfvision.net \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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 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).