From: Vinod Subject: Re: [PATCH v4 6/6] crypto: qcom: Add ACPI support Date: Mon, 9 Jul 2018 11:31:57 +0530 Message-ID: <20180709060157.GZ22377@vkoul-mobl> References: <20180704114427.29953-1-vkoul@kernel.org> <20180704114427.29953-7-vkoul@kernel.org> <20180705060733.GH22377@vkoul-mobl> <38f34817-ff86-06b7-4aab-a009c353a6db@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, Bjorn Andersson , Matt Mackall , Herbert Xu , Arnd Bergmann , Greg Kroah-Hartman , linux-arm-msm@vger.kernel.org, Stephen Boyd , Jeffrey Hugo To: Timur Tabi Return-path: Content-Disposition: inline In-Reply-To: <38f34817-ff86-06b7-4aab-a009c353a6db@kernel.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On 07-07-18, 13:05, Timur Tabi wrote: > On 7/5/18 1:07 AM, Vinod wrote: > > Yes we can add driver data in ACPI ID as well so code can be: > > > > if (!has_acpi_companion(&pdev->dev)) { > > rng->clk = devm_clk_get(&pdev->dev, "core"); > > if (IS_ERR(rng->clk)) > > return PTR_ERR(rng->clk); > > } > > rng->skip_init = device_get_match_data(&pdev->dev); > > > > Looks much neater. > > Yeah, I like it. > > > I will wait for feedback on other patches before updating this. > > Jeff said it works, so I guess v5 will be good to go. Yes posting that right now. It would be great if you folks can test again on ACPI systems Thanks -- ~Vinod