From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756408AbbJIOp2 (ORCPT ); Fri, 9 Oct 2015 10:45:28 -0400 Received: from mail-ob0-f180.google.com ([209.85.214.180]:36609 "EHLO mail-ob0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754227AbbJIOp0 (ORCPT ); Fri, 9 Oct 2015 10:45:26 -0400 MIME-Version: 1.0 In-Reply-To: <20151009201356.78488116@xhacker> References: <1444352635-21965-1-git-send-email-mw@semihalf.com> <1444352635-21965-3-git-send-email-mw@semihalf.com> <20151009201356.78488116@xhacker> Date: Fri, 9 Oct 2015 16:45:25 +0200 Message-ID: Subject: Re: [PATCH v2 2/5] mmc: sdhci-pxav3: enable usage of DAT3 pin as HW card detect From: Marcin Wojtas To: Jisheng Zhang Cc: linux-kernel@vger.kernel.org, "linux-arm-kernel@lists.infradead.org" , "linux-mmc@vger.kernel.org" , Thomas Petazzoni , Andrew Lunn , Ulf Hansson , Jason Cooper , Tawfik Bayouk , Grzegorz Jaszczyk , nadavh@marvell.com, Lior Amsalem , =?UTF-8?Q?Gregory_Cl=C3=A9ment?= , Sebastian Hesselbarth Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Jisheng, >> >> When using DAT3-based detection Armada 38x SDIO IP expects its internal >> clock to be always on, which had to be ensured twofold: > > What happen if runtime suspend disables its core clk and axi clk? I guess > dat3-based detection isn't compatible with runtime pm. If so, do we also > need to disable runtime pm in probe function? Is runtime resume supposed to be triggered by card detection? Is there a way to manually trigger runtime suspend and resume of sdhci? Anyway coreclk is not a problem, as it's not used by A38x. > >> - Each time controller is reset by updating appropriate registers. On the >> occasion of adding new register @0x104, register @0x100 name is modified >> in order to the be aligned with Armada 38x documentation. >> - Leaving the clock enabled despite power-down. For this purpose a new >> quirk had to be added to SDHCI subsystem - SDHCI_QUIRK2_KEEP_INT_CLK_ON. > > As seen from other mails, Ulf calls for no more quirks... > Ok, I'll try to find another solution. Best regards, Marcin