From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Felipe Balbi <balbi@kernel.org>,
linux-kernel@vger.kernel.org, robh@kernel.org,
p.zabel@pengutronix.de
Cc: gregkh@linuxfoundation.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org, cheol.yong.kim@intel.com,
qi-ming.wu@intel.com, yin1.li@intel.com,
andriy.shevchenko@intel.com
Subject: Re: [PATCH v4 2/2] usb: phy: Add USB3 PHY support for Intel LGM SoC
Date: Sun, 12 Jul 2020 13:50:54 +0800 [thread overview]
Message-ID: <04a2d471-168f-7769-895e-b390c64e95ad@linux.intel.com> (raw)
In-Reply-To: <87blknrjg6.fsf@kernel.org>
Hi,
On 10/7/2020 2:08 pm, Felipe Balbi wrote:
>
> Hi,
>
> "Ramuthevar,Vadivel MuruganX"
> <vadivel.muruganx.ramuthevar@linux.intel.com> writes:
>
>> From: Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
>>
>> Add support for USB PHY on Intel LGM SoC.
>>
>> Signed-off-by: Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
>> ---
>> drivers/usb/phy/Kconfig | 11 ++
>> drivers/usb/phy/Makefile | 1 +
>> drivers/usb/phy/phy-lgm-usb.c | 275 ++++++++++++++++++++++++++++++++++++++++++
>
> new phy drivers should use drivers/phy instead.
Noted, Will move to drivers/phy as per your suggestion, Thanks!
Regards
Vadivel
>
prev parent reply other threads:[~2020-07-12 5:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 3:58 [PATCH v4 0/2]usb : phy: Add USB PHY support on Intel LGM SoC Ramuthevar,Vadivel MuruganX
2020-06-17 3:58 ` [PATCH v4 1/2] dt-bindings: usb: Add USB PHY support for " Ramuthevar,Vadivel MuruganX
2020-07-09 23:07 ` Rob Herring
2020-06-17 3:58 ` [PATCH v4 2/2] usb: phy: Add USB3 " Ramuthevar,Vadivel MuruganX
2020-06-17 9:23 ` Philipp Zabel
2020-07-10 6:08 ` Felipe Balbi
2020-07-10 7:07 ` Greg KH
2020-07-12 5:50 ` Ramuthevar, Vadivel MuruganX [this message]
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=04a2d471-168f-7769-895e-b390c64e95ad@linux.intel.com \
--to=vadivel.muruganx.ramuthevar@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=balbi@kernel.org \
--cc=cheol.yong.kim@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=qi-ming.wu@intel.com \
--cc=robh@kernel.org \
--cc=yin1.li@intel.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).