All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Andy Green <andy.green@linaro.org>,
	Zhangfei Gao <zhangfei.gao@linaro.org>,
	Jingoo Han <jg1.han@samsung.com>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	Vinod Koul <vinod.koul@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Wei Xu <xuwei5@hisilicon.com>, Rob Herring <robh+dt@kernel.org>,
	Andy Green <andy@warmcat.com>
Subject: Re: [RFC][PATCH 07/10 v2] ASoC: hisilicon: Add hi6210 i2s audio driver
Date: Wed, 20 Jul 2016 09:53:09 -0700	[thread overview]
Message-ID: <CALAqxLV1Nn7W5DkTG4zwjVCYyT_H9KiWW-_SPEY=ngrDpemHvA@mail.gmail.com> (raw)
In-Reply-To: <20160720002835.GC6509@sirena.org.uk>

On Tue, Jul 19, 2016 at 5:28 PM, Mark Brown <broonie@kernel.org> wrote:
> On Tue, Jul 19, 2016 at 04:22:43PM -0700, John Stultz wrote:
>
>>  sound/soc/Kconfig                |   1 +
>>  sound/soc/Makefile               |   1 +
>>  sound/soc/hisilicon/Kconfig      |   5 +
>>  sound/soc/hisilicon/Makefile     |   1 +
>>  sound/soc/hisilicon/hi6210-i2s.c | 678 +++++++++++++++++++++++++++++++++++++++
>>  sound/soc/hisilicon/hi6210-i2s.h | 276 ++++++++++++++++
>>  6 files changed, 962 insertions(+)
>
> This is adding a new binding without documenting it and still looks like
> it's far more than an I2S controller.

So I added some binding documentation in the patch that proceeded this...

Oh Crud. I forgot to add the cc list to those files. Sorry for that.

Here they are on the list:
https://lkml.org/lkml/2016/7/19/820
https://lkml.org/lkml/2016/7/19/815


As for being more then an i2s controller, I don't have access to the
docs this was written with, so I'm not really sure what I can do to
properly extend this driver beyond acting as an i2s driver.  I'll take
a look, but again, my lack of familiarity with ASoC means I may need
some extra guidance. So apologies up front.

>> +     switch (params_rate(params)) {
>> +     default:
>> +             dev_err(cpu_dai->dev, "Bad rate\n");
>> +             return -EINVAL;
>
> We should tell the user what rate.
>
>> +     if (bits == HII2S_BITS_24) {
>> +             i2s->bits = 32;
>> +             dma_data->addr_width = 3;
>> +     } else {
>> +             i2s->bits = 16;
>> +             dma_data->addr_width = 2;
>> +     }
>
> This looks like it should be a switch statement, there's some similar
> stuff for the channels.

So yea, the switch selection above this does the validation and then
I'm just applying the change here.

I can duplicate the switch in both cases, but this seems a little more terse.

>> +     _hi6210_i2s_set_fmt(i2s, substream);
>
> Why is this not in line given that this is the only user?

I think it breaks up the function some, but I can move it inline.


>> +     res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>> +     if (!res) {
>> +             ret = -ENODEV;
>> +             goto err2;
>> +     }
>> +
>> +     i2s->base = devm_ioremap_resource(dev, res);
>
> devm_ioremap_resource() will check the error.
>
>> +err3:
>> +     while (--i2s->clocks)
>> +             clk_put(i2s->clk[i2s->clocks]);
>> +
>> +err2:
>> +     kfree(i2s);
>
> You switched to using devm_ but left the error handling.

Ok, will address.

Thanks for the review and feedback!
-john

  reply	other threads:[~2016-07-20 16:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 23:22 [RFC][PATCH 00/10 v2] Add HDMI audio support for HiKey John Stultz
2016-07-19 23:22 ` [RFC][PATCH 01/10 v2] k3dma: Fix hisi burst clipping John Stultz
2016-07-19 23:22 ` [RFC][PATCH 02/10 v2] k3dma: Fix dma err offsets John Stultz
2016-07-19 23:22 ` [RFC][PATCH 03/10 v2] k3dma: Fix "nobody cared" message seen on any error John Stultz
2016-07-19 23:22 ` [RFC][PATCH 04/10 v2] k3dma: Add cyclic mode for audio John Stultz
2016-07-19 23:22 ` [RFC][PATCH 05/10 v2] Kconfig: Allow k3dma driver to be selected for more then HISI3xx platforms John Stultz
2016-07-19 23:22 ` [RFC][PATCH 06/10 v2] ASoC: add hi6210-i2s DT bindings John Stultz
2016-07-19 23:22 ` [RFC][PATCH 07/10 v2] ASoC: hisilicon: Add hi6210 i2s audio driver John Stultz
2016-07-20  0:28   ` Mark Brown
2016-07-20 16:53     ` John Stultz [this message]
2016-07-20 17:08       ` Mark Brown
2016-07-19 23:22 ` [RFC][PATCH 08/10 v2] ASoC: add hi6210-hdmi-audio-codec DT bindings John Stultz
2016-07-19 23:22 ` [RFC][PATCH 09/10 v2] ASoC: hisilicon: Add hi6210 hdmi codec driver John Stultz
2016-07-20  0:31   ` Mark Brown
2016-07-19 23:22 ` [RFC][PATCH 10/10 v2] dts: hi6220: Add k3-dma and i2s/hdmi audio support John Stultz
2016-07-20  0:22 ` [RFC][PATCH 00/10 v2] Add HDMI audio support for HiKey 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='CALAqxLV1Nn7W5DkTG4zwjVCYyT_H9KiWW-_SPEY=ngrDpemHvA@mail.gmail.com' \
    --to=john.stultz@linaro.org \
    --cc=andy.green@linaro.org \
    --cc=andy@warmcat.com \
    --cc=broonie@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=jg1.han@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=perex@perex.cz \
    --cc=robh+dt@kernel.org \
    --cc=tiwai@suse.com \
    --cc=vinod.koul@intel.com \
    --cc=xuwei5@hisilicon.com \
    --cc=zhangfei.gao@linaro.org \
    /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.