From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0DD83C433E0 for ; Wed, 6 Jan 2021 18:57:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id BFC3D2312F for ; Wed, 6 Jan 2021 18:57:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725803AbhAFS5i (ORCPT ); Wed, 6 Jan 2021 13:57:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42650 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725789AbhAFS5h (ORCPT ); Wed, 6 Jan 2021 13:57:37 -0500 Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4475DC06134C for ; Wed, 6 Jan 2021 10:56:57 -0800 (PST) Received: by mail-lf1-x133.google.com with SMTP id o19so8982184lfo.1 for ; Wed, 06 Jan 2021 10:56:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BkbT4Hus3vLbtvqvzcx0OaUHLOYXlMI/hIXqReOZJb8=; b=dt4rZYgQgX/X3Y7Cx9cO61ZXTsYyTgoKymYLrDIS9MhWn3O8v1VOr/jqAGQmcEodQj YjQGjSTGFZBJLAbUEs9hZPI9DnWrVeexaaQ9HgUidlA0sz7XGNHg5sIEfeIYPUkk769Z M+4JREGllltqWYBn8o2oElJu/b+x7MS3ekSRTMTn4UXcf6l7q6BQYUDesWbgh1BxWe5B 8RqlfJnGvVZqTL0zeuJXjlRXnf4WJA3EESjHvUgtOtffWtVs+LIDF07dZArk9mlH6HRY /ALSf2e7U9leMo1WUfv3OebDLKeC8BC1XxKsJvRmif/RHF6URTWQ7AAIPe9CrGDttIpy ewtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BkbT4Hus3vLbtvqvzcx0OaUHLOYXlMI/hIXqReOZJb8=; b=eB8u4OHyLj3b+JAGxFn8W1qEHnTU4myr1Wn/HpGZvb09H/+x8rcXti38bBmEAJZm6b cw/v5/1P8lFWODDAt3mDxtL+jy1jZs1ApCYBLbvPrTJLZ3dQPlNJ03ziYqh9SfD6Si85 HO8X1PrJz8CiupE6PZQajyy79GphkaEe4j/eurtzfq8X+8AYVfb2VoZBx5gRjg55rHo2 CsHL8f8ya6O0ZOK9UaQ7zghoFo+Ri2YKxVH0U0q06Cj+FNNHQA+aFAFxa5jfcsoNtN3N iiOK4PnxkMZhlRSJJCYfOS0gjmrszb/iLOjBAL06WhVbu0lTMMdNIXORC3yfWYvCKPtY m/oQ== X-Gm-Message-State: AOAM5324DEV8L/kfvPCRHBJrV8RI0A1/ophElFEyGmv86MSI8y3W5bwK fd0PHJQ7azT49IgEOQ/f+Dk18JQH7DjgGu9VadU= X-Google-Smtp-Source: ABdhPJzT6CDI1ihHDV42x1k7PzDLUIJDHeJEmx05Fil+13kZnMYtnJhKQSKYPZjNsjD5pEtNKzScJvR7SNKi9oHsTcU= X-Received: by 2002:a2e:bc05:: with SMTP id b5mr2618412ljf.444.1609959415759; Wed, 06 Jan 2021 10:56:55 -0800 (PST) MIME-Version: 1.0 References: <20200205092653.GB2737@bogon.m.sigxcpu.org> <5ad361195f2e191484c8a231be0f5a07@akkea.ca> In-Reply-To: From: Fabio Estevam Date: Wed, 6 Jan 2021 15:56:43 -0300 Message-ID: Subject: Re: sdhci timeout on imx8mq To: Lucas Stach Cc: BOUGH CHEN , Angus Ainslie , Leonard Crestez , Peng Fan , Abel Vesa , Stephen Boyd , Michael Turquette , Ulf Hansson , =?UTF-8?Q?Guido_G=C3=BCnther?= , linux-mmc , Adrian Hunter , dl-linux-imx , Sascha Hauer , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-mmc@vger.kernel.org Hi Lucas, On Tue, Jan 5, 2021 at 12:06 PM Lucas Stach wrote: > The reference manual states about this situation: "For any clock, its > source must be left on when it is kept on. Behavior is undefined if > this rule is violated." > And it seems this is exactly what's happening here: some kind of glitch > is introduced in the nand_usdhc_bus clock, which prevents the SDHCI > controller from working, even though the clock branch is properly > enabled later on. On my system the SDHCI timeout and following runtime > suspend/resume cycle on the nand_usdhc_bus clock seem to get it back > into a working state. I think your analysis is correct and I recall helping a customer with a similar issue: https://community.nxp.com/t5/i-MX-Processors/External-clock-that-provide-root-clock-for-SAI3-and-SPDIF/m-p/1019834 Regards, Fabio Estevam From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,DKIM_VALID,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B37C7C433E6 for ; Wed, 6 Jan 2021 18:59:34 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 5B5EB2312F for ; Wed, 6 Jan 2021 18:59:34 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5B5EB2312F Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From:In-Reply-To: References:MIME-Version:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=vK0TQ4ADPYExBwsblgGJ6b3grZisRHr9Qy2ES36lu+0=; b=idUrtStFZ72pCspPeB2TScX9k upE3womY68md6Fo+z6QqIMNpRadORPrj6hRWg1ULZaI52+P0lVUPOPKjxc1af8m7Uhk4K8HLJQVej v9Y4a0ZETTqSsAu30C5bW0WuhcdpqNZoGt0/OAzmfVJkgkWBv843rJiBmGaoCXSonVuQxei/mTLjd +z7HLdEsWO5ESK0ai9ZbDg6hHjq+8zXeDVLHdrd8X4PzmO6gqYPAPH4lwOgM5P0LTqvFk6QAN3rFO WrktAcj8EfX1sRpf4HgLpALyB/rpKgx5nhTu/v4I+IJPFH3VZPSycBTJKJ6KNWGc6sWC4zyh+6zyl l9px0SCcg==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kxDzU-0004Su-HT; Wed, 06 Jan 2021 18:57:04 +0000 Received: from mail-lf1-x134.google.com ([2a00:1450:4864:20::134]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kxDzQ-0004S5-2d for linux-arm-kernel@lists.infradead.org; Wed, 06 Jan 2021 18:57:01 +0000 Received: by mail-lf1-x134.google.com with SMTP id l11so9002395lfg.0 for ; Wed, 06 Jan 2021 10:56:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BkbT4Hus3vLbtvqvzcx0OaUHLOYXlMI/hIXqReOZJb8=; b=dt4rZYgQgX/X3Y7Cx9cO61ZXTsYyTgoKymYLrDIS9MhWn3O8v1VOr/jqAGQmcEodQj YjQGjSTGFZBJLAbUEs9hZPI9DnWrVeexaaQ9HgUidlA0sz7XGNHg5sIEfeIYPUkk769Z M+4JREGllltqWYBn8o2oElJu/b+x7MS3ekSRTMTn4UXcf6l7q6BQYUDesWbgh1BxWe5B 8RqlfJnGvVZqTL0zeuJXjlRXnf4WJA3EESjHvUgtOtffWtVs+LIDF07dZArk9mlH6HRY /ALSf2e7U9leMo1WUfv3OebDLKeC8BC1XxKsJvRmif/RHF6URTWQ7AAIPe9CrGDttIpy ewtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BkbT4Hus3vLbtvqvzcx0OaUHLOYXlMI/hIXqReOZJb8=; b=kK+r9VS/91pLxfITMBqEhBw/ds8TERJArQdZHz/SWNCiL8ib5DJ35NO6I61Rc0ozZd HXyuhBgeU0WGSVpE1B8ya78Ke4VQ/udiS0+oHtFHHuWoeIAt8WaxjEnh6L0KLMmetiGH gt5lEcc+YBN9KnATHnmA4t3Cl5pJQnEQDbDZ4UKOqXsRdlabLa43qaFBZJQKiCHX0AnO T2id5O9r86CSdD6teEGruD3W7HpTvQmW6LWypccruPA/CcOuEd6aPUwd2x8N3muPis7C PBfSa+DwiFd8cZALJEdHO4yXXdjrUldX7jlOY1JExRTjL/AswS+Y6oY8ShdfzcXfT0hI kbuw== X-Gm-Message-State: AOAM532a6a9h91kzoCREcmoi9swZaD59lrv/ZO/03e2Ow6g0khmZj80z 5/Soz3rojFDUDfGepMbpsbttZUZDRSJVqI8betI= X-Google-Smtp-Source: ABdhPJzT6CDI1ihHDV42x1k7PzDLUIJDHeJEmx05Fil+13kZnMYtnJhKQSKYPZjNsjD5pEtNKzScJvR7SNKi9oHsTcU= X-Received: by 2002:a2e:bc05:: with SMTP id b5mr2618412ljf.444.1609959415759; Wed, 06 Jan 2021 10:56:55 -0800 (PST) MIME-Version: 1.0 References: <20200205092653.GB2737@bogon.m.sigxcpu.org> <5ad361195f2e191484c8a231be0f5a07@akkea.ca> In-Reply-To: From: Fabio Estevam Date: Wed, 6 Jan 2021 15:56:43 -0300 Message-ID: Subject: Re: sdhci timeout on imx8mq To: Lucas Stach X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210106_135700_129933_C50A19B0 X-CRM114-Status: GOOD ( 12.70 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Peng Fan , Abel Vesa , Stephen Boyd , Michael Turquette , Angus Ainslie , linux-mmc , Ulf Hansson , BOUGH CHEN , Adrian Hunter , dl-linux-imx , Sascha Hauer , Leonard Crestez , =?UTF-8?Q?Guido_G=C3=BCnther?= , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Lucas, On Tue, Jan 5, 2021 at 12:06 PM Lucas Stach wrote: > The reference manual states about this situation: "For any clock, its > source must be left on when it is kept on. Behavior is undefined if > this rule is violated." > And it seems this is exactly what's happening here: some kind of glitch > is introduced in the nand_usdhc_bus clock, which prevents the SDHCI > controller from working, even though the clock branch is properly > enabled later on. On my system the SDHCI timeout and following runtime > suspend/resume cycle on the nand_usdhc_bus clock seem to get it back > into a working state. I think your analysis is correct and I recall helping a customer with a similar issue: https://community.nxp.com/t5/i-MX-Processors/External-clock-that-provide-root-clock-for-SAI3-and-SPDIF/m-p/1019834 Regards, Fabio Estevam _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel