public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>,
	anish kumar <yesanishhere@gmail.com>,
	lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
	tiwai@suse.com, Sebastian Fricke <sebastian.fricke@collabora.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-sound@vger.kernel.org
Subject: Re: [RFC PATCH] ALSA: Add debugging guide for audio issues
Date: Thu, 07 Nov 2024 14:40:08 -0700	[thread overview]
Message-ID: <874j4i205j.fsf@trenco.lwn.net> (raw)
In-Reply-To: <274400c3-fd64-4e45-bbd2-319634a09d61@infradead.org>

Randy Dunlap <rdunlap@infradead.org> writes:

> On 11/7/24 12:45 PM, Jonathan Corbet wrote:
>> anish kumar <yesanishhere@gmail.com> writes:
>> 
>>> Add a comprehensive debugging guide for ALSA audio issues, covering
>>> topics from bootup to runtime debugging. This document aims to help
>>> developers diagnose and resolve common audio problems in Linux.
>>>
>>> The guide includes sections on:
>>> - Bootup/bringup issues
>>> - Runtime debugging
>>> - XRUN debugging
>>> - Audio pops and clicks
>>>
>>> This addresses the lack of a centralized debugging resource for ALSA
>>> and should help improve the troubleshooting process for audio drivers.
>>>
>>> Inspired by discussions on LKML:
>>> https://lkml.org/lkml/2024/9/24/392
>>>
>>> Signed-off-by: anish kumar <yesanishhere@gmail.com>
>>> ---
>>>  Documentation/sound/soc/debug.rst | 334 ++++++++++++++++++++++++++++++
>>>  Documentation/sound/soc/index.rst |   1 +
>>>  2 files changed, 335 insertions(+)
>>>  create mode 100644 Documentation/sound/soc/debug.rst
>> 
>> At a first glance, this seems useful.
>> 
>> I was just looking at Sebastian's new debugging documentation:
>> 
>>   https://lore.kernel.org/all/20241028-media_docs_improve_v3-v1-0-2b1b486c223e@collabora.com/
>> 
>> ... so my immediate thought is that this documentation should be
>> coherent and together, rather than scattered though the docs.  Maybe
>> move this to process/debugging and integrate it with his work?
>
> and once again I disagree that these docs should be in Documentation/process/.

OK, I guess I missed that...where do you think we should put them?

jon

  reply	other threads:[~2024-11-07 21:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 20:08 [RFC PATCH] ALSA: Add debugging guide for audio issues anish kumar
2024-11-07 20:45 ` Jonathan Corbet
2024-11-07 21:27   ` Randy Dunlap
2024-11-07 21:40     ` Jonathan Corbet [this message]
2024-11-07 21:54       ` Randy Dunlap
2024-11-07 22:25         ` Jonathan Corbet
2024-11-08  4:53           ` Randy Dunlap
2024-11-11  3:37             ` anish kumar
2024-11-12 20:26             ` Jonathan Corbet
2024-12-06 18:16               ` anish kumar

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=874j4i205j.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=rdunlap@infradead.org \
    --cc=sebastian.fricke@collabora.com \
    --cc=tiwai@suse.com \
    --cc=yesanishhere@gmail.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