X86 platform drivers
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>
Cc: platform-driver-x86@vger.kernel.org,
	Darren Hart <dvhart@infradead.org>,
	Vishwanath Somayaji <vishwanath.somayaji@intel.com>
Subject: Re: [PATCH v1 1/1] platform/x86/intel_pmc_core: Convert to DEFINE_DEBUGFS_ATTRIBUTE
Date: Wed, 29 Jun 2016 15:48:25 +0300	[thread overview]
Message-ID: <1467204505.30123.326.camel@linux.intel.com> (raw)
In-Reply-To: <20160629121604.GA26750@rajaneesh-OptiPlex-9010>

On Wed, 2016-06-29 at 17:46 +0530, Rajneesh Bhardwaj wrote:
> On Wed, Jun 29, 2016 at 02:49:45PM +0300, Andy Shevchenko wrote:
> > On Wed, 2016-06-29 at 13:33 +0530, Rajneesh Bhardwaj wrote:
> > > On Tue, Jun 28, 2016 at 01:05:07PM +0300, Andy Shevchenko wrote:

> > > While this is good for simple attributes i see a potential issue
> > > with
> > > this
> > > approch when we want to display multiple attributes for a single
> > > debugfs
> > > entry.
> > >  We typically use seq_printf in a loop and display multiline
> > > output
> > > for a single debugfs entry. How do we go about the scenarios where
> > > we
> > > want
> > > to display formatted  multiline debug information?
> > 
> > We are talking about abstract case or is it change coming to this
> > very
> > driver?
> > 
> 
> We will be sending few patches for this very driver shortly and one
> such
> feature would require multiline formatted output for a single debugfs 
> entry.

If it touches the same attribute it needs to be seen first before
applying this one.

> 
> Can we have seq_printf for such cases and use DEFINE_DEBUGFS_ATTRIBUTE
> for
> other simple attributes? Doing this might raise some coding style
> consistency 
> concerns though so lets wait to hear  Darren's opinion on this patch.

For the rest we have to see the implementation and decide how to proceed
(since it's a debugfs dedicated for _debugging_) we might change it in
the way we like. Though I don't encourage people to do this. I like
interfaces on which people thought before implementing.

-- 

Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2016-06-29 12:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 17:56 [PATCH v1 1/1] platform/x86/intel_pmc_core: Convert to DEFINE_DEBUGFS_ATTRIBUTE Andy Shevchenko
2016-06-23 15:26 ` Rajneesh Bhardwaj
2016-06-23 16:22   ` Andy Shevchenko
2016-06-28  9:05 ` Rajneesh Bhardwaj
2016-06-28 10:05   ` Andy Shevchenko
2016-06-29  8:03     ` Rajneesh Bhardwaj
2016-06-29 11:49       ` Andy Shevchenko
2016-06-29 12:16         ` Rajneesh Bhardwaj
2016-06-29 12:48           ` Andy Shevchenko [this message]
2016-06-29 13:20             ` Rajneesh Bhardwaj
2016-06-29 13:33               ` Andy Shevchenko
2016-07-01 21:30                 ` Darren Hart
2016-07-04 11:35                 ` Rajneesh Bhardwaj
2016-07-04 12:01                   ` Andy Shevchenko
2016-07-04 12:28                     ` Rajneesh Bhardwaj
2016-07-01 21:28           ` Darren Hart
2016-07-01 21:24     ` Darren Hart
2016-07-02 12:10       ` Andy Shevchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1467204505.30123.326.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=dvhart@infradead.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rajneesh.bhardwaj@intel.com \
    --cc=vishwanath.somayaji@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox