Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754227AbcCXNav (ORCPT ); Thu, 24 Mar 2016 09:30:51 -0400 Received: from smtp.math.uni-bielefeld.de ([129.70.45.10]:50566 "EHLO smtp.math.uni-bielefeld.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751842AbcCXNam (ORCPT ); Thu, 24 Mar 2016 09:30:42 -0400 Subject: Re: Warnings for invalid VDD (sdhci-s3c) To: Krzysztof Kozlowski , Ulf Hansson , Adrian Hunter , "Ivan T. Ivanov" , ludovic.desroches@atmel.com, Jisheng Zhang , linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org, Jaehoon Chung References: From: Tobias Jakobi Message-ID: <56F3EBF4.400@math.uni-bielefeld.de> Date: Thu, 24 Mar 2016 14:30:28 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2974 Lines: 77 Hello Krzysztof, I'm seeing a similar problem on my Odroid-X2. I've fixed the issue by letting sdhci_set_power() (in drivers/mmc/host/sdhci.c) handle MMC_VDD_28_29 as well. I'm not sure though what's the rationale behind only handling certain MMC_VDD_x values in the switch statement. With best wishes, Tobias Krzysztof Kozlowski wrote: > Hi, > > After 918f4cbd4340 ("mmc: sdhci: restore behavior when setting VDD via > external regulator") On Trats2 board I see warnings for invalid VDD > value (2.8V): > > [ 3.119656] ------------[ cut here ]------------ > [ 3.119666] WARNING: CPU: 3 PID: 90 at > ../drivers/mmc/host/sdhci.c:1234 sdhci_do_set_ios+0x4cc/0x5e0 > [ 3.119669] mmc0: Invalid vdd 0x10 > [ 3.119673] Modules linked in: > [ 3.119679] CPU: 3 PID: 90 Comm: kworker/3:1 Tainted: G W > 4.5.0-next-20160324 #23 > [ 3.119681] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree) > [ 3.119690] Workqueue: events_freezable mmc_rescan > [ 3.119708] [] (unwind_backtrace) from [] > (show_stack+0x10/0x14) > [ 3.119719] [] (show_stack) from [] > (dump_stack+0x88/0x9c) > [ 3.119728] [] (dump_stack) from [] (__warn+0xe8/0x100) > [ 3.119734] [] (__warn) from [] > (warn_slowpath_fmt+0x38/0x48) > [ 3.119740] [] (warn_slowpath_fmt) from [] > (sdhci_do_set_ios+0x4cc/0x5e0) > [ 3.119748] [] (sdhci_do_set_ios) from [] > (sdhci_runtime_resume_host+0x60/0x114) > [ 3.119758] [] (sdhci_runtime_resume_host) from > [] (__rpm_callback+0x2c/0x60) > [ 3.119767] [] (__rpm_callback) from [] > (rpm_callback+0x20/0x80) > [ 3.119773] [] (rpm_callback) from [] > (rpm_resume+0x36c/0x558) > [ 3.119780] [] (rpm_resume) from [] > (__pm_runtime_resume+0x4c/0x64) > [ 3.119788] [] (__pm_runtime_resume) from [] > (__mmc_claim_host+0x170/0x1b0) > [ 3.119795] [] (__mmc_claim_host) from [] > (mmc_rescan+0x54/0x348) > [ 3.119807] [] (mmc_rescan) from [] > (process_one_work+0x120/0x3f4) > [ 3.119815] [] (process_one_work) from [] > (worker_thread+0x38/0x554) > [ 3.119823] [] (worker_thread) from [] > (kthread+0xdc/0xf4) > [ 3.119831] [] (kthread) from [] > (ret_from_fork+0x14/0x3c) > [ 3.119834] ---[ end trace a22d652aa3276886 ]--- > > The device seems to work correctly but I suppose the patch still has > an effect - the mmc_regulator_set_ocr() is not called. > > Any ideas for fixing this? > > The board is Trats2 (Exynos4412). > > Best regards, > Krzysztof > -- > To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >