Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757493AbcCCLCj (ORCPT ); Thu, 3 Mar 2016 06:02:39 -0500 Received: from mail-sn1nam02on0047.outbound.protection.outlook.com ([104.47.36.47]:47312 "EHLO NAM02-SN1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751572AbcCCLCh (ORCPT ); Thu, 3 Mar 2016 06:02:37 -0500 Authentication-Results: spf=pass (sender IP is 149.199.60.100) smtp.mailfrom=xilinx.com; vger.kernel.org; dkim=none (message not signed) header.d=none;vger.kernel.org; dmarc=bestguesspass action=none header.from=xilinx.com; Subject: Re: [RFC PATCH 4/4] mmc: sdhci-of-arasan: overwrite enhanced strobe callback To: Shawn Lin , Adrian Hunter , Ulf Hansson References: <1456972557-7994-1-git-send-email-shawn.lin@rock-chips.com> <1456972613-8159-1-git-send-email-shawn.lin@rock-chips.com> CC: Michal Simek , , , From: Michal Simek Message-ID: <56D819C4.9080703@xilinx.com> Date: Thu, 3 Mar 2016 12:02:28 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <1456972613-8159-1-git-send-email-shawn.lin@rock-chips.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-TM-AS-Product-Ver: IMSS-7.1.0.1224-8.0.0.1202-22168.006 X-TM-AS-User-Approved-Sender: Yes;Yes X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:149.199.60.100;CTRY:US;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(10009020)(6009001)(2980300002)(438002)(189002)(24454002)(164054003)(199003)(586003)(106466001)(5001960100004)(2906002)(19580395003)(50466002)(1096002)(36386004)(19580405001)(80316001)(23746002)(1220700001)(63266004)(65816999)(54356999)(76176999)(47776003)(87936001)(59896002)(230783001)(6806005)(2950100001)(16796002)(64126003)(92566002)(5008740100001)(50986999)(189998001)(230700001)(36756003)(11100500001)(4326007)(4001350100001)(33656002)(77096005)(5001770100001)(86362001)(65956001)(65806001)(107986001)(217873001);DIR:OUT;SFP:1101;SCL:1;SRVR:BL2NAM02HT214;H:xsj-pvapsmtpgw02;FPR:;SPF:Pass;MLV:sfv;MX:1;A:1;LANG:en; X-MS-Office365-Filtering-Correlation-Id: 937974e0-9449-466c-6343-08d34353530c X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(8251501002);SRVR:BL2NAM02HT214; X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(601004)(2401047)(5005006)(13018025)(13017025)(8121501046)(13015025)(13023025)(13024025)(3002001)(10201501046);SRVR:BL2NAM02HT214;BCL:0;PCL:0;RULEID:;SRVR:BL2NAM02HT214; X-Forefront-PRVS: 0870212862 X-OriginatorOrg: xilinx.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Mar 2016 11:02:34.2320 (UTC) X-MS-Exchange-CrossTenant-Id: 657af505-d5df-48d0-8300-c31994686c5c X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=657af505-d5df-48d0-8300-c31994686c5c;Ip=[149.199.60.100];Helo=[xsj-pvapsmtpgw02] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2NAM02HT214 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1162 Lines: 32 On 3.3.2016 03:36, Shawn Lin wrote: > Currently sdhci-arasan 5.1 can support enhanced strobe function, > but considering the potential requirement in the future for other > version IP, we don't limit it just for "arasan,sdhci-5.1". Add > cap-enhanced-strobe in DT to enable the function if we'r sure our > controller can support it. > > Signed-off-by: Shawn Lin > --- > > drivers/mmc/host/sdhci-of-arasan.c | 20 ++++++++++++++++++++ > 1 file changed, 20 insertions(+) > > diff --git a/drivers/mmc/host/sdhci-of-arasan.c b/drivers/mmc/host/sdhci-of-arasan.c > index 1e4b5e0..31f3494 100644 > --- a/drivers/mmc/host/sdhci-of-arasan.c > +++ b/drivers/mmc/host/sdhci-of-arasan.c > @@ -24,7 +24,9 @@ > #include "sdhci-pltfm.h" > > #define SDHCI_ARASAN_CLK_CTRL_OFFSET 0x2c > +#define SDHCI_ARASAN_VENDOR_REGISTER 0x78 I was checking our register map and we even don't have this register listed as reserved. It looks like that this will be related to certain SoC and different SoC can use it different location. That's why I think this feature and setup should be related to certain SoC specific compatible string. Thanks, Michal