From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
Jaska Uimonen <jaska.uimonen@intel.com>,
broonie@kernel.org
Subject: Re: [PATCH] ASoC: SOF: topology: use set_get_data in process load
Date: Wed, 7 Aug 2019 21:30:07 +0200 [thread overview]
Message-ID: <07fe0e09-6984-76c9-da7c-a1992e7f7b64@intel.com> (raw)
In-Reply-To: <20190807145227.26216-1-pierre-louis.bossart@linux.intel.com>
On 2019-08-07 16:52, Pierre-Louis Bossart wrote:
> From: Jaska Uimonen <jaska.uimonen@intel.com>
> process = kzalloc(ipc_size, GFP_KERNEL);
> - if (!process)
> + if (!process) {
> + kfree(wdata);
> return -ENOMEM;
> + }
>
> /* configure iir IPC message */
> process->comp.hdr.size = ipc_size;
> @@ -1835,7 +1890,9 @@ static int sof_process_load(struct snd_soc_component *scomp, int index,
> if (ret != 0) {
> dev_err(sdev->dev, "error: parse process.cfg tokens failed %d\n",
> le32_to_cpu(private->size));
> - goto err;
> + kfree(wdata);
> + kfree(process);
> + return ret;
> }
>
> @@ -1886,10 +1916,36 @@ static int sof_process_load(struct snd_soc_component *scomp, int index,
>
> ret = sof_ipc_tx_message(sdev->ipc, process->comp.hdr.cmd, process,
> ipc_size, r, sizeof(*r));
> - if (ret >= 0)
> +
> + if (ret < 0) {
> + dev_err(sdev->dev, "error: create process failed\n");
> + kfree(wdata);
> + kfree(process);
> return ret;
> -err:
> - kfree(process);
> + }
> +
> + /* we sent the data in single message so return */
> + if (ipc_data_size) {
> + kfree(wdata);
> + return ret;
> + }
> +
> + /* send control data with large message supported method */
> + for (i = 0; i < widget->num_kcontrols; i++) {
> + wdata[i].control->readback_offset = 0;
> + ret = snd_sof_ipc_set_get_comp_data(sdev->ipc, wdata[i].control,
> + wdata[i].ipc_cmd,
> + wdata[i].ctrl_type,
> + wdata[i].control->cmd,
> + true);
> + if (ret != 0) {
> + dev_err(sdev->dev, "error: send control failed\n");
> + kfree(process);
> + break;
> + }
> + }
> +
> + kfree(wdata);
> return ret;
> }
On several occasions you've added individual error paths instead of a
unified one. Personally I don't find it easier to read and understand
function's flow at all.
<ifs with goto err>
err:
kfree(process);
kfree(wdata);
return ret;
doesn't look that bad..
next prev parent reply other threads:[~2019-08-07 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 14:52 [PATCH] ASoC: SOF: topology: use set_get_data in process load Pierre-Louis Bossart
2019-08-07 19:30 ` Cezary Rojewski [this message]
2019-08-07 20:09 ` Sridharan, Ranjani
2019-08-07 20:17 ` Pierre-Louis Bossart
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=07fe0e09-6984-76c9-da7c-a1992e7f7b64@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jaska.uimonen@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
/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