[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120926170459.GA30454@kroah.com>
Date: Wed, 26 Sep 2012 10:04:59 -0700
From: Greg KH <gregkh@...uxfoundation.org>
To: Kishon Vijay Abraham I <kishon@...com>
Cc: akpm@...ux-foundation.org, joe@...ches.com, davem@...emloft.net,
santosh.shilimkar@...com, grant.likely@...retlab.ca, balbi@...com,
arnd@...db.de, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
robherring2@...il.com, richard.zhao@...escale.com,
B29397@...escale.com, alexander.shishkin@...ux.intel.com,
mkl@...gutronix.de, marex@...x.de, p.paneri@...sung.com,
devicetree-discuss@...ts.ozlabs.org,
broonie@...nsource.wolfsonmicro.com
Subject: Re: [PATCH] drivers: phy: add generic PHY framework
On Wed, Sep 26, 2012 at 08:31:15PM +0530, Kishon Vijay Abraham I wrote:
> The PHY framework provides a set of API's for the PHY drivers to
> create/destroy a PHY and API's for the PHY users to obtain a reference to the
> PHY with or without using phandle. To obtain a reference to the PHY without
> using phandle, the platform specfic intialization code (say from board file)
> should have already called phy_bind with the binding information. The binding
> information consists of phy's device name, phy user device name and an index.
> The index is used when the same phy user binds to mulitple phys.
>
> PHY drivers should create the PHY by passing phy_descriptor that has
> describes the PHY (label, type etc..) and ops like init, exit, suspend, resume,
> poweron, shutdown.
Do you have an example driver that uses this new framework?
How does it look in sysfs? You need to add Documentation/ABI/ entries
for the sysfs files you created as well.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists