From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755074AbcLNJBb (ORCPT ); Wed, 14 Dec 2016 04:01:31 -0500 Received: from mout.kundenserver.de ([212.227.17.13]:63380 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754903AbcLNJB3 (ORCPT ); Wed, 14 Dec 2016 04:01:29 -0500 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Jaghathiswari Rankappagounder Natarajan , openbmc@lists.ozlabs.org, robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk, gregkh@linuxfoundation.org, joel@jms.id.au, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, "linux-gpio@vger.kernel.org" , linus.walleij@linaro.org Subject: Re: [PATCH linux v1 4/4] arm: dts: Add dt-binding to support seven segment display on zaius Date: Wed, 14 Dec 2016 10:00:46 +0100 Message-ID: <10697525.O7CkPN6Gfl@wuerfel> User-Agent: KMail/5.1.3 (Linux/4.4.0-34-generic; KDE/5.18.0; x86_64; ; ) In-Reply-To: <3917905.e4iOqADnVQ@wuerfel> References: <1481702104-8617-1-git-send-email-jaghu@google.com> <1481702104-8617-5-git-send-email-jaghu@google.com> <3917905.e4iOqADnVQ@wuerfel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:kxfd69o2y9bGcxwduQvQfj+N5KPttM4Hp9f9O/8DSAAkxl0c8FL MNSE66EgXm+ii4YQw9+dOH+zDyYZvqp94FRbC/U6KqaTO7EO72mO75XfE4+0IUfU98mq15A MxPPrqKfrdY/jGUFVSFHQ3o+mh5OXE1ceO8u5nGji1mjEisax2NZrHSol6USaKjsEMJT+go fQsP7yEYM29aZFx3BMiJw== X-UI-Out-Filterresults: notjunk:1;V01:K0:hSksyn8eTF4=:HV5pr/K/kl42ax3X3rGqih ZmSoWU/dJC/XpB0VRFiYhRuw+taS28luMR3eH3p6H5VJ8PbUmUzU+tooLdEAsOtr2lwMRQvSw naHlKLodilcm7Ltj5NJEvuQT4gQd2pwPACldUgJbwil+JAMtKt+wMINHVYlms0OrOh0zmzfGe YkTMRKYFwvY7bJR3/f3whFGn3n5RVD3qQu9LZy7BQSibxf+O/a8asu0i4DTK7e4qq2EOgsFdB Jum+CR15rKv6ZOqoyhtTciU6odbVagK5lealrwbstZLcmcphUVT6Jhe/7Kh/853ZTngUd82zR H4fRemgSpimNe7nWQOukl5nfKan+2tdzGjthisQYOG3EU1DAqQGnNJWuEu8RCKaJCHWHCvPr+ V7gvhNia/nWsIl8trNDcZYs3RG+FaezUtNdokxHQ4chnxD0pP3i3Q9Rb2Jl6WoJ4+vAdKafmv vZQDNiIxdJZC78I6T1Zc0Nd5J1HzswkOb2ufR+Gt5PqE9htAcw0/0VHLsK2Tipe2OS1yOygPz o4QdvdJR9K5o7hfb8yzl47hZTwMnUe6M1k8h2k2f88pI7ZRGTsdHWklJeyOIL/U1nPGIrILdh 8kngDmKMRZScAHOW7TCxmGUZGUgr+Hot999mrIQ6fvPi+J/MW0IqnjARsCiHaeRqsPOFDtn3r +AFLtd2UsOs2z1oAuGgbeEx+qMAlJS10IKBI+kT8+0Y8GYqXXryyd2gOT6JrBcjNfundAYcZT 9lMWcjE0yjSAD4Pa Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, December 14, 2016 9:55:47 AM CET Arnd Bergmann wrote: > According to your introductory mail, the interface is assumed to be > a 74HC164. Should we use that ID in the compatible string? > > We can always add other strings later if we want to support multiple > wire formats. Actually, looking up 74hc164, that seems to be a gpio expander, so maybe a more flexible way to do the same is to put a driver for the expander into drivers/gpio/ and have the main driver access the outputs of that using the gpiolib interface. Arnd