From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/7] usb: dwc3: st: Inform the reset framework that our reset line may be shared
Date: Thu, 16 Jun 2016 11:03:30 +0200 [thread overview]
Message-ID: <1466067810.3343.13.camel@pengutronix.de> (raw)
In-Reply-To: <20160606155655.10860-8-lee.jones@linaro.org>
Am Montag, den 06.06.2016, 16:56 +0100 schrieb Lee Jones:
> On the STiH410 B2120 development board the MiPHY28lp shares its reset
> line with the Synopsys DWC3 SuperSpeed (SS) USB 3.0 Dual-Role-Device
> (DRD). New functionality in the reset subsystems forces consumers to
> be explicit when requesting shared/exclusive reset lines.
>
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
> ---
> drivers/usb/dwc3/dwc3-st.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/dwc3/dwc3-st.c b/drivers/usb/dwc3/dwc3-st.c
> index 5c0adb9..e77bacb 100644
> --- a/drivers/usb/dwc3/dwc3-st.c
> +++ b/drivers/usb/dwc3/dwc3-st.c
> @@ -227,7 +227,8 @@ static int st_dwc3_probe(struct platform_device *pdev)
> dev_vdbg(&pdev->dev, "glue-logic addr 0x%p, syscfg-reg offset 0x%x\n",
> dwc3_data->glue_base, dwc3_data->syscfg_reg_off);
>
> - dwc3_data->rstc_pwrdn = devm_reset_control_get(dev, "powerdown");
> + dwc3_data->rstc_pwrdn =
> + devm_reset_control_get_exclusive(dev, "powerdown");
This hunk is not critical. If you split it into a separate patch, this
one doesn't depend on patch 2. The same applies to patch 8.
That way I could take patches 1-5 through reset/next and you wouldn't
have to wait for them to be merged into arm-soc.
regards
Philipp
next prev parent reply other threads:[~2016-06-16 9:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 15:56 [PATCH 0/7] reset: Consumers to explicitly request 'exclusive' or 'shared' lines Lee Jones
2016-06-06 15:56 ` [PATCH 1/7] reset: Reorder inline reset_control_get*() wrappers Lee Jones
2016-06-20 12:07 ` Philipp Zabel
2016-06-06 15:56 ` [PATCH 2/7] reset: Ensure drivers are explicit when requesting reset lines Lee Jones
2016-06-06 15:56 ` [PATCH 3/7] reset: Supply *_shared variant calls when using of_* API Lee Jones
2016-06-06 15:56 ` [PATCH 4/7] reset: Supply *_shared variant calls when using *_optional APIs Lee Jones
2016-06-28 8:56 ` Lee Jones
2016-06-29 7:48 ` Philipp Zabel
2016-06-29 8:06 ` Lee Jones
2016-06-29 9:23 ` Philipp Zabel
2016-06-29 9:37 ` Lee Jones
2016-06-29 21:57 ` Philipp Zabel
2016-06-06 15:56 ` [PATCH 5/7] reset: TRIVIAL: Add line break at same place for similar APIs Lee Jones
2016-06-06 15:56 ` [PATCH 6/7] phy: miphy28lp: Inform the reset framework that our reset line may be shared Lee Jones
2016-06-07 8:37 ` [STLinux Kernel] " Peter Griffin
2016-06-07 8:59 ` Kishon Vijay Abraham I
2016-06-28 7:55 ` Lee Jones
2016-06-06 15:56 ` [PATCH 7/7] usb: dwc3: st: " Lee Jones
2016-06-06 17:08 ` [PATCH 8/10] phy: phy-stih407-usb: " Lee Jones
2016-06-06 17:08 ` [PATCH 9/10] usb: host: ehci-st: " Lee Jones
2016-06-06 17:44 ` Alan Stern
2016-06-28 7:58 ` Lee Jones
2016-06-28 8:01 ` Lee Jones
2016-06-07 8:36 ` [STLinux Kernel] " Peter Griffin
2016-06-06 17:08 ` [PATCH 10/10] usb: host: ohci-st: " Lee Jones
2016-06-07 8:36 ` [STLinux Kernel] [PATCH 8/10] phy: phy-stih407-usb: " Peter Griffin
2016-06-07 9:00 ` Kishon Vijay Abraham I
2016-06-07 8:36 ` [STLinux Kernel] [PATCH 7/7] usb: dwc3: st: " Peter Griffin
2016-06-16 9:03 ` Philipp Zabel [this message]
2016-06-28 9:27 ` [PATCH 1/1] " Lee Jones
2016-06-29 6:33 ` Felipe Balbi
2016-06-07 8:42 ` [STLinux Kernel] [PATCH 0/7] reset: Consumers to explicitly request 'exclusive' or 'shared' lines Peter Griffin
2016-06-07 9:15 ` Lee Jones
2016-06-07 9:24 ` Lee Jones
2016-06-16 9:03 ` Philipp Zabel
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=1466067810.3343.13.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--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).