[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160715112552.GB6939@redhat.com>
Date: Fri, 15 Jul 2016 13:25:53 +0200
From: Stanislaw Gruszka <sgruszka@...hat.com>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@...el.com>
Cc: "prarit@...hat.com" <prarit@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linuxwifi <linuxwifi@...el.com>,
"Coelho, Luciano" <luciano.coelho@...el.com>,
"Berg, Johannes" <johannes.berg@...el.com>,
"kvalo@...eaurora.org" <kvalo@...eaurora.org>,
"Ivgi, Chaya Rachel" <chaya.rachel.ivgi@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Sharon, Sara" <sara.sharon@...el.com>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: Re: [PATCH RESEND] iwlwifi, Do not implement thermal zone unless
ucode is loaded
On Thu, Jul 14, 2016 at 09:44:22AM +0000, Grumbach, Emmanuel wrote:
> > If I understad correctly this error happen 100% of the time, not only during
> > init. Hence seems there is an issue here, i.e. cur_ucode is not marked
> > correctly as IWL_UCODE_REGULAR or iwl_mvm_get_temp() fail 100% of the
> > time (iwl_mvm_is_tt_in_fw() incorrecly return true on Prarit device ? ).
>
> Cur_ucode will not be IWL_UCODE_REGULAR until you load the firmware which
> will happen upon ifup.
Then creating thermal_device on ifup looks more reasonable to me.
Otherwise we can create device that can be non-functional virtually
forever, i.e. when soft RFKILL is enabled. However I admit that
creating thermal_device when HW is detected has some advantages
too.
Stanislaw
Powered by blists - more mailing lists