From: Marek Vasut <marex@denx.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: dsa: mv88e6xxx: Add MV88E6352 DT compatible
Date: Wed, 12 Sep 2018 01:17:19 +0200 [thread overview]
Message-ID: <d49cd07e-70e6-311c-1783-d22def3fe48e@denx.de> (raw)
In-Reply-To: <20180911231246.GB11474@lunn.ch>
On 09/12/2018 01:12 AM, Andrew Lunn wrote:
> On Wed, Sep 12, 2018 at 12:15:36AM +0200, Marek Vasut wrote:
>> Add DT compatible string for MV88E6352 switch.
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> Cc: Andrew Lunn <andrew@lunn.ch>
>> ---
>> drivers/net/dsa/mv88e6xxx/chip.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/net/dsa/mv88e6xxx/chip.c b/drivers/net/dsa/mv88e6xxx/chip.c
>> index e07838430d16..15427380e32e 100644
>> --- a/drivers/net/dsa/mv88e6xxx/chip.c
>> +++ b/drivers/net/dsa/mv88e6xxx/chip.c
>> @@ -4796,6 +4796,10 @@ static const struct of_device_id mv88e6xxx_of_match[] = {
>> .compatible = "marvell,mv88e6190",
>> .data = &mv88e6xxx_table[MV88E6190],
>> },
>> + {
>> + .compatible = "marvell,mv88e6352",
>> + .data = &mv88e6xxx_table[MV88E6352],
>> + },
>
> NACK.
>
> Not needed. Lots of devices use the 6352. It is compatible to the
> marvell,mv88e6085.
So I should have both values in my DT, that is
compatible = "marvell,mv88e6352", "marvell,mv88e6085";
? That works for me ...
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-09-12 4:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 22:15 [PATCH] net: dsa: mv88e6xxx: Add MV88E6352 DT compatible Marek Vasut
2018-09-11 23:12 ` Andrew Lunn
2018-09-11 23:17 ` Marek Vasut [this message]
2018-09-11 23:32 ` Andrew Lunn
2018-09-11 23:52 ` Brandon Streiff
2018-09-12 0:04 ` Marek Vasut
2018-09-12 0:46 ` Andrew Lunn
2018-09-12 8:38 ` Marek Vasut
2018-09-12 12:47 ` Andrew Lunn
2018-09-12 13:10 ` Marek Vasut
2018-09-12 13:32 ` Andrew Lunn
2018-09-12 13:35 ` Marek Vasut
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=d49cd07e-70e6-311c-1783-d22def3fe48e@denx.de \
--to=marex@denx.de \
--cc=andrew@lunn.ch \
--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).