Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753125AbdHRNXv (ORCPT ); Fri, 18 Aug 2017 09:23:51 -0400 Received: from mail.kernel.org ([198.145.29.99]:54590 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753008AbdHRNXs (ORCPT ); Fri, 18 Aug 2017 09:23:48 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B199B22C8B Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=shawnguo@kernel.org Date: Fri, 18 Aug 2017 21:22:02 +0800 From: Shawn Guo To: kgunda@codeaurora.org Cc: gregkh@linuxfoundation.org, sboyd@codeaurora.org, Abhijeet Dharmapurikar , David Collins , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-msm-owner@vger.kernel.org Subject: Re: [PATCH V2 11/12] spmi: pmic-arb: add support for HW version 5 Message-ID: <20170818132200.GP7608@dragon> References: <1501225847-27807-1-git-send-email-kgunda@codeaurora.org> <1501225847-27807-12-git-send-email-kgunda@codeaurora.org> <20170817074150.GA17549@dragon> <3d9ed27c23523965dae6706ff007f1b1@codeaurora.org> <20170817122816.GB17549@dragon> <1ce6e8a0816d6d9b0ade86d3592b4dca@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1ce6e8a0816d6d9b0ade86d3592b4dca@codeaurora.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 607 Lines: 13 On Fri, Aug 18, 2017 at 04:43:23PM +0530, kgunda@codeaurora.org wrote: > From the logs the ownership for these GPIOs is not assigned to the > application processor but to another master. Considering this is a > (apq8016-sbc) APSS only platform ideally the fix for this would be > to update the ownership table in the boot loader. The other option > would be to make the existing ownership check in SW optional for a > platform via DT. I will push a patch shortly for this. Could you > please give that a try. I just tested it on db410c board, and it fixes the problem for me. Thanks for the patch. Shawn