public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ray Jui <rjui@broadcom.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: <linux-kernel@vger.kernel.org>,
	"JD (Jiandong) Zheng" <jdzheng@broadcom.com>,
	Arun Parameswaran <arunp@broadcom.com>,
	<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH 1/5] phy: iproc-mdio: Define DT binding
Date: Thu, 21 May 2015 14:29:02 -0700	[thread overview]
Message-ID: <555E4E1E.2030909@broadcom.com> (raw)
In-Reply-To: <555DD8AD.4040405@ti.com>

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@broadcom.com>
>> Reviewed-by: Arun Parameswaran <aparames@broadcom.com>
>> Reviewed-by: JD (Jiandong) Zheng <jdzheng@broadcom.com>
>> Reviewed-by: Scott Branden <sbranden@broadcom.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

  reply	other threads:[~2015-05-21 21:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  1:23 [PATCH 0/5] Add Cygnus PCIe PHY support Ray Jui
2015-05-20  1:23 ` [PATCH 1/5] phy: iproc-mdio: Define DT binding Ray Jui
2015-05-21 13:07   ` Kishon Vijay Abraham I
2015-05-21 21:29     ` Ray Jui [this message]
2015-05-20  1:23 ` [PATCH 2/5] phy: iproc-mdio: Initial iProc MDC/MDIO support Ray Jui
2015-05-21  7:41   ` Paul Bolle
2015-05-21 23:52     ` Ray Jui
2015-05-22  8:39       ` Paul Bolle
2015-05-21 13:12   ` Kishon Vijay Abraham I
2015-05-21 21:35     ` Ray Jui
2015-05-21 21:51       ` Florian Fainelli
2015-05-21 22:02         ` Ray Jui
2015-05-20  1:23 ` [PATCH 3/5] phy: cygnus: pcie: Define DT binding Ray Jui
2015-05-21 13:14   ` Kishon Vijay Abraham I
2015-05-21 21:59     ` Ray Jui
2015-05-21 23:36       ` Ray Jui
2015-05-20  1:23 ` [PATCH 4/5] phy: cygnus: pcie: Add Cygnus PCIe PHY support Ray Jui
2015-05-21  7:52   ` Paul Bolle
2015-05-21 23:53     ` Ray Jui
2015-05-22  8:47       ` Paul Bolle
2015-05-21 13:19   ` Kishon Vijay Abraham I
2015-05-20  1:23 ` [PATCH 5/5] ARM: dts: enable PCIe PHY support for Cygnus Ray Jui

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=555E4E1E.2030909@broadcom.com \
    --to=rjui@broadcom.com \
    --cc=arunp@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=jdzheng@broadcom.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.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