All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew F. Davis" <afd@ti.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
	"David S . Miller" <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/5] net: phy: dp83848: Add PHY ID for TI version of DP83848C
Date: Wed, 17 Feb 2016 17:37:39 -0600	[thread overview]
Message-ID: <56C50443.8060802@ti.com> (raw)
In-Reply-To: <1454867241-20928-3-git-send-email-afd@ti.com>

On 02/07/2016 11:47 AM, Andrew F. Davis wrote:
> After acquiring National Semiconductor, TI appears to have
> changed the Vendor Model Number for the DP83848C PHYs,
> add this new ID to supported IDs.
>
> Signed-off-by: Andrew F. Davis <afd@ti.com>
> ---
>   drivers/net/phy/dp83848.c | 9 ++++++---
>   1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/phy/dp83848.c b/drivers/net/phy/dp83848.c
> index 4e78f54..d4686d5f 100644
> --- a/drivers/net/phy/dp83848.c
> +++ b/drivers/net/phy/dp83848.c
> @@ -16,7 +16,8 @@
>   #include <linux/module.h>
>   #include <linux/phy.h>
>
> -#define DP83848_PHY_ID			0x20005c90
> +#define TI_DP83848C_PHY_ID		0x20005ca0
> +#define NS_DP83848C_PHY_ID		0x20005c90
>
>   /* Registers */
>   #define DP83848_MICR			0x11
> @@ -65,7 +66,8 @@ static int dp83848_config_intr(struct phy_device *phydev)
>   }
>
>   static struct mdio_device_id __maybe_unused dp83848_tbl[] = {
> -	{ DP83848_PHY_ID, 0xfffffff0 },
> +	{ TI_DP83848C_PHY_ID, 0xfffffff0 },
> +	{ NS_DP83848C_PHY_ID, 0xfffffff0 },
>   	{ }
>   };
>   MODULE_DEVICE_TABLE(mdio, dp83848_tbl);
> @@ -91,7 +93,8 @@ MODULE_DEVICE_TABLE(mdio, dp83848_tbl);
>   	}
>
>   static struct phy_driver dp83848_driver[] = {
> -	DP83848_PHY_DRIVER(DP83848_PHY_ID, "TI DP83848 10/100 Mbps PHY"),
> +	DP83848_PHY_DRIVER(TI_DP83848C_PHY_ID, "TI DP83848C 10/100 Mbps PHY"),
> +	DP83848_PHY_DRIVER(NS_DP83848C_PHY_ID, "TI DP83848C 10/100 Mbps PHY"),

This seems to be causing a warning about duplicate file names (driver name in
sysfs), so the bottom one can probably s/TI/NS, can this be changed in-tree
before the merge or should I submit a patch?

Andrew

>   };
>   module_phy_driver(dp83848_driver);
>
>

  reply	other threads:[~2016-02-17 23:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 17:47 [PATCH v2 0/5] net: phy: dp83848: Add support for TI TLK10x Ethernet PHYs Andrew F. Davis
2016-02-07 17:47 ` [PATCH v2 1/5] net: phy: dp83848: Add macro for dp83848 compatible devices Andrew F. Davis
2016-02-07 17:47 ` [PATCH v2 2/5] net: phy: dp83848: Add PHY ID for TI version of DP83848C Andrew F. Davis
2016-02-17 23:37   ` Andrew F. Davis [this message]
2016-02-17 23:44     ` Florian Fainelli
2016-02-17 23:44       ` Florian Fainelli
2016-02-07 17:47 ` [PATCH v2 3/5] net: phy: dp83848: Reorganize code for readability and safety Andrew F. Davis
2016-02-07 18:13   ` Sergei Shtylyov
2016-02-07 17:47 ` [PATCH v2 4/5] net: phy: dp83848: Add support for TI TLK10x Ethernet PHYs Andrew F. Davis
2016-02-07 17:47 ` [PATCH v2 5/5] net: phy: dp83848: Add comments for register definitions Andrew F. Davis
2016-02-07 22:31 ` [PATCH v2 0/5] net: phy: dp83848: Add support for TI TLK10x Ethernet PHYs Florian Fainelli
2016-02-07 22:31   ` Florian Fainelli
2016-02-11 16:53 ` 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=56C50443.8060802@ti.com \
    --to=afd@ti.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.