Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp5491022imm; Tue, 26 Jun 2018 12:11:03 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKlgnpV55EhoZCrRmAnkyuVDv+6JqpJlSIN3dvuraj5oVoA0F48BGlWObL6Lm7+BTG/ZdKJ X-Received: by 2002:a17:902:5991:: with SMTP id p17-v6mr2814663pli.191.1530040263496; Tue, 26 Jun 2018 12:11:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530040263; cv=none; d=google.com; s=arc-20160816; b=FVeSQ7Aj6ES4Dd3utfK3D3+YTDRCSXe1OB42PHB1+bTnPgWtqsPxAo+x1JrkX4n9QA uQjv/+m8fWyIhmIg5s+GBBGPtJsQLrePMt3vkEg/m/9+Ho0Htilh1G4m+1dr+c+uT1CM iaWckXuE+KUFERfCLRk1WoMWpcmiC52kJfnUy1/j0gsNzlZ131U/KzOt7Y3xBvDiuJo1 SZ78aL//pm6Zy8DOtTV6ojjsvT4gWC3KVivg9MEAEyRTMP07A2ZaXqoBf38+dzzGTfIn O3+9EFSFKcff7YuXev7Z4J7Gz8uYakWHtksQ3qiqpeAXi0PoHQTXPg6Rr4W4Sn++0Nwj J8UA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature :arc-authentication-results; bh=ObE4VSNadsLY0cMdB1Sp4s1MUklkjrNLCp6Wfhc0gfo=; b=p+fLrtdniDz53CzYUBkzfaYYs6gIEC8Q6XiAJSH2PpJBeQkGShwQDcToDHi4rVd1pm THCGpc69DVufVXduaOAMRnVf/e/cZqcJCuWNfcNJld0x9JP6P0FvlzER6xDPU15hvjoG xRnh7/8Y2yF9rF5f+gn8iuY4iqcPVBum1ETe67NX35+1NbQI8qllocnsXunbbsAPSSWp FQpJIiMVYZpnH1FaZATw2KgP2iPB+8g3OTHpLwLPHGjUd94kbCmQZCDT43ZBfpoLAJmQ 7P/QNJbmBaEfh6CrUYE68nr8QlG0kONp6oZtNykcJxmcyKRLak0p+FdFepjod70bqDWy Qogw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=NtPOmCwL; 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=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g1-v6si2238775pld.11.2018.06.26.12.10.48; Tue, 26 Jun 2018 12:11:03 -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=@kernel.org header.s=default header.b=NtPOmCwL; 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=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933973AbeFZSXJ (ORCPT + 99 others); Tue, 26 Jun 2018 14:23:09 -0400 Received: from mail.kernel.org ([198.145.29.99]:42254 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933164AbeFZSXI (ORCPT ); Tue, 26 Jun 2018 14:23:08 -0400 Received: from mail-io0-f176.google.com (mail-io0-f176.google.com [209.85.223.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8156926EF5; Tue, 26 Jun 2018 18:23:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1530037387; bh=M/uwk1NjIHmdVTVAVug6c00vYgYTUz3rkOv8B3ojfJE=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=NtPOmCwLRfvuZ6jejKy8BywKwXwhHMXn0lhfxe2zEohzae1PM2jJq3ebRJksi3ah9 fvYTN3f+9gykrj6OP0QJJbGMoOC+0E0CS329jO4GqPZfRIX46nsQgR64QOVem9JZmJ tu6N95UH5LLzXCnrNmzZl6eX6Jdo7HM0rFtBVMeU= Received: by mail-io0-f176.google.com with SMTP id g7-v6so16831815ioh.11; Tue, 26 Jun 2018 11:23:07 -0700 (PDT) X-Gm-Message-State: APt69E1QJmK5nbLUko18O/oq5wu4vLqRG4lKLqd1svvab/gQly4AgNiT 44kTzW7/gRa9bHuIOf4iDsOhedZuG+rJohuMww== X-Received: by 2002:a5e:c90e:: with SMTP id z14-v6mr63047iol.268.1530037386934; Tue, 26 Jun 2018 11:23:06 -0700 (PDT) MIME-Version: 1.0 References: <20180626164701.1034-1-robert.jarzmik@free.fr> In-Reply-To: <20180626164701.1034-1-robert.jarzmik@free.fr> From: Rob Herring Date: Tue, 26 Jun 2018 12:22:54 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] ARM: dts: pxa: fix the rtc controller To: Robert Jarzmik Cc: Daniel Mack , Haojian Zhuang , Mark Rutland , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 26, 2018 at 10:47 AM Robert Jarzmik wrote: > > The RTC controller is fed by an external fixed 32kHz clock. Yet the > driver wants to acquire this clock, even though it doesn't make any use > of it, ie. doesn't get the rate to make calculation. > > Therefore, add the dummy clock in the PXA clock tree to make the driver > happy and working. > > Signed-off-by: Robert Jarzmik > --- > arch/arm/boot/dts/pxa25x.dtsi | 4 ++++ > arch/arm/boot/dts/pxa27x.dtsi | 4 ++++ > 2 files changed, 8 insertions(+) > > diff --git a/arch/arm/boot/dts/pxa25x.dtsi b/arch/arm/boot/dts/pxa25x.dtsi > index 95d59be97213..c6ca07e4626b 100644 > --- a/arch/arm/boot/dts/pxa25x.dtsi > +++ b/arch/arm/boot/dts/pxa25x.dtsi > @@ -80,6 +80,10 @@ > #pwm-cells = <1>; > clocks = <&clks CLK_PWM1>; > }; > + > + rtc@40900000 { > + clocks = <&clks CLK_NONE>; Don't add fake clocks. Either add a real clock or fix the driver to not require a clock. Rob