From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: alsa-devel@alsa-project.org, mengdong.lin@linux.intel.com,
Takashi Iwai <tiwai@suse.de>,
mengdong.lin@intel.com, broonie@kernel.org,
subhransu.s.prusty@intel.com
Subject: Re: [PATCH] topology: Include <linux/types.h> in API header file
Date: Fri, 06 Nov 2015 14:37:27 +0000 [thread overview]
Message-ID: <1446820647.2776.19.camel@loki> (raw)
In-Reply-To: <s5hfv0jz200.wl-tiwai@suse.de>
On Fri, 2015-11-06 at 14:33 +0100, Takashi Iwai wrote:
> On Fri, 06 Nov 2015 14:31:18 +0100,
> Vinod Koul wrote:
> >
> > On Fri, Nov 06, 2015 at 01:59:41PM +0100, Takashi Iwai wrote:
> > > On Fri, 06 Nov 2015 13:39:36 +0100,
> > > mengdong.lin@linux.intel.com wrote:
> > > >
> > > > From: Mengdong Lin <mengdong.lin@linux.intel.com>
> > > >
> > > > Include <linux/types.h> in the API header file topology.h
> > > >
> > > > The struct snd_tplg_stream_caps_template has a member "formats"
> > > > of type __le64. So <linux/types.h> is needed.
> > >
> > > We shouldn't use __le64 for user-space API. I couldn't find it in
> > > include/topology.h. Where is it used?
> > >
> > > Of course, it's fine to use it for kernel ABI. But then linux/types.h
> > > is already included in local.h, so it shouldn't be a problem.
> >
> > Our tool threw this error
> >
> > ./local-alsa/include/alsa/topology.h:668:2: error: â__le64â does not name a
> > type
> > __le64 formats; /*!< supported formats SNDRV_PCM_FMTBIT_* */
> >
Can you try the following patch for the userspace header.
From 568f769269122e90fceee605a98a1a526db2b3d4 Mon Sep 17 00:00:00 2001
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Date: Fri, 6 Nov 2015 14:30:36 +0000
Subject: [PATCH] topology: remove little endian type from userspace header.
Use a generic unsigned long long for formats instead of an ABI endian
specific __le64 type.
Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
---
include/topology.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/topology.h b/include/topology.h
index b631871..1a110a2 100644
--- a/include/topology.h
+++ b/include/topology.h
@@ -665,7 +665,7 @@ struct snd_tplg_stream_template {
*/
struct snd_tplg_stream_caps_template {
const char *name; /*!< name of the stream caps */
- __le64 formats; /*!< supported formats SNDRV_PCM_FMTBIT_* */
+ unsigned long long formats; /*!< supported formats SNDRV_PCM_FMTBIT_* */
unsigned int rates; /*!< supported rates SNDRV_PCM_RATE_* */
unsigned int rate_min; /*!< min rate */
unsigned int rate_max; /*!< max rate */
--
2.5.0
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2015-11-06 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 12:39 [PATCH] topology: Include <linux/types.h> in API header file mengdong.lin
2015-11-06 12:59 ` Takashi Iwai
2015-11-06 13:31 ` Vinod Koul
2015-11-06 13:33 ` Takashi Iwai
2015-11-06 14:37 ` Liam Girdwood [this message]
2015-11-06 14:40 ` Takashi Iwai
2015-11-06 14:57 ` Liam Girdwood
2015-11-09 14:04 ` Subhransu S. Prusty
2015-11-10 12:29 ` Vinod Koul
2015-11-10 12:29 ` Jaroslav Kysela
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=1446820647.2776.19.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=mengdong.lin@intel.com \
--cc=mengdong.lin@linux.intel.com \
--cc=subhransu.s.prusty@intel.com \
--cc=tiwai@suse.de \
--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