From: Felipe Balbi <balbi@ti.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v11 0/8] PHY framework
Date: Tue, 27 Aug 2013 19:20:59 +0000 [thread overview]
Message-ID: <20130827192059.GZ3005@radagast> (raw)
In-Reply-To: <521B0E79.6060506@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]
Hi,
On Mon, Aug 26, 2013 at 01:44:49PM +0530, Kishon Vijay Abraham I wrote:
> On Wednesday 21 August 2013 11:16 AM, 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
>
> Looks like there are not further comments on this series. Can you take this in
> your misc tree?
Do you want me to queue these for you ? There are quite a few users for
this framework already and I know of at least 2 others which will show
up for v3.13.
Let me know.
cheers
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-27 19:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 5:58 [PATCH v11 0/8] PHY framework Kishon Vijay Abraham I
2013-08-21 5:58 ` [PATCH v11 1/8] drivers: phy: add generic " Kishon Vijay Abraham I
2013-08-21 5:58 ` [PATCH v11 2/8] usb: phy: omap-usb2: use the new " Kishon Vijay Abraham I
2013-09-26 18:51 ` Greg KH
2013-09-27 6:47 ` Kishon Vijay Abraham I
2013-08-21 5:58 ` [PATCH v11 3/8] usb: phy: twl4030: " Kishon Vijay Abraham I
2013-08-21 5:58 ` [PATCH v11 4/8] arm: omap3: twl: add phy consumer data in twl4030_usb_data Kishon Vijay Abraham I
2013-08-21 5:58 ` [PATCH v11 5/8] ARM: dts: omap: update usb_otg_hs data Kishon Vijay Abraham I
2013-08-21 5:58 ` [PATCH v11 6/8] usb: musb: omap2430: use the new generic PHY framework Kishon Vijay Abraham I
2013-08-21 5:58 ` [PATCH v11 7/8] usb: phy: omap-usb2: remove *set_suspend* callback from omap-usb2 Kishon Vijay Abraham I
2013-08-21 5:58 ` [PATCH v11 8/8] usb: phy: twl4030-usb: remove *set_suspend* and *phy_init* ops Kishon Vijay Abraham I
2013-08-26 8:26 ` [PATCH v11 0/8] PHY framework Kishon Vijay Abraham I
2013-08-27 19:20 ` Felipe Balbi [this message]
2013-08-28 10:55 ` Kishon Vijay Abraham I
2013-09-03 15:37 ` Kishon Vijay Abraham I
2013-09-03 15:50 ` Greg KH
2013-09-04 8:58 ` Kishon Vijay Abraham I
2013-09-17 15:41 ` Felipe Balbi
2013-09-20 5:46 ` Kishon Vijay Abraham I
2013-09-20 6:07 ` Greg KH
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=20130827192059.GZ3005@radagast \
--to=balbi@ti.com \
--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).