From: Kevin Hilman <khilman@deeprootsystems•com>
To: Cyril Chemparathy <cyril@ti•com>
Cc: netdev@vger•kernel.org,
davinci-linux-open-source@linux•davincidsp.com,
linux-omap@vger•kernel.org, michael.williamson@criticallink•com,
caglarakyuz@gmail•com, bparrot@ti•com
Subject: Re: [PATCH v4 00/10] split out emac cpdma and mdio for reuse
Date: Wed, 15 Sep 2010 07:54:03 -0700 [thread overview]
Message-ID: <87aanjgir8.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1284559890-31346-1-git-send-email-cyril@ti.com> (Cyril Chemparathy's message of "Wed, 15 Sep 2010 10:11:20 -0400")
Cyril Chemparathy <cyril@ti•com> writes:
> Davinci's EMAC device has an in-built MDIO controller and a CPDMA engine.
> These hardware modules are not restricted to EMAC device alone. For example,
> CPSW3G (3-port gigabit ethernet switch) hardware uses these very same modules
> internally. This patch series separates out EMAC's MDIO and CPDMA
> functionality, allowing these individual pieces to be reused across TI
> hardware.
[...]
> Changes from v3 (rolled in "post cpdma/mdio refactoring fixes" series):
> 1. allow forced 100/full mode instead of phy auto-detect
> 2. specify phy_id on boards that had a phy_mask defined earlier
> 3. requeue cpdma descriptors when EOQ at submit
> 4. use calculated mdio bus access times instead of hardcoded delays
> 5. work around emac soft-reset impact on mdio controller state
> 6. extend register dumps to include cpdma registers
> 7. updated sign offs and acks
Thanks Cyril for one more spin with these updates. Queuing this one for
2.6.37 in davinci-next.
davinci git is now updated with this series (may take a bit to propagate
to kernel.org mirrors though)
Kevin
next prev parent reply other threads:[~2010-09-15 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 14:11 [PATCH v4 00/10] split out emac cpdma and mdio for reuse Cyril Chemparathy
2010-09-15 14:11 ` [PATCH v4 01/10] net: davinci_emac: separate out davinci mdio Cyril Chemparathy
2010-09-15 14:11 ` [PATCH v4 02/10] davinci: add mdio platform devices Cyril Chemparathy
2010-09-15 14:11 ` [PATCH v4 03/10] omap: " Cyril Chemparathy
2010-09-15 14:11 ` [PATCH v4 04/10] net: davinci_emac: switch to new mdio Cyril Chemparathy
2010-09-15 14:11 ` [PATCH v4 05/10] davinci: cleanup mdio arch code and switch to phy_id Cyril Chemparathy
2010-09-15 14:11 ` [PATCH v4 06/10] omap: cleanup unused davinci mdio arch code Cyril Chemparathy
2010-09-15 14:11 ` [PATCH v4 07/10] net: davinci_emac: cleanup unused mdio emac code Cyril Chemparathy
2010-09-15 14:11 ` [PATCH v4 08/10] net: davinci_emac: separate out cpdma code Cyril Chemparathy
2010-09-15 14:11 ` [PATCH v4 09/10] net: davinci_emac: switch to new cpdma layer Cyril Chemparathy
2010-09-15 14:11 ` [PATCH v4 10/10] net: davinci_emac: cleanup unused cpdma code Cyril Chemparathy
2010-09-15 14:54 ` Kevin Hilman [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-14 21:10 [PATCH v4 00/10] split out emac cpdma and mdio for reuse Cyril Chemparathy
2010-09-14 23:10 ` Kevin Hilman
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=87aanjgir8.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems$(echo .)com \
--cc=bparrot@ti$(echo .)com \
--cc=caglarakyuz@gmail$(echo .)com \
--cc=cyril@ti$(echo .)com \
--cc=davinci-linux-open-source@linux$(echo .)davincidsp.com \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=michael.williamson@criticallink$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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