All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.com,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	hdegoede@redhat.com, broonie@kernel.org,
	Amadeusz SX2awiX4ski <amadeuszx.slawinski@linux.intel.com>
Subject: Re: [PATCH 1/5] ALSA: hda: Drop device-argument in NHLT functions
Date: Mon, 18 Oct 2021 14:01:55 +0200	[thread overview]
Message-ID: <s5h35oy5yoc.wl-tiwai@suse.de> (raw)
In-Reply-To: <002bde61-eeea-a1d7-2392-488c5359ce97@intel.com>

On Mon, 18 Oct 2021 11:07:15 +0200,
Cezary Rojewski wrote:
> 
> 
> 
> On 2021-10-18 10:25 AM, Takashi Iwai wrote:
> > On Mon, 18 Oct 2021 10:08:30 +0200,
> > Cezary Rojewski wrote:
> >>
> >> On 2021-10-17 9:52 AM, Takashi Iwai wrote:
> >>> On Fri, 15 Oct 2021 18:42:33 +0200,
> >>> Pierre-Louis Bossart wrote:
> >>>> On 10/15/21 11:40 AM, Cezary Rojewski wrote:
> >>>>> From: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
> >>>>>
> >>>>> ACPI is device independent, so printing warnings using device functions
> >>>>> is misleading. Replace dev_xxx() with pr_xxx() and remove now
> >>>>> unnecessary argument.
> >>>>
> >>>> the routines in sound/hda/intel-nhtl.c are called from a specific PCI
> >>>> device, why would you remove that information?
> >>>>
> >>>> This makes no sense to me.
> >>>
> >>> Right, otherwise this change would confuse user, too; they'll be
> >>> clueless about who triggers it.
> >>>
> >>> It's OK to change to pr_*(), but then it should have more information
> >>> that can be easily identified and understood what user should do.
> >>
> >> Isn't the answer as to 'who' used it obvious, though? NHLT is used for
> >> I2S and DMIC endpoints only, so the question is 'limited' in the first
> >> place. And then, you cannot have several Intel ADSP drivers running
> >> simultaneously.
> >
> > Well, it's not about you or devs -- those must know which driver is
> > relevant very well, of course.  Instead, the problem is for *all*
> > others who read the message.
> >
> > IOW, which user would know and think "hey, it's a NHLT thingy that
> > must be ASoC xxx driver that spewed" only from the text snippet "NHLT
> > table not found"?  That's way too much expectation.  Some more
> > guidance is needed in the error message.  The dev_*() variant gave at
> > least the device names that can help guessing the relevant driver
> > easily.
> >
> >> Also, logs found ACPI-table interface are device-less so this patch
> >> makes NHLT interface look more ACPI-generic alike.
> >
> > The conversion itself is no problem, but the lost information is the
> > problem.
> 
> Well, most invocations that end in error will cause stack of
> error-logs (dev_xxx()) in the parent driver. NHLT reads:
> Non-HDAudio-Link-Table. The name itself points reader towards
> sound/hda already.

But then how dropping the device information would improve things at
all?  It rather cuts off the link between that message and the later
one.

> I understand that not everyone will google "NHLT"
> and such but then there are ton of kernel messages which won't guide
> reader by the hand anyway.

This can't be an excuse, we don't have to follow that anti pattern :)

> "NHLT table not found" is configuration problem, not a driver
> problem. Mixing BIOS/config problems with driver ones leads to
> incorrect conclusions what we want to avoid.

The configuration itself makes sense only if it's in actual use,
i.e. the problem is always tied with the driver.

So, if any, you can put more information around the message mentioning
that it's the configuration problem and what to do for users,
e.g. check your BIOS, etc.  *That* would be the improvement.


Takashi

  reply	other threads:[~2021-10-18 12:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 16:40 [PATCH 0/5] ALSA: hda: New NHLT functions and cleanup Cezary Rojewski
2021-10-15 16:40 ` [PATCH 1/5] ALSA: hda: Drop device-argument in NHLT functions Cezary Rojewski
2021-10-15 16:42   ` Pierre-Louis Bossart
2021-10-17  7:52     ` Takashi Iwai
2021-10-18  8:08       ` Cezary Rojewski
2021-10-18  8:25         ` Takashi Iwai
2021-10-18  9:07           ` Cezary Rojewski
2021-10-18 12:01             ` Takashi Iwai [this message]
2021-10-18 12:18               ` Cezary Rojewski
2021-10-15 16:40 ` [PATCH 2/5] ALSA: hda: Follow ACPI convention in NHLT struct naming Cezary Rojewski
2021-10-15 16:40 ` [PATCH 3/5] ALSA: hda: Fill gaps in NHLT endpoint-interface Cezary Rojewski
2021-10-16  3:21   ` kernel test robot
2021-10-16  3:21     ` kernel test robot
2021-10-16  3:21     ` kernel test robot
2021-10-15 16:40 ` [PATCH 4/5] ALSA: hda: Simplify DMIC-in-NHLT check Cezary Rojewski
2021-10-16  5:09   ` kernel test robot
2021-10-16  5:09     ` kernel test robot
2021-10-16  5:09     ` kernel test robot
2021-10-15 16:40 ` [PATCH 5/5] ASoC: Intel: Skylake: Use NHLT API to search for blob Cezary Rojewski
2021-10-15 16:42   ` Mark Brown

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=s5h35oy5yoc.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.