Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755088AbcC3RHs (ORCPT ); Wed, 30 Mar 2016 13:07:48 -0400 Received: from mga09.intel.com ([134.134.136.24]:50053 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751976AbcC3RHq (ORCPT ); Wed, 30 Mar 2016 13:07:46 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,417,1455004800"; d="scan'208";a="944617148" Message-ID: <1459357591.13525.62.camel@linux.intel.com> Subject: Re: [PATCH v2] thermal: add sysfs_notify on some attributes From: Srinivas Pandruvada To: Eduardo Valentin Cc: "Zhang, Rui" , "linux-kernel@vger.kernel.org" , "srikars@nvidia.com" , "linux-pm@vger.kernel.org" , "linux-tegra@vger.kernel.org" , "mlongnecker@nvidia.com" Date: Wed, 30 Mar 2016 10:06:31 -0700 In-Reply-To: <20160329013540.GA15615@localhost.localdomain> References: <1457979156-10972-1-git-send-email-srikars@nvidia.com> <1458079520.4486.39.camel@intel.com> <20160329013540.GA15615@localhost.localdomain> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.1 (3.18.5.1-1.fc23) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1449 Lines: 45 On Mon, 2016-03-28 at 18:35 -0700, Eduardo Valentin wrote: > On Tue, Mar 15, 2016 at 11:08:00PM +0000, Pandruvada, Srinivas wrote: > > > > On Mon, 2016-03-14 at 11:12 -0700, Srikar Srimath Tirumala wrote: > > > > > > [...] > > > The complexity of such communication (or even the current status of > sysfs ABI) starts to reach limit of such channel. We may definitely > consider other means, such as /dev interface, just like IIO does. Yes. Instead of loading netlink I/F, we need to have thermal channel to notify. > > During last LPC we discussed about using IIO for temperature > > threshold > > notifications and I submitted multiple changes for that. Looks like > > we > > also care of trip point changes. So I think we need more > > comprehensive > > mechanism to address this. > > > > May be we should have thermal mini summit during LPC again and > > decide a > > comprehensive plan to address all asynchronous thermal > > notifications. > > > I have created a wiki for LPC 2016 > http://wiki.linuxplumbersconf.org/2016:thermal > > Overall I believe we need to solve the (temperature) sensing in a > more > structured way within the kernel. We have three subsystem that allow > performing temperature sensing. They are different in design and > concept, but still solve similar problems. > > Again, please lets generate enough quorum to run the micro conf. > I am planning to attend. Thanks, Srinivas > BR,  > > Eduardo Valentin