From: Jeff Garzik <jgarzik@pobox.com>
To: Scott Wood <scottwood@freescale.com>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/7] Generic bitbanged MDIO library
Date: Fri, 31 Aug 2007 09:23:04 -0400 [thread overview]
Message-ID: <46D81638.6050509@pobox.com> (raw)
In-Reply-To: <20070817175357.GA9218@ld0162-tx32.am.freescale.net>
Scott Wood wrote:
> Previously, bitbanged MDIO was only supported in individual
> hardware-specific drivers. This code factors out the higher level
> protocol implementation, reducing the hardware-specific portion to
> functions setting direction, data, and clock.
>
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
> drivers/net/phy/Kconfig | 9 ++
> drivers/net/phy/Makefile | 1 +
> drivers/net/phy/mdio-bitbang.c | 187 ++++++++++++++++++++++++++++++++++++++++
> include/linux/mdio-bitbang.h | 42 +++++++++
> 4 files changed, 239 insertions(+), 0 deletions(-)
> create mode 100644 drivers/net/phy/mdio-bitbang.c
> create mode 100644 include/linux/mdio-bitbang.h
I cannot ACK this, nor do I want to see it merged, until users appear
and have been reviewed alongside this. I do not see any fs_enet patches
that actually use this.
five-second-glance comments:
* "mdio_bitbang_" is a long prefix. consider "mdiobb_" or somesuch
* the delay (where you call ndelay()) is not guaranteed without a flush
of some sort
* how widely applicable is this "generic" library? have you converted
any non-embedded drivers over to it?
next prev parent reply other threads:[~2007-08-31 13:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 17:53 [PATCH 0/7] fs_enet patches Scott Wood
2007-08-17 17:53 ` [PATCH 1/7] Generic bitbanged MDIO library Scott Wood
2007-08-31 13:23 ` Jeff Garzik [this message]
2007-08-31 15:16 ` Scott Wood
2007-08-17 17:53 ` [PATCH 2/7] fs_enet: Whitespace cleanup Scott Wood
2007-08-22 21:04 ` Vitaly Bordug
2007-08-31 13:19 ` Jeff Garzik
2007-08-17 17:54 ` [PATCH 3/7] fs_enet: Don't share the interrupt Scott Wood
2007-08-17 17:54 ` [PATCH 4/7] fs_enet: mac-fcc: Eliminate __fcc-* macros Scott Wood
2007-08-22 21:08 ` Vitaly Bordug
2007-08-22 21:17 ` Scott Wood
2007-08-17 17:54 ` [PATCH 5/7] fs_enet: Align receive buffers Scott Wood
2007-08-17 17:54 ` [PATCH 6/7] fs_enet: Be an of_platform device when CONFIG_PPC_CPM_NEW_BINDING is set Scott Wood
2007-08-17 17:54 ` [PATCH 7/7] fs_enet: sparse fixes Scott Wood
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=46D81638.6050509@pobox.com \
--to=jgarzik@pobox.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).