From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754523Ab1LMMXU (ORCPT ); Tue, 13 Dec 2011 07:23:20 -0500 Received: from mail-gy0-f174.google.com ([209.85.160.174]:35498 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752611Ab1LMMXR (ORCPT ); Tue, 13 Dec 2011 07:23:17 -0500 MIME-Version: 1.0 In-Reply-To: References: <1323431857-8828-1-git-send-email-linus.walleij@stericsson.com> Date: Tue, 13 Dec 2011 13:23:16 +0100 Message-ID: Subject: Re: [PATCH v6] pinctrl: add a pin config interface From: Linus Walleij To: Haojian Zhuang Cc: Linus Walleij , linux-kernel@vger.kernel.org, Stephen Warren , Grant Likely , Barry Song <21cnbao@gmail.com>, Shawn Guo , Thomas Abraham , Dong Aisheng , Rajendra Nayak , Haojian Zhuang Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 13, 2011 at 8:21 AM, Haojian Zhuang wrote: > Excuse me that I didn't find that patch. Did you merge it into your > git tree? Yes. It's pushed out and will also be included in linux-next. > The latest patch on pinconf.c is updating pdev->dev to > &pdev->dev. It *should* be the other way around. So pdev->dev points to the original platform device, and thus you have a handle on that in e.g. board files where the pin controller is defined and thus you can apply pin configurations from there. > By the way, will you merge generic-pinconf into your for-next branch? Nobody has ACK:ed it and Stephen and Mark both have unresolved issue with how this should look. If the current v5 patch suits your needs, please ACK it on the mailing list so we know that there are people who like this solution apart from me. Yours, Linus Walleij