From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751978AbcFWBfo (ORCPT ); Wed, 22 Jun 2016 21:35:44 -0400 Received: from lucky1.263xmail.com ([211.157.147.131]:45204 "EHLO lucky1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751814AbcFWBfm (ORCPT ); Wed, 22 Jun 2016 21:35:42 -0400 X-263anti-spam: KSV:0; X-MAIL-GRAY: 1 X-MAIL-DELIVERY: 0 X-KSVirus-check: 0 X-ABS-CHECKED: 4 X-ADDR-CHECKED: 0 X-RL-SENDER: shawn.lin@rock-chips.com X-FST-TO: devicetree@vger.kernel.org X-SENDER-IP: 58.22.7.114 X-LOGIN-NAME: shawn.lin@rock-chips.com X-UNIQUE-TAG: <7e713acf6ff150d1fac739a7343d7d30> X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Subject: Re: [RFC PATCH 0/4] Introduce new caps to improve the card's init sequence To: Ulf Hansson References: <1465373996-2485-1-git-send-email-shawn.lin@rock-chips.com> Cc: shawn.lin@rock-chips.com, Jaehoon Chung , Rob Herring , linux-mmc , "linux-kernel@vger.kernel.org" , Doug Anderson , "open list:ARM/Rockchip SoC..." , "devicetree@vger.kernel.org" From: Shawn Lin Message-ID: Date: Thu, 23 Jun 2016 09:35:33 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 在 2016/6/22 20:37, Ulf Hansson 写道: > On 8 June 2016 at 10:19, Shawn Lin wrote: >> >> Hi all, >> >> This patchset is gonna improve the card's init sequence >> by exposing some caps to DT. >> >> The basic idea is to skip sending specific init cmd inspired >> by Carlo Caione's commit[0]. >> >> To make it possible, I firstly expose Carlo's MMC_CAP2_NO_SDIO >> to DT and extend two new caps for similar usage of sd and mmc. >> We probably need it because for most of the boards, each of the >> slots should have a specific function when designed. It's impossible >> for one slot which can either to be used as eMMC or a SD card for a >> given board. The same for SDIO case. >> >> We could have two ways to improve it >> A) Skip sending specific commands if knowing we don't support >> the specific card type. >> B) Allow sending specific commands if knowing we do support >> the specific card type. >> >> A) and B) shouldn't have difference, but I take A) as the final >> one as it looks more consistent with Carlo's way, which does not >> seem to break anything as possible. >> >> The only roadblock for this patchset to be landed should be the >> improvement we gain from it. Theoretically sdio-card doesn't get >> improvment as it's already in the first place to be attached. >> But considering the sd and (e)MMC case, we should gain more benifit >> from it. >> >> From the test, we can save nearly 2ms for attaching emmc against the >> original 8ms. And we gain more than 30us improvement for sd card for >> each insert. >> >> [0]: http://permalink.gmane.org/gmane.linux.kernel.mmc/34774 >> >> >> >> Shawn Lin (4): >> Documentation: mmc: add description for new caps >> mmc: core: expose MMC_CAP2_NO_SDIO to dt-binding >> mmc: core: add cap-no-sd and cap-no-mmc properties >> mmc: core: improve initialization flow >> > > I would prefer that you restructure this series a bit. I will do it and I think Doug was asking we to drop the "cap-" prefix which I think need to be clarified before sending non-RFC one. :) > > Start by adding each new MMC_CAP2* separately and without involving > the DT parsing. > > Make the DT documentation patch come after the above, and add a new > separate patch which exposes the caps to device tree. > > In that way, I can pick up the non DT parts and wait for Rob's > ack/nack of the DT bindings. > > Kind regards > Uffe > >> Documentation/devicetree/bindings/mmc/mmc.txt | 3 +++ >> drivers/mmc/core/core.c | 10 +++++----- >> drivers/mmc/core/host.c | 6 ++++++ >> include/linux/mmc/host.h | 2 ++ >> 4 files changed, 16 insertions(+), 5 deletions(-) >> >> -- >> 2.3.7 >> >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > > -- Best Regards Shawn Lin