linux-kernel - Re: [PATCH v3 0/6] Generic PHY Framework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <51712208.5090403@ti.com>
Date:	Fri, 19 Apr 2013 16:22:56 +0530
From:	Sekhar Nori <nsekhar@...com>
To:	Kishon Vijay Abraham I <kishon@...com>
CC:	<balbi@...com>, <gregkh@...uxfoundation.org>, <arnd@...db.de>,
	<akpm@...ux-foundation.org>, <rob@...dley.net>,
	<broonie@...nsource.wolfsonmicro.com>, <linux@....linux.org.uk>,
	<b-cousson@...com>, <linux-doc@...r.kernel.org>,
	<tony@...mide.com>, <devicetree-discuss@...ts.ozlabs.org>,
	<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<rob.herring@...xeda.com>, <grant.likely@...retlab.ca>,
	<eballetbo@...il.com>, <santosh.shilimkar@...com>,
	<linux-arm-kernel@...ts.infradead.org>, <swarren@...dia.com>,
	<javier@...hile0.org>, <linux-omap@...r.kernel.org>,
	<davem@...emloft.net>, <cesarb@...arb.net>, <mchehab@...hat.com>
Subject: Re: [PATCH v3 0/6] Generic PHY Framework

Hi Kishon,

On 3/20/2013 2:41 PM, 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. 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.
> 
> This framework will be of use only to devices that uses external PHY (PHY
> functionality is not embedded within the controller).

>From a top level what you are doing looks closely related to External
connector (extcon).

I understand a connector is not the same as a phy, but it will still be
useful to know why extcon framework (or some extension of it) will not
suffice your needs.

You can probably note it in the cover-letter so folks like me get their
answer.

Thanks,
Sekhar
--
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/