public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Pavel Machek <pavel@denx.de>,
	"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH 5.10.y-cip 02/13] regulator: core: Add helper for allow HW access to enable/disable regulator
Date: Wed, 31 Jul 2024 12:06:04 +0200	[thread overview]
Message-ID: <ZqoMjD5bskPB3Qzq@duo.ucw.cz> (raw)
In-Reply-To: <TY3PR01MB11346EB79E7AB9D5CECF88C4086B02@TY3PR01MB11346.jpnprd01.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

Hi!

> > > +++ b/drivers/regulator/core.c
> > > @@ -3244,6 +3244,34 @@ int regulator_list_hardware_vsel(struct
> > > regulator *regulator,  }
> > > EXPORT_SYMBOL_GPL(regulator_list_hardware_vsel);
> > >
> > > +/**
> > > + * regulator_hardware_enable - access the HW for enable/disable
> > > +regulator
> > > + * @regulator: regulator source
> > > + * @enable: true for enable, false for disable
> > > + *
> > > + * Request that the regulator be enabled/disabled with the regulator
> > > +output at
> > > + * the predefined voltage or current value.
> > 
> > "Unlinke other functions, this can be called ...".
> > 
> > And fill in the blanks. "from interrupt context"? "with interrupts disabled"? I'm not sure what real
> > limits are. Probably can't do that from NMI?
> 
> From interrupt context provided the callback function does not uses any sleeping calls.

So the contexts allowed differ based on what low-level driver is used?
That's quite unfortunate...

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2024-07-31 10:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 15:34 [PATCH 5.10.y-cip 00/13] RZ/G2L enhancements Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 01/13] reset: rzg2l-usbphy-ctrl: Move reset controller registration Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 02/13] regulator: core: Add helper for allow HW access to enable/disable regulator Biju Das
2024-07-30 12:28   ` Pavel Machek
2024-07-30 12:32     ` Biju Das
2024-07-31 10:06       ` Pavel Machek [this message]
2024-07-31 13:08         ` Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 03/13] dt-bindings: reset: renesas,rzg2l-usbphy-ctrl: Document USB VBUS regulator Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 04/13] reset: renesas: Add USB VBUS regulator device as child Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 05/13] regulator: Add Renesas RZ/G2L USB VBUS regulator driver Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 06/13] regulator: renesas-usb-vbus-regulator: Update the default Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 07/13] regulator: Further restrict RZG2L USB VBCTRL regulator dependencies Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 08/13] phy: renesas: phy-rcar-gen3-usb2: Control VBUS for RZ/G2L SoCs Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 09/13] arm64: dts: renesas: rz-smarc: Replace fixed regulator for USB VBUS Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 10/13] dmaengine: sh: rz-dmac: Fix lockdep assert warning Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 11/13] dt-bindings: watchdog: dlg,da9062-watchdog: Drop blank space Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 12/13] rtc: isl1208: Add a delay for clearing alarm Biju Das
2024-07-30 12:30   ` Pavel Machek
2024-07-30 12:34     ` Biju Das
2024-07-29 15:34 ` [PATCH 5.10.y-cip 13/13] rtc: isl1208: Update correct procedure " Biju Das
2024-07-30 12:25 ` [PATCH 5.10.y-cip 00/13] RZ/G2L enhancements Pavel Machek
2024-07-31 10:07 ` Pavel Machek

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=ZqoMjD5bskPB3Qzq@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.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