Re: [PATCH 4/8] thunderbolt: Do not fail adding switch if some port is not implemented

2019-08-05 Thread Mika Westerberg
On Sat, Aug 03, 2019 at 04:14:01PM +0200, Lukas Wunner wrote: > On Fri, Jul 05, 2019 at 12:57:56PM +0300, Mika Westerberg wrote: > > There are two ways to mark a port as unimplemented. Typical way is to > > return port type as TB_TYPE_INACTIVE when its config space is read. > > Alternatively if the

Re: [PATCH 4/8] thunderbolt: Do not fail adding switch if some port is not implemented

2019-08-03 Thread Lukas Wunner
On Fri, Jul 05, 2019 at 12:57:56PM +0300, Mika Westerberg wrote: > There are two ways to mark a port as unimplemented. Typical way is to > return port type as TB_TYPE_INACTIVE when its config space is read. > Alternatively if the port is not physically present (such as ports 10 > and 11 in ICL) rea

[PATCH 4/8] thunderbolt: Do not fail adding switch if some port is not implemented

2019-07-05 Thread Mika Westerberg
There are two ways to mark a port as unimplemented. Typical way is to return port type as TB_TYPE_INACTIVE when its config space is read. Alternatively if the port is not physically present (such as ports 10 and 11 in ICL) reading from port config space returns TB_CFG_ERROR_INVALID_CONFIG_SPACE ins