From: "Jernej Škrabec" <jernej.skrabec@siol.net>
To: Vinod Koul <vkoul@kernel.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
maxime.ripard@bootlin.com, linux-sunxi@googlegroups.com,
linux-kernel@vger.kernel.org, wens@csie.org, robh+dt@kernel.org,
dmaengine@vger.kernel.org, dan.j.williams@intel.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/6] dmaengine: sun6i: Add a quirk for additional mbus clock
Date: Sat, 16 Mar 2019 12:23:47 +0100 [thread overview]
Message-ID: <2451376.qVWA8nfu3q@jernej-laptop> (raw)
In-Reply-To: <20190316110753.GH5348@vkoul-mobl>
Hi!
Dne sobota, 16. marec 2019 ob 12:07:53 CET je Vinod Koul napisal(a):
> On 07-03-19, 17:58, Jernej Skrabec wrote:
> > H6 DMA controller needs additional mbus clock to be enabled.
> >
> > Add a quirk for it and handle it accordingly.
> >
> > Signed-off-by: Jernej Skrabec <jernej.skrabec@siol.net>
> > ---
> >
> > drivers/dma/sun6i-dma.c | 23 ++++++++++++++++++++++-
> > 1 file changed, 22 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/dma/sun6i-dma.c b/drivers/dma/sun6i-dma.c
> > index 0cd13f17fc11..761555080325 100644
> > --- a/drivers/dma/sun6i-dma.c
> > +++ b/drivers/dma/sun6i-dma.c
> > @@ -129,6 +129,7 @@ struct sun6i_dma_config {
> >
> > u32 dst_burst_lengths;
> > u32 src_addr_widths;
> > u32 dst_addr_widths;
> >
> > + bool mbus_clk;
> >
> > };
> >
> > /*
> >
> > @@ -182,6 +183,7 @@ struct sun6i_dma_dev {
> >
> > struct dma_device slave;
> > void __iomem *base;
> > struct clk *clk;
> >
> > + struct clk *clk_mbus;
>
> So rather than have mbus_clk and then a ptr, why not use the ptr and use
> NULL value to check for..?
>
I'm not sure what you mean here. clk_mbus will hold a reference to a clock
retrieved by devm_clk_get() so it has to be "struct clk *".
What I'm missing here?
> > int irq;
> > spinlock_t lock;
> > struct reset_control *rstc;
> >
> > @@ -1208,6 +1210,14 @@ static int sun6i_dma_probe(struct platform_device
> > *pdev)>
> > return PTR_ERR(sdc->clk);
> >
> > }
> >
> > + if (sdc->cfg->mbus_clk) {
>
> where is the populated? I was expecting this to be set based on DT!
Of course it is based on DT. Check patch 5, where quirks structure attached to
H6 DMA compatible contains ".mbus_clk = true,". "sdc->cfg" points to this
quirk structure.
>
> > + sdc->clk_mbus = devm_clk_get(&pdev->dev, "mbus");
> > + if (IS_ERR(sdc->clk_mbus)) {
> > + dev_err(&pdev->dev, "No mbus clock
specified\n");
> > + return PTR_ERR(sdc->clk_mbus);
> > + }
> > + }
> > +
> >
> > sdc->rstc = devm_reset_control_get(&pdev->dev, NULL);
> > if (IS_ERR(sdc->rstc)) {
> >
> > dev_err(&pdev->dev, "No reset controller specified\n");
> >
> > @@ -1312,11 +1322,19 @@ static int sun6i_dma_probe(struct platform_device
> > *pdev)>
> > goto err_reset_assert;
> >
> > }
> >
> > + if (sdc->cfg->mbus_clk) {
> > + ret = clk_prepare_enable(sdc->clk_mbus);
> > + if (ret) {
> > + dev_err(&pdev->dev, "Couldn't enable mbus
clock\n");
> > + goto err_clk_disable;
> > + }
> > + }
> > +
> >
> > ret = devm_request_irq(&pdev->dev, sdc->irq, sun6i_dma_interrupt,
0,
> >
> > dev_name(&pdev->dev), sdc);
> >
> > if (ret) {
> >
> > dev_err(&pdev->dev, "Cannot request IRQ\n");
> >
> > - goto err_clk_disable;
> > + goto err_mbus_clk_disable;
> >
> > }
> >
> > ret = dma_async_device_register(&sdc->slave);
> >
> > @@ -1341,6 +1359,8 @@ static int sun6i_dma_probe(struct platform_device
> > *pdev)>
> > dma_async_device_unregister(&sdc->slave);
> >
> > err_irq_disable:
> > sun6i_kill_tasklet(sdc);
> >
> > +err_mbus_clk_disable:
> > + clk_disable_unprepare(sdc->clk_mbus);
> >
> > err_clk_disable:
> > clk_disable_unprepare(sdc->clk);
> >
> > err_reset_assert:
> > @@ -1359,6 +1379,7 @@ static int sun6i_dma_remove(struct platform_device
> > *pdev)>
> > sun6i_kill_tasklet(sdc);
> >
> > + clk_disable_unprepare(sdc->clk_mbus);
> >
> > clk_disable_unprepare(sdc->clk);
> > reset_control_assert(sdc->rstc);
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-16 11:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 16:58 [PATCH 0/6] Allwinner H6 DMA support Jernej Skrabec
2019-03-07 16:58 ` [PATCH 1/6] dt-bindings: arm64: allwinner: h6: Add binding for DMA controller Jernej Skrabec
2019-03-16 10:57 ` Vinod Koul
2019-03-16 11:27 ` Jernej Škrabec
2019-03-27 23:47 ` Rob Herring
2019-03-07 16:58 ` [PATCH 2/6] dmaengine: sun6i: Add a quirk for additional mbus clock Jernej Skrabec
2019-03-11 5:47 ` Chen-Yu Tsai
2019-03-16 11:07 ` Vinod Koul
2019-03-16 11:23 ` Jernej Škrabec [this message]
2019-03-22 12:59 ` Vinod Koul
2019-03-22 13:03 ` Maxime Ripard
2019-03-07 16:58 ` [PATCH 3/6] dmaengine: sun6i: Add a quirk for setting DRQ fields Jernej Skrabec
2019-03-07 16:58 ` [PATCH 4/6] dmaengine: sun6i: Add a quirk for setting mode fields Jernej Skrabec
2019-03-07 16:58 ` [PATCH 5/6] dmaengine: sun6i: Add support for H6 DMA Jernej Skrabec
2019-03-16 11:13 ` Vinod Koul
2019-03-16 11:37 ` Jernej Škrabec
2019-03-07 16:58 ` [PATCH 6/6] arm64: dts: allwinner: h6: Add DMA node Jernej Skrabec
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=2451376.qVWA8nfu3q@jernej-laptop \
--to=jernej.skrabec@siol.net \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=wens@csie.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