All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Vinod Koul <vinod.koul@intel.com>
Cc: alsa-devel@alsa-project.org, patches.audio@intel.com,
	Hardik T Shah <hardik.t.shah@intel.com>,
	Guneshwor Singh <guneshwor.o.singh@intel.com>,
	liam.r.girdwood@linux.intel.com, broonie@kernel.org
Subject: Re: [PATCH 1/3] ALSA - hda: Add support for GTS capability
Date: Mon, 11 Jul 2016 16:06:25 +0200	[thread overview]
Message-ID: <s5ha8hotgke.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160711140732.GH9681@localhost>

On Mon, 11 Jul 2016 16:07:32 +0200,
Vinod Koul wrote:
> 
> > > diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
> > > index 9a0d1445ca5c..b4ebdde59398 100644
> > > --- a/sound/pci/hda/hda_intel.c
> > > +++ b/sound/pci/hda/hda_intel.c
> > > @@ -1649,6 +1649,7 @@ static int azx_first_init(struct azx *chip)
> > >  		return -ENXIO;
> > >  	}
> > >  
> > > +	azx_parse_capabilities(chip);
> > 
> > Is it really safe to call the function no matter which chip?
> 
> I think so, since we read base HDA registers for capablity. For older hw the
> next capablity will not be there.
> 
> But yes I will verify this on older machines.

I checked the spec 1.0 and 1.0a, and there is no definition for the
register offset 0x14.  So, it's likely unsafe to use it
unconditionally.


Takashi

  reply	other threads:[~2016-07-11 14:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 10:13 [PATCH 0/3] ALSA - hda: Add support for link audio time reporting Vinod Koul
2016-07-11 10:13 ` [PATCH 1/3] ALSA - hda: Add support for GTS capability Vinod Koul
2016-07-11 10:22   ` Takashi Iwai
2016-07-11 14:07     ` Vinod Koul
2016-07-11 14:06       ` Takashi Iwai [this message]
2016-07-11 14:22         ` Vinod Koul
2016-07-11 14:17           ` Takashi Iwai
2016-07-11 10:13 ` [PATCH 2/3] ALSA - hda: Add support for link audio time reporting Vinod Koul
2016-07-11 10:32   ` Takashi Iwai
2016-07-11 14:11     ` Vinod Koul
     [not found]   ` <201607111916.R5HdrB76%fengguang.wu@intel.com>
2016-07-15  4:37     ` Vinod Koul
2016-07-15  5:00       ` Takashi Iwai
2016-07-15  5:19         ` Vinod Koul
2016-07-15  5:17           ` Takashi Iwai
2016-07-15  5:39             ` Vinod Koul
2016-07-15  5:39               ` Takashi Iwai
2016-07-15  5:50                 ` Vinod Koul
2016-07-15  5:56                   ` Takashi Iwai
2016-07-11 10:13 ` [PATCH 3/3] ALSA - hda: Fix timestamping documentation Vinod Koul
2016-07-11 10:46   ` Takashi Iwai
2016-07-11 14:12     ` 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=s5ha8hotgke.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=guneshwor.o.singh@intel.com \
    --cc=hardik.t.shah@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@intel.com \
    --cc=vinod.koul@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 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.