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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <555E4E1E.2030909@broadcom.com>
Date:	Thu, 21 May 2015 14:29:02 -0700
From:	Ray Jui <rjui@...adcom.com>
To:	Kishon Vijay Abraham I <kishon@...com>
CC:	<linux-kernel@...r.kernel.org>,
	"JD (Jiandong) Zheng" <jdzheng@...adcom.com>,
	Arun Parameswaran <arunp@...adcom.com>,
	<bcm-kernel-feedback-list@...adcom.com>
Subject: Re: [PATCH 1/5] phy: iproc-mdio: Define DT binding

Hi Kishon,

On 5/21/2015 6:07 AM, Kishon Vijay Abraham I wrote:
> Hi,
> 
> On Wednesday 20 May 2015 06:53 AM, Ray Jui wrote:
>> Define device tree bindings for iProc MDC/MDIO interface
> 
> 
> Fix $subject to something like 'dt_bindings: Add iProc MDC/MDIO PHY
> bindings'
> 
Will do.

>>
>> Signed-off-by: Ray Jui <rjui@...adcom.com>
>> Reviewed-by: Arun Parameswaran <aparames@...adcom.com>
>> Reviewed-by: JD (Jiandong) Zheng <jdzheng@...adcom.com>
>> Reviewed-by: Scott Branden <sbranden@...adcom.com>
>> ---
>>   .../devicetree/bindings/phy/brcm,iproc-mdio.txt    |   15
>> +++++++++++++++
>>   1 file changed, 15 insertions(+)
>>   create mode 100644
>> Documentation/devicetree/bindings/phy/brcm,iproc-mdio.txt
>>
>> diff --git a/Documentation/devicetree/bindings/phy/brcm,iproc-mdio.txt
>> b/Documentation/devicetree/bindings/phy/brcm,iproc-mdio.txt
>> new file mode 100644
>> index 0000000..dce7644
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/phy/brcm,iproc-mdio.txt
>> @@ -0,0 +1,15 @@
>> +Broadcom iProc MDC/MDIO interface
>> +
>> +The iProc MDC/MDIO interface is found on various iProc based SoCs and
>> used to
>> +communicate with various types of Serdes/PHYs including Ethernet,
>> PCIe, USB,
>> +and etc.
> 
> This sounds like it isn't a PHY exactly but a bus to which other PHYs
> are connected?

Yes it's an internal MDIO interface connected to various types of
internal Serdes or PHYs.

> 
> Thanks
> Kishon
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ