From: Greg KH <gregkh@linuxfoundation.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: peter.chen@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
luca.ceresoli@bootlin.com, jun.li@nxp.com,
linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] usb: chipidea: ci_hdrc_imx: add wakeup clock and keep it always on
Date: Thu, 14 Dec 2023 13:01:08 +0100 [thread overview]
Message-ID: <2023121447-consent-decent-7c69@gregkh> (raw)
In-Reply-To: <20231214112622.2412321-1-xu.yang_2@nxp.com>
On Thu, Dec 14, 2023 at 07:26:20PM +0800, Xu Yang wrote:
> Some platform using ChipIdea IP may keep 32KHz wakeup clock always
> on without usb driver intervention. And some may need driver to handle
> this clock. This patch will get wakeup clock and keep it always on to
> make controller work correctlly.
>
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> ---
> drivers/usb/chipidea/ci_hdrc_imx.c | 22 +++++++++++++++++++++-
> 1 file changed, 21 insertions(+), 1 deletion(-)
>
Why do I have 2 different copies of this series? Please fix up and send
a v2 and describe what changed...
thanks,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-14 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 11:26 [PATCH 1/3] usb: chipidea: ci_hdrc_imx: add wakeup clock and keep it always on Xu Yang
2023-12-14 11:26 ` [PATCH 2/3] usb: chipidea: wait controller resume finished for wakeup irq Xu Yang
2023-12-14 11:26 ` [PATCH 3/3] usb: phy: mxs: remove CONFIG_USB_OTG condition for mxs_phy_is_otg_host() Xu Yang
2023-12-14 11:25 ` Fabio Estevam
2023-12-14 12:35 ` [EXT] " Xu Yang
2023-12-14 12:01 ` Greg KH [this message]
2023-12-14 12:33 ` [EXT] Re: [PATCH 1/3] usb: chipidea: ci_hdrc_imx: add wakeup clock and keep it always on Xu Yang
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=2023121447-consent-decent-7c69@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=festevam@gmail.com \
--cc=jun.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=peter.chen@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=xu.yang_2@nxp.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;
as well as URLs for NNTP newsgroup(s).