From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Magnus Damm <magnus.damm@gmail.com>,
Gareth Williams <gareth.williams.jx@renesas.com>,
Phil Edworthy <phil.edworthy@renesas.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Vinod Koul <vkoul@kernel.org>,
linux-renesas-soc@vger.kernel.org, dmaengine@vger.kernel.org,
Milan Stevanovic <milan.stevanovic@se.com>,
Jimmy Lalande <jimmy.lalande@se.com>,
Pascal Eberhard <pascal.eberhard@se.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>,
Clement Leger <clement.leger@bootlin.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, Viresh Kumar <vireshk@kernel.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v8 5/9] dmaengine: dw: dmamux: Introduce RZN1 DMA router support
Date: Fri, 8 Apr 2022 14:45:50 +0300 [thread overview]
Message-ID: <YlAgbh2AFevBktxd@smile.fi.intel.com> (raw)
In-Reply-To: <6fbeebe2-9693-f91-78bd-451480f7a6dd@linux.intel.com>
On Fri, Apr 08, 2022 at 12:55:47PM +0300, Ilpo Järvinen wrote:
> On Wed, 6 Apr 2022, Miquel Raynal wrote:
>
> > The Renesas RZN1 DMA IP is based on a DW core, with eg. an additional
> > dmamux register located in the system control area which can take up to
> > 32 requests (16 per DMA controller). Each DMA channel can be wired to
> > two different peripherals.
> >
> > We need two additional information from the 'dmas' property: the channel
> > (bit in the dmamux register) that must be accessed and the value of the
> > mux for this channel.
> > + mask = BIT(map->req_idx);
> > + mutex_lock(&dmamux->lock);
> > + dmamux->used_chans |= mask;
> > + ret = r9a06g032_sysctrl_set_dmamux(mask, val ? mask : 0);
> > + if (ret)
> > + goto release_chan_and_unlock;
> > +
> > + mutex_unlock(&dmamux->lock);
> > +
> > + return map;
> > +
> > +release_chan_and_unlock:
> > + dmamux->used_chans &= ~mask;
>
> Now that I check this again, I'm not sure why dmamux->used_chans |= mask;
> couldn't be done after r9a06g032_sysctrl_set_dmamux() call so this
> rollback of it wouldn't be necessary.
I would still need the mutex unlock which I believe is down path there under
some other label. Hence you are proposing something like
mask = BIT(map->req_idx);
mutex_lock(&dmamux->lock);
ret = r9a06g032_sysctrl_set_dmamux(mask, val ? mask : 0);
if (ret)
goto err_unlock; // or whatever label is
dmamux->used_chans |= mask;
mutex_unlock(&dmamux->lock);
return map;
Is that correct? If so, I don't see impediments either.
> Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-04-08 11:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 16:18 [PATCH v8 0/9] RZN1 DMA support Miquel Raynal
2022-04-06 16:18 ` [PATCH v8 1/9] dt-bindings: dmaengine: Introduce RZN1 dmamux bindings Miquel Raynal
2022-04-06 16:18 ` [PATCH v8 2/9] dt-bindings: clock: r9a06g032-sysctrl: Reference the DMAMUX subnode Miquel Raynal
2022-04-06 16:18 ` [PATCH v8 3/9] dt-bindings: dmaengine: Introduce RZN1 DMA compatible Miquel Raynal
2022-04-06 16:18 ` [PATCH v8 4/9] soc: renesas: rzn1-sysc: Export function to set dmamux Miquel Raynal
2022-04-06 16:18 ` [PATCH v8 5/9] dmaengine: dw: dmamux: Introduce RZN1 DMA router support Miquel Raynal
2022-04-08 9:55 ` Ilpo Järvinen
2022-04-08 11:45 ` Andy Shevchenko [this message]
2022-04-08 12:38 ` Ilpo Järvinen
2022-04-12 10:12 ` Miquel Raynal
2022-04-11 11:24 ` Vinod Koul
2022-04-12 10:12 ` Miquel Raynal
2022-04-06 16:18 ` [PATCH v8 6/9] clk: renesas: r9a06g032: Probe possible children Miquel Raynal
2022-04-06 16:18 ` [PATCH v8 7/9] dmaengine: dw: Add RZN1 compatible Miquel Raynal
2022-04-06 16:18 ` [PATCH v8 8/9] ARM: dts: r9a06g032: Add the two DMA nodes Miquel Raynal
2022-04-06 16:18 ` [PATCH v8 9/9] ARM: dts: r9a06g032: Describe the DMA router Miquel Raynal
2022-04-07 0:45 ` [PATCH v8 0/9] RZN1 DMA support Stephen Boyd
2022-04-07 8:16 ` Miquel Raynal
2022-04-11 15:09 ` Geert Uytterhoeven
2022-04-12 7:31 ` Miquel Raynal
2022-04-12 7:37 ` Geert Uytterhoeven
2022-04-12 7:43 ` Miquel Raynal
2022-04-12 7:52 ` Geert Uytterhoeven
2022-04-12 8:03 ` Miquel Raynal
2022-04-12 8:12 ` Geert Uytterhoeven
2022-04-12 10:08 ` Miquel Raynal
2022-04-14 11:24 ` Miquel Raynal
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=YlAgbh2AFevBktxd@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=clement.leger@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=gareth.williams.jx@renesas.com \
--cc=geert@linux-m68k.org \
--cc=herve.codina@bootlin.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jimmy.lalande@se.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=milan.stevanovic@se.com \
--cc=miquel.raynal@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=pascal.eberhard@se.com \
--cc=phil.edworthy@renesas.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=vireshk@kernel.org \
--cc=vkoul@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).