From: Florian Fainelli <f.fainelli@gmail.com>
To: David Daney <david.daney@cavium.com>,
netdev@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of_mdio: Add "broadcom,bcm5241" to the whitelist.
Date: Fri, 17 Feb 2017 12:09:29 -0800 [thread overview]
Message-ID: <799d4300-64f0-1fb2-2ef7-870a4d5fac20@gmail.com> (raw)
In-Reply-To: <20170217200412.11680-1-david.daney@cavium.com>
On 02/17/2017 12:04 PM, David Daney wrote:
> Some Cavium dev boards have firmware which doesn't supply a proper
> ethernet-phy-ieee802.3-c22" compatible property. Restore these boards
> to working order by whitelisting this compatible value.
>
> Signed-off-by: David Daney <david.daney@cavium.com>
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> drivers/of/of_mdio.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/of/of_mdio.c b/drivers/of/of_mdio.c
> index 262281b..0b29798 100644
> --- a/drivers/of/of_mdio.c
> +++ b/drivers/of/of_mdio.c
> @@ -147,6 +147,7 @@ EXPORT_SYMBOL(of_mdio_parse_addr);
> */
> static const struct of_device_id whitelist_phys[] = {
> { .compatible = "brcm,40nm-ephy" },
> + { .compatible = "broadcom,bcm5241" },
And that's not the vendor prefix from vendor-prefixes.txt.
> { .compatible = "marvell,88E1111", },
> { .compatible = "marvell,88e1116", },
> { .compatible = "marvell,88e1118", },
>
--
Florian
next prev parent reply other threads:[~2017-02-17 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 20:04 David Daney
2017-02-17 20:09 ` Florian Fainelli [this message]
2017-02-17 21:41 ` David Daney
2017-02-19 23:20 ` 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=799d4300-64f0-1fb2-2ef7-870a4d5fac20@gmail.com \
--to=f.fainelli@gmail.com \
--cc=david.daney@cavium.com \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®