From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751566AbeBZTqv (ORCPT ); Mon, 26 Feb 2018 14:46:51 -0500 Received: from mga02.intel.com ([134.134.136.20]:58877 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751465AbeBZTqu (ORCPT ); Mon, 26 Feb 2018 14:46:50 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,397,1515484800"; d="scan'208";a="34291662" Date: Mon, 26 Feb 2018 21:46:45 +0200 From: Mika Westerberg To: Jeremy McNicoll Cc: linux-kernel@vger.kernel.org, Andreas Noever , Michael Jamet , Yehezkel Bernat , Bjorn Helgaas , Mario.Limonciello@dell.com, Radion Mirchevsky Subject: Re: [07/18] thunderbolt: Handle rejected Thunderbolt devices Message-ID: <20180226194645.GA3774@lahna.fi.intel.com> References: <20180213170018.9780-8-mika.westerberg@linux.intel.com> <20180222231736.GA628@mini-rhel.redhat.com> <20180226102029.GG27191@lahna.fi.intel.com> <20180226133802.GR27191@lahna.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 26, 2018 at 11:28:16AM -0800, Jeremy McNicoll wrote: > On 2018-02-26 5:38 AM, Mika Westerberg wrote: > > On Mon, Feb 26, 2018 at 12:20:29PM +0200, Mika Westerberg wrote: > > > On Thu, Feb 22, 2018 at 03:17:38PM -0800, Jeremy McNicoll wrote: > > > > > + if (pkg->link_info & ICM_LINK_INFO_REJECTED) { > > > > > + tb_info(tb, "switch at %u.%u was rejected by ICM firmware\n", > > > > > + link, depth); > > > > > > > > This kind of condition sounds more like an error instead of info. > > > > Please bump this up to tb_WARN/tb_warn ideally tb_err(). > > > > > > No, this is not an error. > > > > To be more clear, it is totally fine to have the firmware to reject some > > devices. For example in case of the new usbonly security level the > > firmware rejects other devices but the first. > > > > Ok. Is that kind of information available to the kernel? What security > mode we are in? > > ie) if (LINK_REJECTED && !USB_SECURITY) > print "Error switch %u was rejected since its not usbonly" > endif > > I am sure something like that simplified pseudo code above would > be somewhat useful to users when debugging. That's why it is on info level so it goes to dmesg but does not scare the user :-)