From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Shevchenko Subject: Re: [PATCH v10] mmc: Export host capabilities to debugfs. Date: Thu, 15 Mar 2018 15:02:08 +0200 Message-ID: <1521118928.10722.658.camel@linux.intel.com> References: <1520917812-20047-1-git-send-email-harish_kandiga@mentor.com> <1521109575.10722.654.camel@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Ulf Hansson Cc: Harish Jenny K N , Linus Walleij , Adrian Hunter , Shawn Lin , avri.altman@wdc.com, "linux-mmc@vger.kernel.org" , Linux Kernel Mailing List , Vladimir Zapolskiy List-Id: linux-mmc@vger.kernel.org On Thu, 2018-03-15 at 13:29 +0100, 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 > > .com > > > > 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? It is helpful for scripting (since it's debugfs, under scripting I mean something rather for test suites than for actual use). > 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. -- Andy Shevchenko Intel Finland Oy