Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
	Guneshwor Singh <guneshwor.o.singh@intel.com>,
	liam.r.girdwood@linux.intel.com,
	Patches Audio <patches.audio@intel.com>,
	Mark Brown <broonie@kernel.org>,
	Vunny Sodhi <vunnyx.sodhi@intel.com>
Subject: Re: [PATCH v2 1/4] ASoC: Intel: Skylake: Add debugfs support
Date: Thu, 29 Jun 2017 15:46:14 +0530	[thread overview]
Message-ID: <20170629101614.GI19154@localhost> (raw)
In-Reply-To: <4d9ce5ac-ae35-7c38-cace-e482b222e82a@sakamocchi.jp>

On Thu, Jun 29, 2017 at 05:16:05PM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> On Jun 29 2017 16:56, Vinod Koul wrote:
> > On Thu, Jun 29, 2017 at 04:43:38PM +0900, Takashi Sakamoto wrote:
> >> Hi,
> > 
> > Hi Takashi,
> > 
> >>> +struct skl_debug *skl_debugfs_init(struct skl *skl)
> >>> +{
> >>> +	struct skl_debug *d;
> >>> +
> >>> +	d = devm_kzalloc(&skl->pci->dev, sizeof(*d), GFP_KERNEL);
> >>> +	if (!d)
> >>> +		return NULL;
> >>> +
> >>> +	/* create the root dir first */
> >>> +	d->fs = debugfs_create_dir(KBUILD_MODNAME, NULL);
> >>
> >> ALSA SoC part has a debugfs support. It adds "asoc" node into debugfs
> >> mount point and export "snd_soc_debugfs_root" symbol as a root node. I
> >> think it a better idea to collect relevant nodes into the place, rather
> >> than dispersing them.
> > 
> > Yes we can use that, but then this is very driver specific info, does it
> > make sense to keep under framework 'asoc' ?
> 
> It makes sense in a point that it's a part of drivers in ALSA SoC part.

Yes that is a very valid point indeed

> > If we decide to use that, a more intuitive place might be "platform" rather
> > than "asoc" which creates dependency on sound card creation which might happen
> > much later.
> >
> > for debug, I would like to avoid complexity and go with simple device
> > approach...
> 
> I have no objection to your opinion. I like an idea "keep it short and
> simple". If no issues I had, I would select the same direction. However,
> space on debugfs is one of shared resources on system. If being polite
> to the other subsystems, it's better to avoid scattering it, in my opinion.
> 
> For naming scheme or directory structure inner the node, please have
> enough discussion with the other developers for ALSA SoC part. But in
> this timing, it would be acceptable to add your node just under "asoc"
> node. The arrangement could be done later.

Okay we rechecked and we could use component.debugfs_root which would point
to component directory which seems more apt, so we will use that instead of
root 'asoc'

Thanks for the suggestions, will send v3 shortly

-- 
~Vinod

  reply	other threads:[~2017-06-29 10:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29  6:56 [v2 0/4] Add debugfs support for skylake driver Guneshwor Singh
2017-06-29  6:56 ` [PATCH v2 1/4] ASoC: Intel: Skylake: Add debugfs support Guneshwor Singh
2017-06-29  7:43   ` Takashi Sakamoto
2017-06-29  7:56     ` Vinod Koul
2017-06-29  8:16       ` Takashi Sakamoto
2017-06-29 10:16         ` Vinod Koul [this message]
2017-06-29  6:56 ` [PATCH v2 2/4] ASoC: Intel: Skylake: Debugfs facility to dump module config Guneshwor Singh
2017-06-29  6:56 ` [PATCH v2 3/4] ASoC: Intel: common: Add sram address to sst_addr structure Guneshwor Singh
2017-06-30 12:29   ` Applied "ASoC: Intel: Skylake: Add sram address to sst_addr structure" to the asoc tree Mark Brown
2017-06-29  6:56 ` [PATCH v2 4/4] ASoC: Intel: Skylake: Add support to read firmware registers Guneshwor Singh
2017-07-02 12:12   ` kbuild test robot
2017-07-03  3:27     ` Vinod Koul

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=20170629101614.GI19154@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=guneshwor.o.singh@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=o-takashi@sakamocchi.jp \
    --cc=patches.audio@intel.com \
    --cc=tiwai@suse.de \
    --cc=vunnyx.sodhi@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