[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191004151621.GL2819@lahna.fi.intel.com>
Date: Fri, 4 Oct 2019 18:16:21 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Christian Kellner <christian@...lner.me>
Cc: Mario.Limonciello@...l.com, yehezkelshb@...il.com,
linux-usb@...r.kernel.org, andreas.noever@...il.com,
michael.jamet@...el.com, rajmohan.mani@...el.com,
nicholas.johnson-opensource@...look.com.au, lukas@...ner.de,
gregkh@...uxfoundation.org, stern@...land.harvard.edu,
anthony.wong@...onical.com, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 17/22] thunderbolt: Add initial support for USB4
On Fri, Oct 04, 2019 at 05:02:37PM +0200, Christian Kellner wrote:
> Should work. What would the value be for Thunderbolt 3 (and before)? I
> guess '0' if I am looking at the right thing (bits 31:24 in
> ROUTER_CS_4)?
Yes, it would be 0x10 and below that depending on the generation.
> Is there any harm of also having the 'generation' exposed
> as well? I like the simplicity of the mapping from that value to
> Thunderbolt/USB4 standard version (e.g. I would show that in 'boltctl
> list'); 'hw_version' will need a bit more "interpreting".
If generation is the only thing you need, we can export that now and
forget hw_version :)
Powered by blists - more mailing lists