From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: Joachim Eastwood <manabian@gmail.com>, <davem@davemloft.net>
Cc: <alexandre.torgue@st.com>, <netdev@vger.kernel.org>
Subject: Re: [net-next PATCH 0/7] stmmac: dwmac-sti refactor+cleanup
Date: Fri, 4 Nov 2016 14:49:31 +0100 [thread overview]
Message-ID: <5eb811e8-0d1d-2e9e-245c-043a07c87bca@st.com> (raw)
In-Reply-To: <20161030200507.851-1-manabian@gmail.com>
Hello Joachim.
I have tested the patches on STiH390 with GMAC4 and the driver is ok.
So you can add my Acked-by/Tested-by in the V2.
I just ask you, when rename the sti_dwmac_init in sti_dwmac_set_phy_mode
to use another name: sti_dwmac_set_mode could be good, IMO.
In fact, this function is not strictly related to the PHY and the
system config registers could touch different MAC/MII settings.
Regards
Peppe
On 10/30/2016 9:05 PM, Joachim Eastwood wrote:
> This patch set aims to remove the init/exit callbacks from the
> dwmac-sti driver and instead use standard PM callbacks. Doing this
> will also allow us to cleanup the driver.
>
> Eventually the init/exit callbacks will be deprecated and removed
> from all drivers dwmac-* except for dwmac-generic. Drivers will be
> refactored to use standard PM and remove callbacks.
>
> Note that this patch set has only been test compiled and no functional
> change is intended.
>
> Joachim Eastwood (7):
> stmmac: dwmac-sti: remove useless of_node check
> stmmac: dwmac-sti: remove clk NULL checks
> stmmac: dwmac-sti: add PM ops and resume function
> stmmac: dwmac-sti: move st,gmac_en parsing to sti_dwmac_parse_data
> stmmac: dwmac-sti: move clk_prepare_enable out of init and add error handling
> stmmac: dwmac-sti: clean up and rename sti_dwmac_init
> stmmac: dwmac-sti: remove unused priv dev member
>
> drivers/net/ethernet/stmicro/stmmac/dwmac-sti.c | 86 ++++++++++++++++---------
> 1 file changed, 57 insertions(+), 29 deletions(-)
>
next prev parent reply other threads:[~2016-11-04 13:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 20:05 [net-next PATCH 0/7] stmmac: dwmac-sti refactor+cleanup Joachim Eastwood
2016-10-30 20:05 ` [net-next PATCH 1/7] stmmac: dwmac-sti: remove useless of_node check Joachim Eastwood
2016-10-30 20:05 ` [net-next PATCH 2/7] stmmac: dwmac-sti: remove clk NULL checks Joachim Eastwood
2016-10-30 20:05 ` [net-next PATCH 3/7] stmmac: dwmac-sti: add PM ops and resume function Joachim Eastwood
2016-11-01 17:19 ` Joachim Eastwood
2016-10-30 20:05 ` [net-next PATCH 4/7] stmmac: dwmac-sti: move st,gmac_en parsing to sti_dwmac_parse_data Joachim Eastwood
2016-10-30 20:05 ` [net-next PATCH 5/7] stmmac: dwmac-sti: move clk_prepare_enable out of init and add error handling Joachim Eastwood
2016-10-30 20:05 ` [net-next PATCH 6/7] stmmac: dwmac-sti: clean up and rename sti_dwmac_init Joachim Eastwood
2016-10-30 20:05 ` [net-next PATCH 7/7] stmmac: dwmac-sti: remove unused priv dev member Joachim Eastwood
2016-10-31 19:47 ` [net-next PATCH 0/7] stmmac: dwmac-sti refactor+cleanup David Miller
2016-11-01 15:56 ` David Miller
2016-11-01 17:00 ` Joachim Eastwood
2016-11-02 6:39 ` Giuseppe CAVALLARO
2016-11-04 13:49 ` Giuseppe CAVALLARO [this message]
2016-11-04 16:19 ` Joachim Eastwood
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=5eb811e8-0d1d-2e9e-245c-043a07c87bca@st.com \
--to=peppe.cavallaro@st.com \
--cc=alexandre.torgue@st.com \
--cc=davem@davemloft.net \
--cc=manabian@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).