All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Sit, Michael Wei Hong" <michael.wei.hong.sit@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Sia, Jee Heng" <jee.heng.sia@intel.com>
Subject: Re: [bug report] ASoC: Intel: KMB: Enable TDM audio capture
Date: Tue, 25 Aug 2020 16:58:00 +0300	[thread overview]
Message-ID: <20200825135800.GS5493@kadam> (raw)
In-Reply-To: <CE6D3DA0-65A3-42BA-8341-13A3C6E80A55@intel.com>

On Tue, Aug 25, 2020 at 01:49:25PM +0000, Sit, Michael Wei Hong wrote:
> 
> 
> > On 25 Aug 2020, at 9:21 PM, Dan Carpenter <dan.carpenter@oracle.com> wrote:
> > 
> > Hello Michael Sit Wei Hong,
> > 
> > The patch 9c3bab3c4f15: "ASoC: Intel: KMB: Enable TDM audio capture"
> > from Aug 11, 2020, leads to the following static checker warning:
> > 
> >    sound/soc/intel/keembay/kmb_platform.c:518 kmb_dai_hw_params()
> >    warn: potential ! vs ~ typo
> > 
> > sound/soc/intel/keembay/kmb_platform.c
> >   502          }
> >   503  
> >   504          config->chan_nr = params_channels(hw_params);
> >   505  
> >   506          switch (config->chan_nr) {
> >   507          case 8:
> >   508          case 4:
> >   509                  /*
> >   510                   * Platform is not capable of providing clocks for
> >   511                   * multi channel audio
> >   512                   */
> >   513                  if (kmb_i2s->master)
> >   514                          return -EINVAL;
> >   515  
> >   516                  write_val = ((config->chan_nr / 2) << TDM_CHANNEL_CONFIG_BIT) |
> >   517                                  (config->data_width << DATA_WIDTH_CONFIG_BIT) |
> >   518                                  !MASTER_MODE | TDM_OPERATION;
> >                                        ^^^^^^^^^^^^
> > MASTER_MODE is BIT(13).  It's unclear what this is supposed to be.  My
> > best guess is that the ! should just be deleted.
> 
> This ! is intentional because it is meant to be Slave mode. Would a better approach be to create another #define for slave mode?

In my opinion, it's better to just leave it out.  ORing with zero causes
a different static checker warning on my unreleased checks...  Is it
0 << 13?  I feel like ORing with zero just makes things more confusing.

regards,
dan carpenter


  reply	other threads:[~2020-08-25 14:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 13:21 [bug report] ASoC: Intel: KMB: Enable TDM audio capture Dan Carpenter
2020-08-25 13:49 ` Sit, Michael Wei Hong
2020-08-25 13:58   ` Dan Carpenter [this message]
2020-08-25 14:47     ` Sit, Michael Wei Hong
2020-08-25 15:58       ` Pierre-Louis Bossart
2020-08-25 17:22         ` Sit, Michael Wei Hong
2020-08-25 18:23           ` Pierre-Louis Bossart
2020-08-26  3:09             ` Sit, Michael Wei Hong

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=20200825135800.GS5493@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jee.heng.sia@intel.com \
    --cc=michael.wei.hong.sit@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.