From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, andrew@lunn.ch, vivien.didelot@savoirfairelinux.com
Subject: Re: [PATCH net-next] net: dsa: Mock-up driver
Date: Tue, 28 Mar 2017 15:16:20 -0700 [thread overview]
Message-ID: <5ce01215-9a87-1ce1-a8dd-9d4b39f7866d@gmail.com> (raw)
In-Reply-To: <20170328215624.24888-1-f.fainelli@gmail.com>
On 03/28/2017 02:56 PM, Florian Fainelli wrote:
> This patch adds support for a DSA mock-up driver which essentially does
> the following:
>
> - registers/unregisters 4 fixed PHYs to the slave network devices
> - uses eth0 (configurable) as the master netdev
> - registers the switch as a fixed MDIO device against the fixed MDIO bus
> at address 31
> - includes dynamic debug prints for dsa_switch_ops functions that can be
> enabled to get call traces
>
> This is a good way to test modular builds as well as exercise the DSA
> APIs without requiring access to real hardware. This does not test the
> data-path, although this could be added later on.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> diff --git a/include/linux/phy_fixed.h b/include/linux/phy_fixed.h
> index 1d41ec44e39d..e352bc315e00 100644
> --- a/include/linux/phy_fixed.h
> +++ b/include/linux/phy_fixed.h
> @@ -26,6 +26,7 @@ extern int fixed_phy_set_link_update(struct phy_device *phydev,
> extern int fixed_phy_update_state(struct phy_device *phydev,
> const struct fixed_phy_status *status,
> const struct fixed_phy_status *changed);
> +extern struct device *platform_fmb_bus_get(void);
This is from a previous iteration of the driver and is no longer
required, I will respin, provided that we see value in having this
driver live in the kernel.
--
Florian
prev parent reply other threads:[~2017-03-28 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 21:56 [PATCH net-next] net: dsa: Mock-up driver Florian Fainelli
2017-03-28 22:16 ` Florian Fainelli [this message]
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=5ce01215-9a87-1ce1-a8dd-9d4b39f7866d@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).