From: Greg KH <gregkh@linuxfoundation.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: swarren@wwwdotorg.org, bcousson@baylibre.com, tony@atomide.com,
balbi@ti.com, s.nawrocki@samsung.com, rob.herring@calxeda.com,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, rob@landley.net,
linux@arm.linux.org.uk, jkosina@suse.cz, m.chehab@samsung.com,
cesarb@cesarb.net, joe@perches.com, davem@davemloft.net,
davidb@codeaurora.org, sameo@linux.intel.com,
peter.ujfalusi@ti.com, t-kristo@ti.com,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org,
akpm@linux-foundation.org, balajitk@ti.com,
george.cherian@ti.com, nsekhar@ti.com, rogerq@ti.com
Subject: Re: [PATCH v12 0/7] PHY framework
Date: Fri, 27 Sep 2013 17:37:42 -0700 [thread overview]
Message-ID: <20130928003742.GA3659@kroah.com> (raw)
In-Reply-To: <1380263012-9687-1-git-send-email-kishon@ti.com>
On Fri, Sep 27, 2013 at 11:53:24AM +0530, Kishon Vijay Abraham I wrote:
> Added a generic PHY framework that provides a set of APIs for the PHY drivers
> to create/destroy a PHY and APIs for the PHY users to obtain a reference to
> the PHY with or without using phandle.
>
> This framework will be of use only to devices that uses external PHY (PHY
> functionality is not embedded within the controller).
>
> The intention of creating this framework is to bring the phy drivers spread
> all over the Linux kernel to drivers/phy to increase code re-use and to
> increase code maintainability.
>
> Comments to make PHY as bus wasn't done because PHY devices can be part of
> other bus and making a same device attached to multiple bus leads to bad
> design.
>
> If the PHY driver has to send notification on connect/disconnect, the PHY
> driver should make use of the extcon framework. Using this susbsystem
> to use extcon framwork will have to be analysed.
>
> You can find this patch series @
> git://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git testing
>
> I'll create a new branch *next* once this patch series is finalized. All the
> PHY driver development that depends on PHY framework can be based on this
> branch.
>
> Did USB enumeration testing in panda and beagle after applying [1] (needed for
> non-dt)
All now applied to my usb-next branch. Thanks for redoing this many
times and sticking with it.
greg k-h
next prev parent reply other threads:[~2013-09-28 0:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 6:23 [PATCH v12 0/7] PHY framework Kishon Vijay Abraham I
2013-09-27 6:23 ` [PATCH v12 2/7] usb: phy: omap-usb2: use the new generic " Kishon Vijay Abraham I
2013-09-27 6:23 ` [PATCH v12 4/7] arm: omap3: twl: add phy consumer data in twl4030_usb_data Kishon Vijay Abraham I
[not found] ` <1380263012-9687-1-git-send-email-kishon-l0cyMroinI0@public.gmane.org>
2013-09-27 6:23 ` [PATCH v12 1/7] drivers: phy: add generic PHY framework Kishon Vijay Abraham I
2013-09-27 6:23 ` [PATCH v12 3/7] usb: phy: twl4030: use the new " Kishon Vijay Abraham I
2013-09-27 6:23 ` [PATCH v12 5/7] ARM: dts: omap: update usb_otg_hs data Kishon Vijay Abraham I
2013-09-27 6:23 ` [PATCH v12 6/7] usb: musb: omap2430: use the new generic PHY framework Kishon Vijay Abraham I
2013-09-27 6:23 ` [PATCH v12 7/7] usb: phy: twl4030-usb: remove *set_suspend* and *phy_init* ops Kishon Vijay Abraham I
2013-09-28 0:37 ` Greg KH [this message]
2013-09-28 9:42 ` [PATCH v12 0/7] PHY framework Kishon Vijay Abraham I
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=20130928003742.GA3659@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=balajitk@ti.com \
--cc=balbi@ti.com \
--cc=bcousson@baylibre.com \
--cc=cesarb@cesarb.net \
--cc=davem@davemloft.net \
--cc=davidb@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=george.cherian@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jkosina@suse.cz \
--cc=joe@perches.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.chehab@samsung.com \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=pawel.moll@arm.com \
--cc=peter.ujfalusi@ti.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rogerq@ti.com \
--cc=s.nawrocki@samsung.com \
--cc=sameo@linux.intel.com \
--cc=swarren@wwwdotorg.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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).