[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180214184705.GC93895@bjorns-mbp-2.lan>
Date: Wed, 14 Feb 2018 10:47:05 -0800
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc: vinod.koul@...el.com, andy.gross@...aro.org,
dmaengine@...r.kernel.org, robh+dt@...nel.org,
mark.rutland@....com, david.brown@...aro.org,
dan.j.williams@...el.com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-soc@...r.kernel.org, yanhe@...cinc.com,
ramkri@....qualcomm.com, sdharia@...cinc.com
Subject: Re: [PATCH v2 1/5] dmaengine: qcom: bam_dma: make bam clk optional
On Wed 14 Feb 10:19 PST 2018, Srinivas Kandagatla wrote:
> Thanks for the Review,
>
> On 14/02/18 15:41, Bjorn Andersson wrote:
> > > bdev->bamclk = devm_clk_get(bdev->dev, "bam_clk");
> > > - if (IS_ERR(bdev->bamclk))
> > > - return PTR_ERR(bdev->bamclk);
> > > -
> > > - ret = clk_prepare_enable(bdev->bamclk);
> > > - if (ret) {
> > > - dev_err(bdev->dev, "failed to prepare/enable clock\n");
> > > - return ret;
> > > + if (IS_ERR(bdev->bamclk)) {
> > In the case of !bdev->controlled_remotely I think this should still be
> > an error.
> >
> Yep makes sense,
>
> You mean something like this?
>
> ------------------------->cut<------------------------
> bdev->bamclk = devm_clk_get(bdev->dev, "bam_clk");
> if (IS_ERR(bdev->bamclk)) {
> if (!bdev->controlled_remotely);
> return PTR_ERR(bdev->bamclk);
>
> bdev->bamclk = NULL;
> }
>
> ret = clk_prepare_enable(bdev->bamclk);
> if (ret) {
> dev_err(bdev->dev, "failed to prepare/enable clock\n");
> return ret;
> }
>
> ------------------------->cut<------------------------
>
Yes
Regards,
Bjorn
Powered by blists - more mailing lists