From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
dmaengine <dmaengine@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Gareth Williams <gareth.williams.jx@renesas.com>,
Phil Edworthy <phil.edworthy@renesas.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Milan Stevanovic <milan.stevanovic@se.com>,
Jimmy Lalande <jimmy.lalande@se.com>,
Pascal Eberhard <pascal.eberhard@se.com>
Subject: Re: [PATCH v2 4/8] dma: dmamux: Introduce RZN1 DMA router support
Date: Thu, 24 Feb 2022 16:56:40 +0100 [thread overview]
Message-ID: <20220224165640.321d7c56@xps13> (raw)
In-Reply-To: <CAMuHMdWofNo5aCZscADc_LuQjzDb7YoQhZS736d7_hrswdY5DA@mail.gmail.com>
Hi Geert,
geert@linux-m68k.org wrote on Thu, 24 Feb 2022 13:16:09 +0100:
> Hi Miquel,
>
> On Thu, Feb 24, 2022 at 12:36 PM Miquel Raynal
> <miquel.raynal@bootlin.com> wrote:
> > > > > > > > +static int rzn1_dmamux_probe(struct platform_device *pdev)
> > > > > > > > +{
> > > > > > > > + struct device_node *mux_node = pdev->dev.of_node;
> > > > > > > > + const struct of_device_id *match;
> > > > > > > > + struct device_node *dmac_node;
> > > > > > > > + struct rzn1_dmamux_data *dmamux;
> > > > > > > > +
> > > > > > > > + dmamux = devm_kzalloc(&pdev->dev, sizeof(*dmamux), GFP_KERNEL);
> > > > > > > > + if (!dmamux)
> > > > > > > > + return -ENOMEM;
> > > > > > > > +
> > > > > > > > + mutex_init(&dmamux->lock);
> > > > > > > > +
> > > > > > > > + dmac_node = of_parse_phandle(mux_node, "dma-masters", 0);
> > > > > > > > + if (!dmac_node)
> > > > > > > > + return dev_err_probe(&pdev->dev, -ENODEV, "Can't get DMA master node\n");
> > > > > > > > +
> > > > > > > > + match = of_match_node(rzn1_dmac_match, dmac_node);
> > > > > > > > + if (!match) {
> > > > > > > > + of_node_put(dmac_node);
> > > > > > > > + return dev_err_probe(&pdev->dev, -EINVAL, "DMA master is not supported\n");
> > > > > > > > + }
> > > > > > > > +
> > > > > > > > + if (of_property_read_u32(dmac_node, "dma-requests", &dmamux->dmac_requests)) {
> > > > > > > > + of_node_put(dmac_node);
> > > > > > > > + return dev_err_probe(&pdev->dev, -EINVAL, "Missing DMAC requests information\n");
> > > > > > > > + }
> > > > > > > > +
> > > > > > > > + of_node_put(dmac_node);
> > > > > > >
> > > > > > > When hardcoding dmac_requests to 16, I guess the whole dmac_node
> > > > > > > handling can be removed?
> > > > > >
> > > > > > Not really, I think the following checks are still valid and fortunate,
> > > > > > and they need some of_ handling to work properly:
> > > > > > - verify that the chan requested is within the range of dmac_requests
> > > > > > in the _route_allocate() callback
> > > > > > - ensure the dmamux is wired to a supported DMAC in the DT (this
> > > > > > condition might be loosen in the future if needed or dropped entirely
> > > > > > if considered useless)
> > > > > > - I would like to add a check against the number of requests supported
> > > > > > by the dmamux and the dmac (not done yet).
> > > > > > For the record, I've taken inspiration to write these lines on the other
> > > > > > dma router driver from TI.
> >
> > ^^^^^^^^^^^
> > ... these checks
>
> I don't know. Some of them will be checked when calling into the
> parent DMAC, right?
Only the first item above will be validated by the DMAC driver. But I
prefer to error out sooner than later, because getting the mux in
place while knowing that the request is invalid sounds silly.
Thanks,
Miquèl
next prev parent reply other threads:[~2022-02-24 15:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 10:34 [PATCH v2 0/8] RZN1 DMA support Miquel Raynal
2022-02-22 10:34 ` [PATCH v2 1/8] dt-bindings: dma: Introduce RZN1 dmamux bindings Miquel Raynal
2022-02-23 11:27 ` Geert Uytterhoeven
2022-02-22 10:34 ` [PATCH v2 2/8] dt-bindings: dma: Introduce RZN1 DMA compatible Miquel Raynal
2022-02-23 12:21 ` Geert Uytterhoeven
2022-02-23 15:49 ` Miquel Raynal
2022-02-23 16:16 ` Geert Uytterhoeven
2022-02-23 17:10 ` Miquel Raynal
2022-02-22 10:34 ` [PATCH v2 3/8] soc: renesas: rzn1-sysc: Export function to set dmamux Miquel Raynal
2022-02-23 12:28 ` Geert Uytterhoeven
2022-02-23 15:54 ` Miquel Raynal
2022-02-22 10:34 ` [PATCH v2 4/8] dma: dmamux: Introduce RZN1 DMA router support Miquel Raynal
2022-02-22 20:27 ` kernel test robot
2022-02-23 8:26 ` Miquel Raynal
2022-02-23 8:26 ` Miquel Raynal
2022-02-23 10:31 ` Miquel Raynal
2022-02-23 12:46 ` Geert Uytterhoeven
2022-02-23 16:49 ` Miquel Raynal
2022-02-24 9:14 ` Geert Uytterhoeven
2022-02-24 9:27 ` Miquel Raynal
2022-02-24 9:52 ` Geert Uytterhoeven
2022-02-24 11:36 ` Miquel Raynal
2022-02-24 12:16 ` Geert Uytterhoeven
2022-02-24 15:56 ` Miquel Raynal [this message]
2022-02-22 10:34 ` [PATCH v2 5/8] dma: dw: Avoid partial transfers Miquel Raynal
2022-02-23 13:35 ` Andy Shevchenko
2022-02-24 16:30 ` Miquel Raynal
2022-02-25 20:30 ` Andy Shevchenko
2022-02-22 10:34 ` [PATCH v2 6/8] dma: dw: Add RZN1 compatible Miquel Raynal
2022-02-23 12:50 ` Geert Uytterhoeven
2022-02-22 10:34 ` [PATCH v2 7/8] ARM: dts: r9a06g032: Add the two DMA nodes Miquel Raynal
2022-02-23 12:54 ` Geert Uytterhoeven
2022-02-23 17:14 ` Miquel Raynal
2022-02-24 9:17 ` Geert Uytterhoeven
2022-02-22 10:34 ` [PATCH v2 8/8] ARM: dts: r9a06g032: Describe the DMA router 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=20220224165640.321d7c56@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=gareth.williams.jx@renesas.com \
--cc=geert@linux-m68k.org \
--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=mturquette@baylibre.com \
--cc=pascal.eberhard@se.com \
--cc=phil.edworthy@renesas.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--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 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.