Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp440319imm; Thu, 31 May 2018 03:24:17 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIIhEOJphy2pScGskCeGCgTaXi8xjtlXW3tEyaTMEb5tW8gOeqobiaudZFVR1UqhArahTpH X-Received: by 2002:a17:902:2983:: with SMTP id h3-v6mr6459976plb.232.1527762257902; Thu, 31 May 2018 03:24:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527762257; cv=none; d=google.com; s=arc-20160816; b=xvr2bTsuO+2l/Hsii6FgCuRMR9TlLxeRFOYPDWgswBnw+6+Z8n2oP1EJC1ZuFAeQfg yLP9rha/1AvQZv8277G4Q2TcDBnZO75ecQ+dPLFJTp2NPm39xXaSThZME0OLYlKK5Bz6 +uoW2HLS4f6yZxYtOMXkiP5rT8kc+T+I2B8QpCBWkjbCY8Rt9mk2Rl1fgWsJ5hFNwVhl XrsG7jbeq8K1XXGknUhV9IUCD1fZyLJ+5B6NCT8RoYZym4+fjUuTdwurcYVu4OA9cKzM 6iPCgqjMbsni+7eLlwefxSgetwjuVWwoiNqUaR3nQ9kNkVW/UstfGSQrX/GQH+5cBEQL 3wTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:date:from:dkim-signature:arc-authentication-results; bh=/9Zfm3CoXcP9e1DoNX6uCV20eGXrwqw6C8qs+KLGlfo=; b=qIR9ZEmOoQWkc6ChVy4ogzvotCMkjGij955TT/QfNG3pjHogHkV1zhDx/4kV4K4lQ7 K0TMLYvc0pKwq9CidXUjiKowshqHpm6fVBB9yGzn/B7PKV+W5k8+VbeNeKV/eFeYYBj7 UWjnsBen6wppk9XiY6NfTQko29qMLQISqPv23a/NDlI+868I19NOkMc8TGIt7/+yPbMI OrvQ4EVAM5diHAA7YuvAhhHE41TRTAq3tHjCmAwg79DMgsvbsgu9CaF+qb33rI8+q2JL mP/hk1sLGzPXx3phC5i1PflbnUrVeFEksgBqPYcElRPfjL/XoFDyi202PXBEPUofn7OL GcEw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Cjn+5gB5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f64-v6si37829393pfa.252.2018.05.31.03.24.03; Thu, 31 May 2018 03:24:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Cjn+5gB5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754456AbeEaKX3 (ORCPT + 99 others); Thu, 31 May 2018 06:23:29 -0400 Received: from mail-lf0-f65.google.com ([209.85.215.65]:33381 "EHLO mail-lf0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754324AbeEaKXZ (ORCPT ); Thu, 31 May 2018 06:23:25 -0400 Received: by mail-lf0-f65.google.com with SMTP id y20-v6so8944185lfy.0; Thu, 31 May 2018 03:23:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=/9Zfm3CoXcP9e1DoNX6uCV20eGXrwqw6C8qs+KLGlfo=; b=Cjn+5gB5EuOKd6vnBO2aG9MPkxby2YlvNIXw+ZJ3nTyV6twwJUlDrfoF0htjeVKeve 2oS0djuHb+h+8qhc0OUfVK1IVw7pEHP06Kq8S1U1GntId8W4ieonXFFMiPDbYA1yUg9C 9j/ByoXVNN8E9ydfKI1SgSVrGEzzdDBwY6JP3CUr39T5Ix9s8yXsAuCTMZig36zxjy/h vnQOAd5ca61mmXWoxIsvpFxEZO/TTG3DKPvz+Gr1/8+r3+0QrJDv2hNnzatstk2xSQ+V ZLlBylCrUfE1/qC/XRpViohDL3n7St65NNr3CXK+BTEz1SwzBtRrTnXUU85EgpmbwY9F ZjVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=/9Zfm3CoXcP9e1DoNX6uCV20eGXrwqw6C8qs+KLGlfo=; b=KU2FPgRqyhHjBYLxytKXIxjSTpEfAT8TBLG8iSpSgUNbPS6Ku9vlunp0DuZkKuferV yUXc/g+zZPXEZTmgf0gaA3EYl/rocHyTyyOAUUNRA93/VpGaXDVm9AkZoa9k1JIIBx3K pOk06DjM7ese/1+2zN8GIlXngfdJc8Hr4VwKsAFMb1PKfP/QMUBQiW18dYNIoOEzZnoB uw9I/fQOdgbDG9tdhDns1iYAKt8OHmz042tfssLuvn2CychGSu5Ku3ArPwZKRaryA3LJ Gf6au0ozOwUcwqYzDPlVql8JQeAAyog3EmFm5vcTi2Ivz+zv8f9I5vWMo5i0RpX3uTyl rV7w== X-Gm-Message-State: ALKqPwcxWlSYaQDNFB+AG++77hEKZmIgjXy/EJRGEU1XB9qyz63zt0eS 2kiHfZz+czrtyejKtsn0RF96t+Xd X-Received: by 2002:a2e:60:: with SMTP id 93-v6mr1541862lja.96.1527762204117; Thu, 31 May 2018 03:23:24 -0700 (PDT) Received: from localhost.localdomain ([213.255.186.34]) by smtp.gmail.com with ESMTPSA id m81-v6sm8200403lfi.1.2018.05.31.03.23.22 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 31 May 2018 03:23:23 -0700 (PDT) From: Matti Vaittinen X-Google-Original-From: Matti Vaittinen Date: Thu, 31 May 2018 13:23:15 +0300 To: Matti Vaittinen Cc: Rob Herring , Matti Vaittinen , mturquette@baylibre.com, sboyd@kernel.org, mark.rutland@arm.com, lee.jones@linaro.org, lgirdwood@gmail.com, broonie@kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, mikko.mutanen@fi.rohmeurope.com, heikki.haikola@fi.rohmeurope.com Subject: Re: [PATCH v4 2/6] mfd: bd71837: Devicetree bindings for ROHM BD71837 PMIC Message-ID: <20180531102315.GA5150@localhost.localdomain> References: <3b05ca98a671a762013c312f8b70543402ee7556.1527669443.git.matti.vaittinen@fi.rohmeurope.com> <20180531030129.GA16122@rob-hp-laptop> <20180531071717.GG13528@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180531071717.GG13528@localhost.localdomain> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 31, 2018 at 10:17:17AM +0300, Matti Vaittinen wrote: > Hello Rob, > > Thanks for the review! > > On Wed, May 30, 2018 at 10:01:29PM -0500, Rob Herring wrote: > > On Wed, May 30, 2018 at 11:42:03AM +0300, Matti Vaittinen wrote: > > > Document devicetree bindings for ROHM BD71837 PMIC MFD. > > > + - interrupts : The interrupt line the device is connected to. > > > + - interrupt-controller : Marks the device node as an interrupt controller. > > > > What sub blocks have interrupts? > > The PMIC can generate interrupts from events which cause it to reset. > Eg, irq from watchdog line change, power button pushes, reset request > via register interface etc. I don't know any generic handling for these > interrupts. In "normal" use-case this PMIC is powering the processor > where driver is running and I do not see reasonable handling because > power-reset is going to follow the irq. > Oh, but when reading this I understand that the interrupt-controller property should at least be optional. Br, Matti Vaittinen