Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965731AbbLPDtW (ORCPT ); Tue, 15 Dec 2015 22:49:22 -0500 Received: from mail-pf0-f170.google.com ([209.85.192.170]:35798 "EHLO mail-pf0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965555AbbLPDtU (ORCPT ); Tue, 15 Dec 2015 22:49:20 -0500 From: Eduardo Valentin To: Rui Zhang Cc: Linux PM , LKML , Eduardo Valentin Subject: [PATCH 0/3] thermal: rework core to improve userspace interaction Date: Tue, 15 Dec 2015 19:49:11 -0800 Message-Id: <1450237754-31906-1-git-send-email-edubezval@gmail.com> X-Mailer: git-send-email 2.5.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1442 Lines: 39 Hello Rui, linux-pm Please consider these three patches in the thermal core to improve the interaction with userspace. The first is already in its second version. It avoids reconfiguring monitor period. Now the thermal core configures the monitor only after handling all trip points. The second is about improving emul_temp. The background here is to allow using emul_temp, even if the thermal zone is not fully setup, with a missing .get_temp(). The third is to improve hot trip points handling. Hot trip points are described as notification entry points. However, we do very little on them. This patch adds a uevent to propagate the event to userspace. Today, we rely on thermal zone driver. I believe having the same message coming on every thermal zone makes more sense. However, I did not remove the .notify() callback, and it should behave the same. BR, Eduardo Valentin (3): thermal: setup monitor only once after handling trips thermal: rework core to allow emul_temp to be treated as regular temp thermal: improve hot trip handling drivers/thermal/thermal_core.c | 96 ++++++++++++++++++++++++++++++++++-------- 1 file changed, 78 insertions(+), 18 deletions(-) -- 2.5.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/