From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] usb: core: add power sequence for USB devices
Date: Sat, 5 Mar 2016 15:10:11 +0100 [thread overview]
Message-ID: <20160305141011.GA28343@lunn.ch> (raw)
In-Reply-To: <20160305083347.GA28858@shlinux2.ap.freescale.net>
> So, would you like to accept the generic solution like below:
>
> - Create a generic power sequence driver, and it will be probed
> according to compatible string at device tree. At its probe,
> we can create a power sequence structure, and let this structure
> as the private data for this power sequence device.
I'm not sure a separate driver is required. Why not consider it more
like pinctrl properties? They are listed in the devices node. Have the
bus enumerate code first walk all children and run their on sequence.
Bus shutdown would again walk the children and run the off sequence.
Andrew
next prev parent reply other threads:[~2016-03-05 14:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 10:01 [PATCH 0/3] Add power sequence for hard-wired USB devices Peter Chen
2016-03-03 10:01 ` [PATCH 1/3] usb: core: add power sequence for " Peter Chen
2016-03-03 18:31 ` Alan Stern
2016-03-04 2:07 ` Peter Chen
2016-03-03 20:54 ` Rob Herring
2016-03-04 2:02 ` Peter Chen
2016-03-04 2:23 ` Andrew Lunn
2016-03-04 2:37 ` Peter Chen
2016-03-05 4:28 ` Rob Herring
2016-03-05 8:33 ` Peter Chen
2016-03-05 14:10 ` Andrew Lunn [this message]
2016-03-14 10:42 ` Peter Chen
2016-04-05 9:35 ` Peter Chen
2016-03-03 10:01 ` [PATCH 2/3] usb: chipidea: host: let the hcd know's parent device node Peter Chen
2016-03-03 14:42 ` Andrew Lunn
2016-03-04 1:53 ` Peter Chen
2016-03-04 2:17 ` Andrew Lunn
2016-03-04 2:32 ` Peter Chen
2016-03-03 10:01 ` [PATCH 3/3] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Peter Chen
2016-03-03 22:30 ` Maciej S. Szmigiero
2016-03-04 2:04 ` 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=20160305141011.GA28343@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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).