From: David Daney <david.daney@cavium.com>
To: David Miller <davem@davemloft.net>
Cc: ddaney.cavm@gmail.com, grant.likely@secretlab.ca,
rob.herring@calxeda.com, devicetree-discuss@lists.ozlabs.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org, afleming@gmail.com,
galak@kernel.crashing.org
Subject: Re: [PATCH v4 3/3] netdev/of/phy: Add MDIO bus multiplexer driven by GPIO lines.
Date: Wed, 18 Apr 2012 09:24:56 -0700 [thread overview]
Message-ID: <4F8EEAD8.8050205@cavium.com> (raw)
In-Reply-To: <20120417.225308.1588669089502246200.davem@davemloft.net>
On 04/17/2012 07:53 PM, David Miller wrote:
> From: David Daney<ddaney.cavm@gmail.com>
> Date: Tue, 17 Apr 2012 10:32:46 -0700
>
>> From: David Daney<david.daney@cavium.com>
>>
>> The GPIO pins select which sub bus is connected to the master.
>>
>> Initially tested with an sn74cbtlv3253 switch device wired into the
>> MDIO bus.
>>
>> Signed-off-by: David Daney<david.daney@cavium.com>
>
> Are you sure the Kconfig dependencies are sufficient? This code seems
> to depend upon OF, and in particular the OF_MDIO stuff.
>
You are correct. Should I:
A) Create a patch to fix the dependencies it on top of the previous set?
B) Regenerate the entire set with said patch rolled in?
Thanks,
David Daney
next prev parent reply other threads:[~2012-04-18 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 17:32 [PATCH v4 0/3] netdev/of/phy: MDIO bus multiplexer support David Daney
2012-04-17 17:32 ` [PATCH v4 1/3] netdev/of/phy: New function: of_mdio_find_bus() David Daney
2012-04-17 17:32 ` [PATCH v4 2/3] netdev/of/phy: Add MDIO bus multiplexer support David Daney
2012-04-17 17:32 ` [PATCH v4 3/3] netdev/of/phy: Add MDIO bus multiplexer driven by GPIO lines David Daney
2012-04-18 2:53 ` David Miller
2012-04-18 16:24 ` David Daney [this message]
2012-04-18 17:45 ` David Miller
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=4F8EEAD8.8050205@cavium.com \
--to=david.daney@cavium.com \
--cc=afleming@gmail.com \
--cc=davem@davemloft.net \
--cc=ddaney.cavm@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=galak@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.org \
--cc=rob.herring@calxeda.com \
/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