From: kernel test robot <lkp@intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [freescale-fslc:pr/639 178/24603] sound/soc/fsl/fsl_esai_client.c:85:5: warning: no previous prototype for 'fsl_esai_client_pcm_trigger'
Date: Fri, 1 Sep 2023 09:39:24 +0800 [thread overview]
Message-ID: <202309010934.tlLILvnI-lkp@intel.com> (raw)
Hi Shengjiu,
FYI, the error/warning still remains.
tree: https://github.com/Freescale/linux-fslc pr/639
head: 857fbf7cebaba3b1ffccc558deee1d13ac0e11d7
commit: c03a789d0a2388b61aeabe8b5bad7935e2951497 [178/24603] MLK-24612-1: ASoC: fsl_esai: Add esai client driver
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20230901/202309010934.tlLILvnI-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230901/202309010934.tlLILvnI-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309010934.tlLILvnI-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/fsl/fsl_esai_client.c:85:5: warning: no previous prototype for 'fsl_esai_client_pcm_trigger' [-Wmissing-prototypes]
85 | int fsl_esai_client_pcm_trigger(struct snd_soc_component *component,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/fsl_esai_client_pcm_trigger +85 sound/soc/fsl/fsl_esai_client.c
84
> 85 int fsl_esai_client_pcm_trigger(struct snd_soc_component *component,
86 struct snd_pcm_substream *substream, int cmd)
87 {
88 struct snd_soc_pcm_runtime *rtd = substream->private_data;
89 struct snd_soc_dai *cpu_dai = asoc_rtd_to_cpu(rtd, 0);
90 struct fsl_esai_client *client = snd_soc_dai_get_drvdata(cpu_dai);
91 bool tx = substream->stream == SNDRV_PCM_STREAM_PLAYBACK;
92
93 switch (cmd) {
94 case SNDRV_PCM_TRIGGER_START:
95 case SNDRV_PCM_TRIGGER_RESUME:
96 case SNDRV_PCM_TRIGGER_PAUSE_RELEASE:
97 /* These info are needed by esai mix*/
98 client->dma[tx].buffer_bytes = snd_pcm_lib_buffer_bytes(substream);
99 client->dma[tx].period_bytes = snd_pcm_lib_period_bytes(substream);
100 client->dma[tx].buffer_offset = 0;
101 client->dma[tx].active = true;
102 break;
103 case SNDRV_PCM_TRIGGER_SUSPEND:
104 case SNDRV_PCM_TRIGGER_PAUSE_PUSH:
105 case SNDRV_PCM_TRIGGER_STOP:
106 client->dma[tx].active = false;
107 break;
108 default:
109 return -EINVAL;
110 }
111
112 return 0;
113 }
114
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-01 1:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202309010934.tlLILvnI-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=otavio@ossystems.com.br \
/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.