linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Souptick Joarder <jrdr.linux@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Charles Keepax <ckeepax@opensource.cirrus.com>,
	kbuild-all@lists.01.org,
	 Linux Memory Management List <linux-mm@kvack.org>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [linux-next:master 802/5720] sound/soc/samsung/s3c24xx-i2s.c:173:14: error: 'SND_SOC_DAIFMT_BC_CFC' undeclared; did you mean 'SND_SOC_DAIFMT_BC_FC'?
Date: Mon, 27 Jun 2022 07:16:56 +0530	[thread overview]
Message-ID: <CAFqt6za7CyUthX9RqFSy88-+JRebk-QZ9dUtKmaLT6yPtJ_kYg@mail.gmail.com> (raw)
In-Reply-To: <202206270521.Eam09vo4-lkp@intel.com>

On Mon, Jun 27, 2022 at 3:03 AM kernel test robot <lkp@intel.com> wrote:
>
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   2f9cb3d3bd73fc2225d66aa8fcffb632ed3eb235
> commit: 0b491c7c1b2555ef08285fd49a8567f2f9f34ff8 [802/5720] ASoC: samsung: Update to use set_fmt_new callback
> config: arm-randconfig-r003-20220627
> compiler: arm-linux-gnueabi-gcc (GCC) 11.3.0
> reproduce (this is a W=1 build):
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=0b491c7c1b2555ef08285fd49a8567f2f9f34ff8
>         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>         git fetch --no-tags linux-next master
>         git checkout 0b491c7c1b2555ef08285fd49a8567f2f9f34ff8
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash sound/soc/samsung/
>
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>    sound/soc/samsung/s3c24xx-i2s.c: In function 's3c24xx_i2s_set_fmt':
> >> sound/soc/samsung/s3c24xx-i2s.c:173:14: error: 'SND_SOC_DAIFMT_BC_CFC' undeclared (first use in this function); did you mean 'SND_SOC_DAIFMT_BC_FC'?
>      173 |         case SND_SOC_DAIFMT_BC_CFC:
>          |              ^~~~~~~~~~~~~~~~~~~~~
>          |              SND_SOC_DAIFMT_BC_FC
>    sound/soc/samsung/s3c24xx-i2s.c:173:14: note: each undeclared identifier is reported only once for each function it appears in

Looking into linux-next -

 File          Function            Line
0 s3c24xx-i2s.c s3c24xx_i2s_set_fmt 173 case SND_SOC_DAIFMT_BC_CFC:

There is only one reference of SND_SOC_DAIFMT_BC_CFC. Not sure how it
is defined ?
SND_SOC_DAIFMT_BC_CFC is not defined inside soc-dai.h as well.


>
>
> vim +173 sound/soc/samsung/s3c24xx-i2s.c
>
>    160
>    161  /*
>    162   * Set S3C24xx I2S DAI format
>    163   */
>    164  static int s3c24xx_i2s_set_fmt(struct snd_soc_dai *cpu_dai,
>    165                  unsigned int fmt)
>    166  {
>    167          u32 iismod;
>    168
>    169          iismod = readl(s3c24xx_i2s.regs + S3C2410_IISMOD);
>    170          pr_debug("hw_params r: IISMOD: %x \n", iismod);
>    171
>    172          switch (fmt & SND_SOC_DAIFMT_CLOCK_PROVIDER_MASK) {
>  > 173          case SND_SOC_DAIFMT_BC_CFC:
>    174                  iismod |= S3C2410_IISMOD_SLAVE;
>    175                  break;
>    176          case SND_SOC_DAIFMT_BP_FP:
>    177                  iismod &= ~S3C2410_IISMOD_SLAVE;
>    178                  break;
>    179          default:
>    180                  return -EINVAL;
>    181          }
>    182
>    183          switch (fmt & SND_SOC_DAIFMT_FORMAT_MASK) {
>    184          case SND_SOC_DAIFMT_LEFT_J:
>    185                  iismod |= S3C2410_IISMOD_MSB;
>    186                  break;
>    187          case SND_SOC_DAIFMT_I2S:
>    188                  iismod &= ~S3C2410_IISMOD_MSB;
>    189                  break;
>    190          default:
>    191                  return -EINVAL;
>    192          }
>    193
>    194          writel(iismod, s3c24xx_i2s.regs + S3C2410_IISMOD);
>    195          pr_debug("hw_params w: IISMOD: %x \n", iismod);
>    196
>    197          return 0;
>    198  }
>    199
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
>


      reply	other threads:[~2022-06-27  1:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-26 21:33 kernel test robot
2022-06-27  1:46 ` Souptick Joarder [this message]

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=CAFqt6za7CyUthX9RqFSy88-+JRebk-QZ9dUtKmaLT6yPtJ_kYg@mail.gmail.com \
    --to=jrdr.linux@gmail.com \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@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