Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752110AbaGaXbg (ORCPT ); Thu, 31 Jul 2014 19:31:36 -0400 Received: from cantor2.suse.de ([195.135.220.15]:43535 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750906AbaGaXbe (ORCPT ); Thu, 31 Jul 2014 19:31:34 -0400 Message-ID: <53DAD1C6.9070102@suse.de> Date: Fri, 01 Aug 2014 01:31:18 +0200 From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= Organization: SUSE LINUX Products GmbH User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Tomasz Figa , linux-samsung-soc@vger.kernel.org CC: Vincent Palatin , Doug Anderson , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, Stephan van Schaik , Javier Martinez Canillas , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Ben Dooks , Kukjin Kim , LKML Subject: Re: [PATCH v4 4/4] ARM: dts: Add exynos5250-spring device tree References: <1406822910-6255-1-git-send-email-afaerber@suse.de> <1406822910-6255-5-git-send-email-afaerber@suse.de> <53DA936E.9060004@gmail.com> <53DA9709.10602@suse.de> <53DA9BA9.60808@gmail.com> <53DACE73.8080009@suse.de> <53DAD0AA.7040105@gmail.com> In-Reply-To: <53DAD0AA.7040105@gmail.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 01.08.2014 01:26, schrieb Tomasz Figa: > On 01.08.2014 01:17, Andreas Färber wrote: >> Am 31.07.2014 21:40, schrieb Tomasz Figa: >>> On 31.07.2014 21:20, Andreas Färber wrote: >>>> Am 31.07.2014 21:05, schrieb Tomasz Figa: >>>>> On 31.07.2014 18:08, Andreas Färber wrote: > [snip] >>>>>> +&dp_hpd { >>>>>> + samsung,pins = "gpc3-0"; >>>>>> + samsung,pin-function = <0>; >>>>>> + samsung,pin-pud = <3>; >>>>>> + samsung,pin-drv = <0>; >>>>>> +}; >>>>> >>>>> Hmm, what node is this referencing? I believe this should rather >>>>> reference the pin controller and add a new board-specific pinconf/pinmux >>>>> group instead.... >>>> >>>> It's a -pinctrl node. See v3->v4 change log and discussion on v3. >>>> >>> >>> Well, this is clearly a board specific node anyway, because it does not >>> refer to a special function, but simply an input/interrupt GPIO. If it >>> somehow has landed in generic pinctrl dtsi then it should be removed >>> from there and this patch should simply introduce its own instance of >>> dp_hpd node, so you did the right thing in v3. >> >> Well, my point was that the 3.8 tree contains only one dp-hpd node, not >> two as we would get by adding a new node here. >> >> Apart from Spring, it's used in Snow and SMDK5250, so moving it there >> seems feasible and the cleanest solution to me. >> > > What I mean is that in exynos5250-pinctrl.dtsi only generic SoC pin > groups should be defined and those more or less correspond to groups > with samsung,pin-function set to something other than 0 (input) or 1 > (output). Now here hpd_gpio is just a normal GPIO input used as > interrupt source to detect when a cable is plugged or unplugged. This is > by no means generic to the SoC, because any GPIO with interrupt > capability can be used for this purpose. This means that the whole > pin{conf,mux} group should be defined on board level. Exactly what I meant! :) Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/