Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966314AbcKXP1I (ORCPT ); Thu, 24 Nov 2016 10:27:08 -0500 Received: from mail-qk0-f176.google.com ([209.85.220.176]:36317 "EHLO mail-qk0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965982AbcKXP1G (ORCPT ); Thu, 24 Nov 2016 10:27:06 -0500 MIME-Version: 1.0 In-Reply-To: <20161124102529.20212-1-stephen.boyd@linaro.org> References: <20161124102529.20212-1-stephen.boyd@linaro.org> From: Linus Walleij Date: Thu, 24 Nov 2016 16:27:05 +0100 Message-ID: Subject: Re: [PATCH 0/2] OF phandle nexus support + GPIO nexus To: Stephen Boyd Cc: Rob Herring , Frank Rowand , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-gpio@vger.kernel.org" , Pantelis Antoniou , Mark Brown 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: 1206 Lines: 27 On Thu, Nov 24, 2016 at 11:25 AM, Stephen Boyd wrote: > This is one small chunk of work related to DT overlays for expansion > boards. It would be good to have a way to expose #-cells types of > providers through a connector in a standard way. So we introduce a way > to make "nexus" nodes for these types of properties to remap the consumer > number space to the other side of the connector's number space. It's > basically a copy of the interrupt nexus implementation, but without > the address space matching design and interrupt-parent walking. > > The first patch implements a generic method to do this, and the second patch > adds a unit test for it. The third patch is more of an example than anything > else. It shows how we would modify frameworks to use the new API. > > Stephen Boyd (3): > of: Support parsing phandle argument lists through a nexus node > of: unittest: Add phandle remapping test > gpio: Support gpio nexus dt bindings Looks perfectly reasonable to me. But it's mainly for the DT people to review I guess. I have no idea about the eventual merge path though, I guess it needs to go through the OF tree with my ACK. Yours, Linus Walleij