From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/7] binding: mdio-mux: Add DT binding doc for Broadcom MDIO bus mutiplexer
Date: Tue, 31 May 2016 14:27:57 +0200 [thread overview]
Message-ID: <20160531122757.GD24402@lunn.ch> (raw)
In-Reply-To: <e002ac1b95d8ee4725f7315427f65fbf@mail.gmail.com>
> Yes. I agree. We will logical OR MII_ADDR_C45 into the address from PHY
> drivers. Is there any standard property exist for non-ethernet-phy DRIVERS
> to decide the whether PHY node support C45 or C22?
Why do you even need this in the device tree? If the driver needs to
access a register > 31, it knows it must use C45. If it is less than
32, it can use either C22 or C45.
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Pramod Kumar <pramod.kumar@broadcom.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
"David S. Miller" <davem@davemloft.net>,
devicetree@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/7] binding: mdio-mux: Add DT binding doc for Broadcom MDIO bus mutiplexer
Date: Tue, 31 May 2016 14:27:57 +0200 [thread overview]
Message-ID: <20160531122757.GD24402@lunn.ch> (raw)
In-Reply-To: <e002ac1b95d8ee4725f7315427f65fbf@mail.gmail.com>
> Yes. I agree. We will logical OR MII_ADDR_C45 into the address from PHY
> drivers. Is there any standard property exist for non-ethernet-phy DRIVERS
> to decide the whether PHY node support C45 or C22?
Why do you even need this in the device tree? If the driver needs to
access a register > 31, it knows it must use C45. If it is less than
32, it can use either C22 or C45.
Andrew
next prev parent reply other threads:[~2016-05-31 12:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 7:10 [PATCH 0/7] Add MDIO bus multiplexer support for iProc SoCs Pramod Kumar
2016-05-30 7:10 ` Pramod Kumar
2016-05-30 7:10 ` [PATCH 1/7] mdio:mux: Enhanced MDIO mux framework for integrated multiplexers Pramod Kumar
2016-05-30 7:10 ` Pramod Kumar
2016-05-30 7:10 ` [PATCH 2/7] DT: phy.txt: Add mdio-integrated-mux property Pramod Kumar
2016-05-30 7:10 ` Pramod Kumar
2016-05-30 7:10 ` [PATCH 3/7] binding: mdio-mux: Add DT binding doc for Broadcom MDIO bus mutiplexer Pramod Kumar
2016-05-30 7:10 ` Pramod Kumar
2016-05-30 15:24 ` Andrew Lunn
2016-05-30 15:24 ` Andrew Lunn
2016-05-31 12:04 ` Pramod Kumar
2016-05-31 12:04 ` Pramod Kumar
2016-05-31 12:27 ` Andrew Lunn [this message]
2016-05-31 12:27 ` Andrew Lunn
2016-05-30 7:10 ` [PATCH 4/7] DT:mdio-mux: Add mdio multiplexer driver node Pramod Kumar
2016-05-30 7:10 ` Pramod Kumar
2016-05-30 7:10 ` [PATCH 5/7] net:mdio-mux: Add MDIO mux driver for iProc SoCs Pramod Kumar
2016-05-30 7:10 ` Pramod Kumar
2016-05-30 13:34 ` Andrew Lunn
2016-05-30 13:34 ` Andrew Lunn
2016-05-30 13:34 ` Andrew Lunn
2016-05-30 14:39 ` Pramod Kumar
2016-05-30 14:39 ` Pramod Kumar
2016-05-30 7:10 ` [PATCH 6/7] Binding:PHY: Binding doc for NS2 PCIe PHYs Pramod Kumar
2016-05-30 7:10 ` Pramod Kumar
2016-05-30 7:10 ` [PATCH 7/7] phy: Add Northstar2 PCI Phy support Pramod Kumar
2016-05-30 7:10 ` Pramod Kumar
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=20160531122757.GD24402@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.