On Wed, Apr 27, 2016 at 10:44 AM, Dan Murphy wrote:
> Joe
>
> On 04/26/2016 04:42 PM, Joe Hershberger wrote:
>> On Mon, Apr 25, 2016 at 4:32 PM, Joe Hershberger
>> wrote:
>>> On Fri, Apr 15, 2016 at 7:27 AM, Dan Murphy wrote:
Add
Joe
On 04/26/2016 04:42 PM, Joe Hershberger wrote:
> On Mon, Apr 25, 2016 at 4:32 PM, Joe Hershberger
> wrote:
>> On Fri, Apr 15, 2016 at 7:27 AM, Dan Murphy wrote:
>>> Add the ability to read the phy-handle node of the
>>> cpsw slave. Upon reading
On Mon, Apr 25, 2016 at 4:32 PM, Joe Hershberger
wrote:
> On Fri, Apr 15, 2016 at 7:27 AM, Dan Murphy wrote:
>> Add the ability to read the phy-handle node of the
>> cpsw slave. Upon reading this handle the phy-id
>> can be stored based on the reg node
On Fri, Apr 15, 2016 at 7:27 AM, Dan Murphy wrote:
> Add the ability to read the phy-handle node of the
> cpsw slave. Upon reading this handle the phy-id
> can be stored based on the reg node in the DT.
It would be great if the phy could be handled generically.
Unfortunately
On Friday 15 April 2016 05:57 PM, Dan Murphy wrote:
> Add the ability to read the phy-handle node of the
> cpsw slave. Upon reading this handle the phy-id
> can be stored based on the reg node in the DT.
>
> The phy-handle also needs to be stored and passed
> to the phy to access any phy data
Bump?
On 04/15/2016 07:27 AM, Dan Murphy wrote:
> Add the ability to read the phy-handle node of the
> cpsw slave. Upon reading this handle the phy-id
> can be stored based on the reg node in the DT.
>
> The phy-handle also needs to be stored and passed
> to the phy to access any phy data that
Add the ability to read the phy-handle node of the
cpsw slave. Upon reading this handle the phy-id
can be stored based on the reg node in the DT.
The phy-handle also needs to be stored and passed
to the phy to access any phy data that is available.
Signed-off-by: Dan Murphy
---
7 matches
Mail list logo