From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [PATCH V5 01/13] mmc: core: Add mmc_retune_hold_now() Date: Sun, 20 Aug 2017 13:26:31 +0200 Message-ID: References: <1502366898-23691-1-git-send-email-adrian.hunter@intel.com> <1502366898-23691-2-git-send-email-adrian.hunter@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from mail-oi0-f41.google.com ([209.85.218.41]:34870 "EHLO mail-oi0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752721AbdHTL0c (ORCPT ); Sun, 20 Aug 2017 07:26:32 -0400 Received: by mail-oi0-f41.google.com with SMTP id e124so132301779oig.2 for ; Sun, 20 Aug 2017 04:26:32 -0700 (PDT) In-Reply-To: <1502366898-23691-2-git-send-email-adrian.hunter@intel.com> Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Adrian Hunter Cc: Ulf Hansson , linux-mmc , Bough Chen , Alex Lemberg , Mateusz Nowak , Yuliy Izrailov , Jaehoon Chung , Dong Aisheng , Das Asutosh , Zhangfei Gao , Sahitya Tummala , Harjani Ritesh , Venu Byravarasu , Shawn Lin On Thu, Aug 10, 2017 at 2:08 PM, Adrian Hunter wrote: > mmc_return_hold() / mmc_retune_release() are used around a group of > commands to prevent re-tuning between the commands. Re-tuning can still > happen before the first command. In some cases, re-tuning must be > prevented entirely. Add mmc_retune_hold_now() for that purpose. It is > added in preparation for CQE support where it will be used by CQE recovery. > > Signed-off-by: Adrian Hunter Reviewed-by: Linus Walleij > +void mmc_retune_hold_now(struct mmc_host *host) > void mmc_retune_release(struct mmc_host *host) If the only hint we have about how to use these functions is through the commit log we are in trouble, but I would say in this case the function name is kind of half-obvious at least. I think what troubles me is Rusty's API maturity guideline #6 "6. The name tells you how to use it." Yours, Linus Walleij