Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751594AbdFIUPV (ORCPT ); Fri, 9 Jun 2017 16:15:21 -0400 Received: from mail-wr0-f173.google.com ([209.85.128.173]:33047 "EHLO mail-wr0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751536AbdFIUPU (ORCPT ); Fri, 9 Jun 2017 16:15:20 -0400 MIME-Version: 1.0 In-Reply-To: References: <1496686434-13181-1-git-send-email-daniel.lezcano@linaro.org> <20170609154652.GG2244@mai> From: John Stultz Date: Fri, 9 Jun 2017 13:15:18 -0700 Message-ID: Subject: Re: [PATCH] ARM64: Kconfig: Fix the missing hi655x common clk To: Arnd Bergmann Cc: Daniel Lezcano , Ulf Hansson , Catalin Marinas , Will Deacon , Olof Johansson , Wei Xu , "moderated list:ARM64 PORT (AARCH64 ARCHITECTURE)" , open list Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1655 Lines: 40 On Fri, Jun 9, 2017 at 1:06 PM, Arnd Bergmann wrote: > On Fri, Jun 9, 2017 at 5:46 PM, Daniel Lezcano > wrote: >> On Tue, Jun 06, 2017 at 04:17:40PM +0200, Ulf Hansson wrote: >>> On 5 June 2017 at 20:13, Daniel Lezcano wrote: >>> > With the addition of the hi655x common clock, the config option is missing >>> > for the ARM64's hi6220 platform. That leads to a non functionnal WiFi because >>> > the hi655x clock driver misses when initializing the power sequence via DT. >>> > >>> > Cc: John Stultz >>> > Cc: Ulf Hansson >>> > Cc: Wei Xu >>> > Signed-off-by: Daniel Lezcano >>> >>> Acked-by: Ulf Hansson >>> >>> Would be nice to get this trivial fix in for 4.12 rcs to make the WiFi >>> work for Hikey. >>> >> >> I'm wondering if I submitted this patch for the right path. >> >> Shall it go through arm-soc ? > > Yes, but I'm not sure this is the right patch either. We tend to not > use 'select' for user-visible drivers, and most hisilicon platforms > won't need this driver. > > I think it would be more consistent to add this to the defconfig > and regard it as a user error when the driver is disabled on a > machine that needs it. Maybe the select is not exactly in the right place, but I don't really feel like a pmic on an SoC is a "user-visible driver". I deal with the board often and when the new dependency was made on the clk, I would have never have found it on my own w/o Ulf and Daniel pointing out what I needed to enable. thanks -john