From: Takashi Iwai <tiwai@suse.de>
To: Vinod Koul <vinod.koul@intel.com>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org,
Jeeja KP <jeeja.kp@intel.com>
Subject: Re: [PATCH v3 3/7] ASoC: hda - adds SoC controller and stream operations
Date: Thu, 30 Apr 2015 11:49:34 +0200 [thread overview]
Message-ID: <s5hy4ladjyp.wl-tiwai@suse.de> (raw)
In-Reply-To: <20150430093504.GL3521@localhost>
At Thu, 30 Apr 2015 15:05:04 +0530,
Vinod Koul wrote:
>
> On Wed, Apr 29, 2015 at 02:26:40PM +0200, Takashi Iwai wrote:
> > At Wed, 29 Apr 2015 01:24:26 +0530,
> > Vinod Koul wrote:
> > >
> > > +struct soc_hdac_stream {
> > > + struct hdac_stream hstream;
> > > + unsigned int decoupled:1;
> > > + void __iomem *pphc_addr; /* processing pipe host stream reg pointer */
> > > + void __iomem *pplc_addr; /* processing pipe link stream reg pointer */
> > > + bool link_locked:1;
> > > + struct snd_pcm_substream *link_substream;
> > > + bool link_prepared;
> >
> > The bit fields should be gathered into the same place so that the
> > struct can be packed better. Also, use bool consistently for bit
> > fields, too.
> Sure, btw should we use bitfields or bool alone. I dont see much reason to
> use bitfields here?
You can use a bit field for boolean instead of unsigned int, e.g.
bool foo:1;
> > > + continue;
> > > +
> > > + if (hlink->lsdiid && (0x1 << addr)) {
> > > + snprintf(hlink->codec[addr],
> > > + sizeof(hlink->codec[addr]),
> > > + "codec#%03x.%d", addr, addr);
> >
> > Does repeating the address twice make sense?
> It doesnt :)
Looking at the codec side, it might be that the ASoC core appends the
dot automatically? If so, we may accept it, of course.
Takashi
next prev parent reply other threads:[~2015-04-30 9:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 19:54 [PATCH v3 0/7] ASoC: intel - add skylake PCM driver Vinod Koul
2015-04-28 19:54 ` [PATCH v3 1/7] ASoC: hda - add soc hda codec driver wrapper Vinod Koul
2015-04-29 11:59 ` Takashi Iwai
2015-05-04 13:12 ` Mark Brown
2015-05-06 3:47 ` Vinod Koul
2015-05-06 12:51 ` Mark Brown
2015-05-06 16:51 ` Vinod Koul
2015-04-28 19:54 ` [PATCH v3 2/7] ALSA: hda - add new HDA registers Vinod Koul
2015-04-29 10:41 ` Takashi Iwai
2015-04-29 10:57 ` Vinod Koul
2015-04-29 12:02 ` Takashi Iwai
2015-04-28 19:54 ` [PATCH v3 3/7] ASoC: hda - adds SoC controller and stream operations Vinod Koul
2015-04-29 12:26 ` Takashi Iwai
2015-04-30 9:35 ` Vinod Koul
2015-04-30 9:49 ` Takashi Iwai [this message]
2015-04-28 19:54 ` [PATCH v3 4/7] ASoC: intel - add Skylake HDA platform driver Vinod Koul
2015-04-29 12:31 ` Takashi Iwai
2015-04-30 9:42 ` Vinod Koul
2015-04-30 9:52 ` Takashi Iwai
2015-04-30 10:39 ` Vinod Koul
2015-04-28 19:54 ` [PATCH v3 5/7] ASoC: intel - add Skylake HDA audio driver Vinod Koul
2015-04-29 12:49 ` Takashi Iwai
2015-04-30 10:11 ` Vinod Koul
2015-04-30 10:18 ` Takashi Iwai
2015-04-28 19:54 ` [PATCH v3 6/7] ASoC: intel - add makefile support for SKL driver Vinod Koul
2015-04-28 19:54 ` [PATCH v3 7/7] ASoC: intel - adds support for decoupled mode in skl driver 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=s5hy4ladjyp.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jeeja.kp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox