Received: by 10.213.65.68 with SMTP id h4csp153950imn; Thu, 15 Mar 2018 21:22:07 -0700 (PDT) X-Google-Smtp-Source: AG47ELsXdFfo5JswrRD/E68o8rhHyc1zqNuSIVpwRGh1ycja5WU4Ans7ntTy/TFHHhPgzTnWhqRP X-Received: by 10.98.174.16 with SMTP id q16mr360309pff.92.1521174127218; Thu, 15 Mar 2018 21:22:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521174127; cv=none; d=google.com; s=arc-20160816; b=kD7j3NIt+yfz0fzY4mwPDtxQl2oL4/VYfmLi2oNnl5uHugo5gyOqGavv233c3dnuR4 pyHb7yDZhOf+0xjzazMjRZZruiqxget+8HtrVTVMOCfGP3I5Ee8CzO70tYpnehUl54QX YprqZYiKdgxdha09/oP3EihzJJPjO4riBEmcsGhuRjJwzc66O9C2qel5g7TaoLKV8SIB A6fBayuNkYsiD+UiJzMdBY6KMluYOVCd6IEAMYRgtvxizpPvX1LWxXyIQnfNoOgiurMd v+GF2hPNp1yUPVceVrY21tAXrVEqJgiZOAscwSRxr9zMSXE9lms6sPLQozX5K5/GRRBi QKww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=9kQAOOI7krVbUy0y5CBITWDqURMiiQV97gl4l6r4wMY=; b=zalSVf8mNHnFZGv1KHgA2lkrS9xwiMVKHG4CX2vA5aod5EY4l5lqDLSsJQcMIHkt+7 uQn6MjjI2uNAhTy71vdMx5MFFmEetA6PxNh6V8qwIfMuJwugc/9hwSCyCNREqUhJoA0c v/Q5mQw4ru2bkh6GBy33ug+nVs85caJ4c72YTaK6yAR2Icw8YNBjzMymLakrhkqZdmzT R9TSPRucRhmbdM17Mdd90MmnYuj99yA2zw5xW8O/+3hBSgcqsvJpLB52d0GWIQOOv8Vf QPqhz6yybHfm5zzijCMTdlMse8FE2H7kbXtvSzd4MDw/KmcKZLRGqHh+iaFVQoue7rbV mlIg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 14si4441820pga.613.2018.03.15.21.21.50; Thu, 15 Mar 2018 21:22:07 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750847AbeCPEUw (ORCPT + 99 others); Fri, 16 Mar 2018 00:20:52 -0400 Received: from relay1.mentorg.com ([192.94.38.131]:60942 "EHLO relay1.mentorg.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750749AbeCPEUv (ORCPT ); Fri, 16 Mar 2018 00:20:51 -0400 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=svr-ies-mbx-01.mgc.mentorg.com) by relay1.mentorg.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-SHA384:256) id 1ewgrI-0005nN-Kn from Harish_Kandiga@mentor.com ; Thu, 15 Mar 2018 21:20:48 -0700 Received: from [10.0.2.15] (137.202.0.87) by svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 16 Mar 2018 04:20:43 +0000 Subject: Re: [PATCH v10] mmc: Export host capabilities to debugfs. To: Ulf Hansson , Andy Shevchenko CC: Linus Walleij , Adrian Hunter , Shawn Lin , , "linux-mmc@vger.kernel.org" , Linux Kernel Mailing List , Vladimir Zapolskiy References: <1520917812-20047-1-git-send-email-harish_kandiga@mentor.com> <1521109575.10722.654.camel@linux.intel.com> From: Harish Jenny K N Message-ID: Date: Fri, 16 Mar 2018 09:50:40 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Content-Language: en-US X-Originating-IP: [137.202.0.87] X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 15 March 2018 05:59 PM, Ulf Hansson wrote: > On 15 March 2018 at 11:26, Andy Shevchenko > wrote: >> On Thu, 2018-03-15 at 11:12 +0100, Ulf Hansson wrote: >>> On 13 March 2018 at 06:10, Harish Jenny K N >>> wrote: >>>> >>> Honestly, I don't like this, but maybe other people do, then I am fine >>> with this approach. >>> >>> If were to decide, I would just rather print the caps field in a >>> hexadecimal bit form and leave the translation to the user. >> A compromise would be to print both: >> >> 0xHHHHHHHH\n >> Description of each enabled field, one per line >> >> >> Another format would be: >> >> Bit XX: Description of a field > If we were to print the description, there is no point in printing the > bits in hex. Or is it? Yes. I also do not see the use of printing hex value if we are printing the description. > > As I said, if you and other folkz thinks this is valuable, then I am > fine as well. Just saying, it's not my preferred option. > > I just want to inform that the idea of printing the description came after discussion in https://www.spinics.net/lists/linux-mmc/msg48246.html, where it was decided adding utility in mmc-utils was not going to work ( reason:  We may very well be changing the bit offsets for the caps and caps2 in the mmc kernel header, keeping a copy of them is not a good idea. It's just a matter of *when* it will break). On Thu, 2018-03-15 at 11:12 +0100, Ulf Hansson wrote: > If were to decide, I would just rather print the caps field in a hexadecimal bit form and leave the translation to the user. I think translation becomes difficult for the above reason and hence I would prefer printing the description. Note: Printing values in Hex was the original idea and it is also available in https://www.spinics.net/lists/linux-mmc/msg48213.html just in case if it is required. Thanks & Regards, Harish Jenny K N