From: Christian Eggers <ceggers@arri.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Woojung Huh <woojung.huh@microchip.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] net: dsa: microchip: add ksz9563 to ksz9477 I2C driver
Date: Wed, 7 Oct 2020 15:13:15 +0200 [thread overview]
Message-ID: <5079657.ehXnlxHBby@n95hx1g2> (raw)
In-Reply-To: <20201007122107.GA112961@lunn.ch>
Hi Andrew,
> What chip_id values does it use? I don't see it listed in
> ksz9477_switch_chips.
here a short dump of the first chip registers:
> Chip ID0 00
> Chip ID1_2 9893 Chip ID 9893
> Chip ID3 60 Revision ID 6 Reset normal
> Chip ID4 1C SKU ID 1C
In ksz9477_switch_detect(), the 32 bit value is built from only
the 2 middle bytes: 0x00989300. The number of port (3) is also
assigned within this function:
> if ((id_lo & 0xf) == 3) {
> /* Chip is from KSZ9893 design. */
> dev->features |= IS_9893;
> /* Chip does not support gigabit. */
> if (data8 & SW_QW_ABLE)
> dev->features &= ~GBIT_SUPPORT;
> dev->mib_port_cnt = 3;
> dev->phy_port_cnt = 2;
> } ...
The chip id 0x00989300 does already exist in ksz9477_switch_chips:
> {
> .chip_id = 0x00989300,
> .dev_name = "KSZ9893",
> .num_vlans = 4096,
> .num_alus = 4096,
> .num_statics = 16,
> .cpu_ports = 0x07, /* can be configured as cpu port */
> .port_cnt = 3, /* total port count */
> },
But my chip is really a KSZ9563.
Best regards
Christian
next prev parent reply other threads:[~2020-10-07 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 9:30 [PATCH net-next] net: dsa: microchip: add ksz9563 to ksz9477 I2C driver Christian Eggers
2020-10-07 12:21 ` Andrew Lunn
2020-10-07 13:13 ` Christian Eggers [this message]
2020-10-07 13:19 ` Andrew Lunn
2020-10-07 13:20 ` Andrew Lunn
2020-10-09 20:08 ` Jakub Kicinski
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=5079657.ehXnlxHBby@n95hx1g2 \
--to=ceggers@arri.de \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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 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.