public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
To: Raphael-Xu <13691752556@139.com>, broonie@kernel.org
Cc: alsa-devel@alsa-project.org, raphael-xu@ti.com,
	shenghao-ding@ti.com, navada@ti.com
Subject: Re: [PATCH v2] add tas2780
Date: Wed, 6 Jul 2022 12:29:59 +0200	[thread overview]
Message-ID: <3d16471d-62f0-a0fc-24f5-df414de87b07@linux.intel.com> (raw)
In-Reply-To: <20220706095721.18974-1-13691752556@139.com>

On 7/6/2022 11:57 AM, Raphael-Xu wrote:
> diff --git a/sound/soc/codecs/tas2780.c b/sound/soc/codecs/tas2780.c
> new file mode 100644
> index 000000000000..e6923c791b49
> --- /dev/null
> +++ b/sound/soc/codecs/tas2780.c
> @@ -0,0 +1,693 @@
> +// SPDX-License-Identifier: GPL-2.0
> +// Driver for the Texas Instruments TAS2780 Mono
> +//		Audio amplifier
> +// Copyright (C) 2022 Texas Instruments Inc.
> +

I noticed one more thing, are all those headers really needed?

> +#include <linux/module.h>
> +#include <linux/moduleparam.h>
I see no module parameters in code?

> +#include <linux/err.h>
> +#include <linux/init.h>
This seems to be used mainly for marking functions as __init etc. which 
doesn't seem to be done here?

> +#include <linux/pm.h>
> +#include <linux/i2c.h>
> +#include <linux/gpio.h>
> +#include <linux/gpio/consumer.h>
> +#include <linux/regmap.h>
> +#include <linux/of.h>
> +#include <linux/of_gpio.h>
> +#include <sound/soc.h>
> +#include <sound/pcm.h>
> +#include <sound/pcm_params.h>
> +#include <sound/initval.h>
This one also seems to define things that aren't used in code?

> +#include <sound/tlv.h>



  reply	other threads:[~2022-07-06 10:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06  9:57 [PATCH v2] add tas2780 Raphael-Xu
2022-07-06 10:29 ` Amadeusz Sławiński [this message]
2022-07-06 13:07 ` Mark Brown

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=3d16471d-62f0-a0fc-24f5-df414de87b07@linux.intel.com \
    --to=amadeuszx.slawinski@linux.intel.com \
    --cc=13691752556@139.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=navada@ti.com \
    --cc=raphael-xu@ti.com \
    --cc=shenghao-ding@ti.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