All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@kernel.org>
To: Peter Chen <peter.chen@nxp.com>,
	"mathias.nyman@intel.com" <mathias.nyman@intel.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	dl-linux-imx <linux-imx@nxp.com>,
	"pawell@cadence.com" <pawell@cadence.com>,
	"rogerq@ti.com" <rogerq@ti.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	Jun Li <jun.li@nxp.com>
Subject: RE: [PATCH 1/8] usb: cdns3: add runtime PM support
Date: Mon, 31 Aug 2020 14:27:04 +0300	[thread overview]
Message-ID: <87wo1f9htj.fsf@kernel.org> (raw)
In-Reply-To: <AM7PR04MB71572A2B1EDC6D379B1CBDA88B510@AM7PR04MB7157.eurprd04.prod.outlook.com>

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


Hi,

Peter Chen <peter.chen@nxp.com> writes:
>> Peter Chen <peter.chen@nxp.com> writes:
>> > Introduce runtime PM and wakeup interrupt handler for cdns3, the
>> > runtime PM is default off since other cdns3 has not implemented glue
>> > layer support for runtime PM.
>> 
>> it should be left disabled by default even after every glue implements it.
>> Enabling runtime PM is a policy decision better left to userspace, IMO.
>> 
>> > When the controller is in low power mode, the lpm flag will be set.
>> > The interrupt triggered later than lpm flag is set considers as wakeup
>> > interrupt and handled at cdns_drd_irq. Once the wakeup
>> 
>> This sentence doesn't parse very well. Do you want to rephrase it?
>> 
>> > occurs, it first disables interrupt to avoid later interrupt
>> > occurrence since the controller is in low power mode at that time, and
>> > access registers may be invalid at that time. At wakeup handler, it
>> > will call pm_runtime_get to wakeup controller, and at runtime resume
>> > handler, it will enable interrupt again.
>> 
>> Then what? Are you going to, somehow, process pending interrupts? At what
>> point?
>> 
>> > The API platform_suspend is introduced for glue layer to implement
>> > platform specific PM sequence.
>> 
>> I really think that's unnecessary. Why can't we rely on parent->child
>> relationship for this?
>> 
>  
> Hi Felipe,
>
> This is the old version patch; I replied your questions at your reply for new
> version at last Friday, thanks.

yeah sorry, I'm getting caught up on my inbox from oldest to
newest. This slip through the cracks ;-)

-- 
balbi

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

  reply	other threads:[~2020-08-31 11:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 10:32 [PATCH 0/8] usb: cdns3: add runtime PM support Peter Chen
2020-05-22 10:32 ` [PATCH 1/8] " Peter Chen
2020-08-31 10:01   ` Felipe Balbi
2020-08-31 10:59     ` Peter Chen
2020-08-31 11:27       ` Felipe Balbi [this message]
2020-05-22 10:32 ` [PATCH 2/8] usb: cdns3: imx: add glue layer runtime pm implementation Peter Chen
2020-08-31 10:04   ` Felipe Balbi
2020-05-22 10:32 ` [PATCH 3/8] usb: host: xhci-plat: add platform data support Peter Chen
2020-05-22 10:32 ` [PATCH 4/8] usb: host: xhci-plat: add .suspend_quirk for struct xhci_plat_priv Peter Chen
2020-08-31 10:06   ` Felipe Balbi
2020-08-31 11:00     ` Peter Chen
2020-05-22 10:32 ` [PATCH 5/8] usb: host: xhci-plat: delete the unnecessary code Peter Chen
2020-05-22 10:32 ` [PATCH 6/8] usb: host: xhci-plat: add priv flag for skip_phy_initialization Peter Chen
2020-05-22 10:32 ` [PATCH 7/8] usb: cdns3: host: add .suspend_quirk for xhci-plat.c Peter Chen
2020-05-22 10:32 ` [PATCH 8/8] usb: cdns3: host: add xhci_plat_priv's flag skip_phy_initialization Peter Chen

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=87wo1f9htj.fsf@kernel.org \
    --to=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jun.li@nxp.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=pawell@cadence.com \
    --cc=peter.chen@nxp.com \
    --cc=rogerq@ti.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 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.