From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932574AbcAYMvd (ORCPT ); Mon, 25 Jan 2016 07:51:33 -0500 Received: from mail.karo-electronics.de ([81.173.242.67]:49253 "EHLO mail.karo-electronics.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757174AbcAYMv2 convert rfc822-to-8bit (ORCPT ); Mon, 25 Jan 2016 07:51:28 -0500 Date: Mon, 25 Jan 2016 13:51:09 +0100 From: Lothar =?UTF-8?B?V2HDn21hbm4=?= To: Mark Brown Cc: =?UTF-8?B?QmVub8OudA==?= Cousson , Ian Campbell , Kumar Gala , Liam Girdwood , Mark Rutland , Pawel Moll , Rob Herring , Russell King , Tony Lindgren , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org Subject: Re: [PATCH 1/2] regulator: ltc3589: make IRQ optional Message-ID: <20160125135109.760ba5f0@ipc1.ka-ro> In-Reply-To: <20160125124123.GQ6588@sirena.org.uk> References: <20160120164258.GF6588@sirena.org.uk> <20160121080524.27af489f@ipc1.ka-ro> <20160121102015.GI6588@sirena.org.uk> <20160121112611.34e17cb2@ipc1.ka-ro> <20160121111115.GJ6588@sirena.org.uk> <20160121123311.5346e40d@ipc1.ka-ro> <20160121162646.GK6588@sirena.org.uk> <20160122064145.36b7f2b4@ipc1.ka-ro> <20160122162610.GZ6588@sirena.org.uk> <20160125133731.72669115@ipc1.ka-ro> <20160125124123.GQ6588@sirena.org.uk> Organization: Ka-Ro electronics GmbH MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Mon, 25 Jan 2016 12:41:23 +0000 Mark Brown wrote: > On Mon, Jan 25, 2016 at 01:37:31PM +0100, Lothar Waßmann wrote: > > On Fri, 22 Jan 2016 16:26:10 +0000 Mark Brown wrote: > > > > You're not just making the interrupt optional, you are also implementing > > > polling support. That's really unusual and there's no clear reason for > > > Any suggestions how to handle this case in a more sensible way? > > The above, for example - make the interrupt optional. > This will make it impossible to notify the system about overtemperature (and undervoltage). I implemented polling to be able to get at least overtemperature warnings. (Undervoltage cannot be handled sensibly without interrupt anyway) Lothar Waßmann