From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/2] Add support for the ethernet switch on the ESPRESSObin
Date: Fri, 20 Jan 2017 18:43:21 +0100 [thread overview]
Message-ID: <20170120174321.GF25907@lunn.ch> (raw)
In-Reply-To: <87a8al64mp.fsf@free-electrons.com>
> What I wanted to do was to test 6390 and 6352 temperature related
> functions and to see if one of them worked. That's how I realized it was
> not possible to do it with dsa2.
Hi Gregory
Probably the best thing to do is wait until the temperature code moves
into the PHY driver. It then becomes easier to test. It probably is
the same as the 6352, or like the 6390 which i've so far failed to get
working, despite the registers being the same as the 6352.
Andrew
next prev parent reply other threads:[~2017-01-20 17:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 21:49 [PATCH v5 0/2] Add support for the ethernet switch on the ESPRESSObin Gregory CLEMENT
2017-01-19 21:49 ` [PATCH v5 1/2] net: dsa: mv88e6xxx: Don't forbid MDIO I/Os for PHY addr >= num_of_ports Gregory CLEMENT
2017-01-19 22:13 ` Vivien Didelot
2017-01-20 0:06 ` Andrew Lunn
2017-01-20 1:54 ` Vivien Didelot
2017-01-19 21:49 ` [PATCH v5 2/2] net: dsa: mv88e6xxx: Add support for ethernet switch 88E6341 Gregory CLEMENT
2017-01-19 22:26 ` Vivien Didelot
2017-01-20 0:12 ` Andrew Lunn
2017-01-20 1:55 ` Vivien Didelot
2017-01-20 17:21 ` Gregory CLEMENT
2017-01-20 17:30 ` Vivien Didelot
2017-01-20 23:15 ` Andrew Lunn
2017-01-19 22:06 ` [PATCH v5 0/2] Add support for the ethernet switch on the ESPRESSObin Andrew Lunn
2017-01-19 23:41 ` [EXT] " Jon Pannell
2017-01-20 17:08 ` Gregory CLEMENT
2017-01-20 17:43 ` Andrew Lunn [this message]
2017-01-20 22:38 ` Andrew Lunn
2017-01-19 22:07 ` Vivien Didelot
2017-01-19 22:33 ` Vivien Didelot
2017-01-20 19:17 ` David Miller
2017-01-24 16:47 ` Gregory CLEMENT
2017-01-24 18:08 ` Vivien Didelot
2017-01-24 19:57 ` Andrew Lunn
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=20170120174321.GF25907@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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).