Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752679AbbBWTEk (ORCPT ); Mon, 23 Feb 2015 14:04:40 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:37336 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752283AbbBWTEi (ORCPT ); Mon, 23 Feb 2015 14:04:38 -0500 Message-ID: <54EB79C4.50405@codeaurora.org> Date: Mon, 23 Feb 2015 11:04:36 -0800 From: Stephen Boyd User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Mathieu Olivari , robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, linux@arm.linux.org.uk, wim@iguana.be, corbet@lwn.net, standby24x7@gmail.com CC: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-watchdog@vger.kernel.org Subject: Re: [PATCH 1/3] watchdog: qcom: use timer devicetree binding References: <1424485176-8348-1-git-send-email-mathieu@codeaurora.org> <1424485176-8348-2-git-send-email-mathieu@codeaurora.org> In-Reply-To: <1424485176-8348-2-git-send-email-mathieu@codeaurora.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 769 Lines: 21 On 02/20/15 18:19, Mathieu Olivari wrote: > MSM watchdog configuration happens in the same register block as the > timer, so we'll use the same binding as the existing timer. > > The qcom-wdt will now be probed when devicetree has an entry compatible > with "qcom,kpss-timer" or "qcom-scss-timer". > > Signed-off-by: Mathieu Olivari > Reviewed-by: Stephen Boyd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- 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/