From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E828CFA372A for ; Wed, 16 Oct 2019 11:19:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BC46A2067B for ; Wed, 16 Oct 2019 11:19:18 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="ZE6OEgnZ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389534AbfJPLTS (ORCPT ); Wed, 16 Oct 2019 07:19:18 -0400 Received: from mail-lf1-f66.google.com ([209.85.167.66]:39299 "EHLO mail-lf1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390988AbfJPLTR (ORCPT ); Wed, 16 Oct 2019 07:19:17 -0400 Received: by mail-lf1-f66.google.com with SMTP id 195so4179074lfj.6 for ; Wed, 16 Oct 2019 04:19:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1AlVFzVNzLFhybDABbQIP7y9fwuWZqgdiTuBdrVDMgU=; b=ZE6OEgnZ8yrNuwOpjQUl1DrdrhOJcU/OfJQ+UWAJV5VSuBLt4kobSn90ZvkwKhz3/W DmWuNa8o4L6xpUpEA32J5Ft1QTqgjgdu1dbOpgk5naABVzkOtVTLGgWzYWNTzQ0WgTbb Y5niXn2s+/QyNMl5FrZPP125aQ4QKxA3TA4Lw+iuOCQIhfIOlJhBFdeOJIR1GZ+oDqDq hCnZiK17J2nBsS8Ybej2tVBY0I7+6EKSRi0R6PvzZFSb1ptl6XnMGK+lHRNew2QPY1xJ KNOCbpWsHgotFI3zRLMVcXg5iQytMnF3Gq7qsWWyjGRj8Jo3TTknxKUco7I816TsaM43 NMEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1AlVFzVNzLFhybDABbQIP7y9fwuWZqgdiTuBdrVDMgU=; b=o9wom2wqo3H4aSryo0v4zLk0ZvPGfXzvcOOrf05Tf8h7YxtmB0HaAvzFVFLLF1mqcS kW+jXB47ikOK7oEt0aWRwFmo+Jkbtyc5Jv/lbfKOgyzPX4y0++v04GtHErA/yRlUjcZ2 X4ZhWcapzXw1Qbp1IQC1owCF2wso4dIXDhsJh440u7sK8AwBSh/dElgZ+Kq0h1CIV2LV N6qhBsZZffXfrx3VgTYXnzjU7AVMAwjgOUb8hm1m2PIn9vSgBzWkVgX0mhAsN5wQlCp7 NELrZJn7sZYGfstmK5sU8IUNao9klQLs0qhUrScyZ6bN+IbU+B/Ah4oLi9l19NlxPOR1 +3Ww== X-Gm-Message-State: APjAAAXg+WsYwVa8i/zjjqiaD3t5QOkCFIuuLRJWaCjdH8me1q49WTVO DatH+cRCzv583tAUIGWZj4KQj8ikuPEJTfBvZ69ddA== X-Google-Smtp-Source: APXvYqzpMNbiy51j6vtkjPuuhusjbti4CJFbH8pcmfYvGpawltJmnzSIwtrjLRWD8kgfIxeJjRT4UBofz6S6sUNLEa8= X-Received: by 2002:ac2:4345:: with SMTP id o5mr4806342lfl.60.1571224755662; Wed, 16 Oct 2019 04:19:15 -0700 (PDT) MIME-Version: 1.0 References: <20191008044153.12734-1-andrew@aj.id.au> In-Reply-To: <20191008044153.12734-1-andrew@aj.id.au> From: Linus Walleij Date: Wed, 16 Oct 2019 13:19:01 +0200 Message-ID: Subject: Re: [PATCH 0/7] pinctrl: Fixes for AST2600 support To: Andrew Jeffery Cc: "open list:GPIO SUBSYSTEM" , Rob Herring , Mark Rutland , Joel Stanley , linux-aspeed , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux ARM , "linux-kernel@vger.kernel.org" , johnny_huang@aspeedtech.com, ryanchen.aspeed@gmail.com Content-Type: text/plain; charset="UTF-8" Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Tue, Oct 8, 2019 at 6:41 AM Andrew Jeffery wrote: > This series resolves several issues found in testing by Johnny Huang from > ASPEED, who also contributed the patches to fix them. We'll have more patches > from him in the near future (which I'm pretty happy about). > > The major issue resolved is the way I grouped the eMMC pins. What I had was > ugly and I want to get rid of it before the binding is solidified with the 5.4 > release. Should some of these go in with fixes? All of them? Or just some? I applied them to devel right now (for v5.5). > The remaining fixes are minor issues that stem from lack of documentation or > understanding on my part, and at least one brain-fart. Do they need to go in to v5.4 or not? I need a shortlist of anything that should go into v5.4 if anything. Yours, Linus Walleij From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 05452FA372B for ; Wed, 16 Oct 2019 11:19:31 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id CF3212067B for ; Wed, 16 Oct 2019 11:19:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="I3Yabrth"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="ZE6OEgnZ" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CF3212067B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linaro.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=P6vmLLDTX1UVJqoBisc1TIEhojw8fFI7k1ZBuoiSPjg=; b=I3YabrthSlMtKB C8j1xM+t6NMbkWCuYF9GqaHFD5vueADQ/QNd3UC42omN4uqohOscX8UlFKu01GrCU7li26/yxortY znogxV6IN+2c5A3XRCyJjKUuFP6EiN5UbIhHssWs2VSCof839wTkg9ctf4x+b1qZTk2A0dOx4l60F vUDQ1/xBX9eKNTHLcmHm8ac0dQs1EM1yQaspoAj6uvt97ezrfPS0jRhjWzggdR9Q+llCZArJYVbim +veZPb5auymWda3ZPRFxAozP879hJFA/D9vIMY/bkL/lH7yvDLIC08sy1qw8h8ueath4cslXNoeVF 4NCCrfXLFgXXHtRPM3/g==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1iKhKr-0001iV-6o; Wed, 16 Oct 2019 11:19:21 +0000 Received: from mail-lf1-x144.google.com ([2a00:1450:4864:20::144]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1iKhKn-0001hg-LI for linux-arm-kernel@lists.infradead.org; Wed, 16 Oct 2019 11:19:18 +0000 Received: by mail-lf1-x144.google.com with SMTP id y127so17151560lfc.0 for ; Wed, 16 Oct 2019 04:19:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1AlVFzVNzLFhybDABbQIP7y9fwuWZqgdiTuBdrVDMgU=; b=ZE6OEgnZ8yrNuwOpjQUl1DrdrhOJcU/OfJQ+UWAJV5VSuBLt4kobSn90ZvkwKhz3/W DmWuNa8o4L6xpUpEA32J5Ft1QTqgjgdu1dbOpgk5naABVzkOtVTLGgWzYWNTzQ0WgTbb Y5niXn2s+/QyNMl5FrZPP125aQ4QKxA3TA4Lw+iuOCQIhfIOlJhBFdeOJIR1GZ+oDqDq hCnZiK17J2nBsS8Ybej2tVBY0I7+6EKSRi0R6PvzZFSb1ptl6XnMGK+lHRNew2QPY1xJ KNOCbpWsHgotFI3zRLMVcXg5iQytMnF3Gq7qsWWyjGRj8Jo3TTknxKUco7I816TsaM43 NMEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1AlVFzVNzLFhybDABbQIP7y9fwuWZqgdiTuBdrVDMgU=; b=XpRAskyROUDTpPqx10OG7SQ4MmMH1WgbH7DkHPZUQRGyVKT0PCUkiW8PnonowsuwFQ OrhVZ61GG0iaLYDBpsnrGmS3YanZ9+qkYsX4aNoOgy1IKkH7TGC8eapAgjX5bK2kUWs/ aY7CWG4FxwyzVS2/hwJxReGewG2iWGy7ows6u2mhK8k4xvTSxhXiJgUFugX41PR8y6x/ yt0qFnfdMKRQGWg0rHiK1Ub2cYrYKSoNQrTbO6clVhZGolM2O5KfXmK7agiYS4SN2D15 hnQ3KseI+a7SAQ0twOXAlDeMWql9juJQGkK+/v6UISr896HB6VIpLq7HiCDeTIK308Du uu4w== X-Gm-Message-State: APjAAAVIXDz+FqpNDjApLgeYQ0NbfP+evNGW7DUMmQWrP8GsgSjYPx5C 97g517SLjdiAr/7bbLJQjiRtTnjUZhecKNXTHAXTpA== X-Google-Smtp-Source: APXvYqzpMNbiy51j6vtkjPuuhusjbti4CJFbH8pcmfYvGpawltJmnzSIwtrjLRWD8kgfIxeJjRT4UBofz6S6sUNLEa8= X-Received: by 2002:ac2:4345:: with SMTP id o5mr4806342lfl.60.1571224755662; Wed, 16 Oct 2019 04:19:15 -0700 (PDT) MIME-Version: 1.0 References: <20191008044153.12734-1-andrew@aj.id.au> In-Reply-To: <20191008044153.12734-1-andrew@aj.id.au> From: Linus Walleij Date: Wed, 16 Oct 2019 13:19:01 +0200 Message-ID: Subject: Re: [PATCH 0/7] pinctrl: Fixes for AST2600 support To: Andrew Jeffery X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20191016_041917_697803_F3A88443 X-CRM114-Status: GOOD ( 11.74 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , johnny_huang@aspeedtech.com, linux-aspeed , ryanchen.aspeed@gmail.com, "linux-kernel@vger.kernel.org" , "open list:GPIO SUBSYSTEM" , Rob Herring , Joel Stanley , Linux ARM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Oct 8, 2019 at 6:41 AM Andrew Jeffery wrote: > This series resolves several issues found in testing by Johnny Huang from > ASPEED, who also contributed the patches to fix them. We'll have more patches > from him in the near future (which I'm pretty happy about). > > The major issue resolved is the way I grouped the eMMC pins. What I had was > ugly and I want to get rid of it before the binding is solidified with the 5.4 > release. Should some of these go in with fixes? All of them? Or just some? I applied them to devel right now (for v5.5). > The remaining fixes are minor issues that stem from lack of documentation or > understanding on my part, and at least one brain-fart. Do they need to go in to v5.4 or not? I need a shortlist of anything that should go into v5.4 if anything. Yours, Linus Walleij _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel