Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp1446136ybd; Wed, 26 Jun 2019 18:09:31 -0700 (PDT) X-Google-Smtp-Source: APXvYqwgg6dJezkWf9B5H36I6znVaGZZzkPyG6i1HxWvmC8ka1YTw5SNO4Q1aIscMOLkP+RraUOC X-Received: by 2002:a17:90a:b30a:: with SMTP id d10mr2584034pjr.8.1561597771284; Wed, 26 Jun 2019 18:09:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561597771; cv=none; d=google.com; s=arc-20160816; b=H7I5he5+QaLecUoyRZt6RHndlin0HZyUDKRQox3IZDyXRdDXnPhC9T1KRnYvCHsZDY oFkq4dKncts07d1Sthhk1VumeBJHXC3kuMlKT4896ecJCHV/3uETUCAGlEB81AShv9I1 McvjOvwr4uaq5j/t5Ag/JmvTwppGTqBZN+98fBRjF1q2s4YBDT1nVngzFfAe3zlLQmVo UER+TeJRiy8uihUJB3uri0opENW0R+u8+gxdzVo8RylMJBsXW+GiPOUjKFNi8OVn19fC H+d/j2KmgxhbKu73msQOgOhyrj4nN7S2rmFUdoD7Dw25xxispfus40NwV4JYIbTWZRJ1 LrpQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:subject:cc:to:from:date:references :in-reply-to:message-id:mime-version:user-agent:dkim-signature :dkim-signature; bh=ZiI3xxfYKmvDILJvqB7fVk8L/I2NP9dzhcO3iE+B9zo=; b=N3nlY/naSdgJElRHOF3h5KDxXhzdKgK5czwT7YkDEeX74QDGCr4Vob75Je6suIWAzP E3Krx17c0jZzwp29jYwIOJci4rMN3LQuGU2/Cwo4eF5lNAz61Q9Zu+S1kICv+blgvBqv QofF96xm2Sy6N4Y8bzakiVuRwbRxGLVUFUl8Eqe5MTryoF2/UDF7qVvYFYQIKKHczxMG 5gsGs70q5XTrLPU+S5HRerUOfyRp65Mhh670c1XLz0rgPFVOfDaAhPyUiSI1SWEj+/AS zccsB/yhiWt05FX3cyp5jx+abD2iFNh0Rf5BR1V4YwMSFAzaGP76c0BErCHbjjj0mu+B SKng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm3 header.b=BrQd3vXr; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=x28MdS6a; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v19si693509plo.404.2019.06.26.18.09.15; Wed, 26 Jun 2019 18:09:31 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm3 header.b=BrQd3vXr; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=x28MdS6a; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726926AbfF0BIs (ORCPT + 99 others); Wed, 26 Jun 2019 21:08:48 -0400 Received: from new1-smtp.messagingengine.com ([66.111.4.221]:51011 "EHLO new1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726748AbfF0BIs (ORCPT ); Wed, 26 Jun 2019 21:08:48 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id C99512212; Wed, 26 Jun 2019 21:08:46 -0400 (EDT) Received: from imap2 ([10.202.2.52]) by compute4.internal (MEProxy); Wed, 26 Jun 2019 21:08:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aj.id.au; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm3; bh=ZiI3xxfYKmvDILJvqB7fVk8L/I2NP9d zhcO3iE+B9zo=; b=BrQd3vXrWK9cQIP8itJI4yLnYhOACmlwPP91fUYKHYbtLHN 0ogcNMGV9W8splCz6t+XZdCMVtGizKYBnKF6spbmNMI1eNJ6r+zmg0k/+6d1W4q7 +k6I7itFCu1bItE/yvKsMYtBMQbyf7ltQhuQNYElu9gTFj+zsRAICpm4ZS3tjhSO 8KyHLX8mudpz7eKttQhCLCyBwkrhEGeoJnAWoKEEPhEBLvIUpP4H96wTd8IEJ2ZZ LX5xaOVrj7Rhsd0+tt7yoGhVBceeevSXkUP0PmG4wUmk0duMN1c4jl9K34kW1Pta 3zBsro14GpbO11VWv70wehz/6gPZQ0EQNjl1Piw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=ZiI3xx fYKmvDILJvqB7fVk8L/I2NP9dzhcO3iE+B9zo=; b=x28MdS6aAMJjnWtjtB7WWg 2siByivl2x8w5XEtXmNUvuYl+f7lY2HcDQ86cOF1asYgl4kcNcg1cZt4i7zxB5jt QLsmQfxgwN/OVfIho5k3aZXV16b3jTI9CGMsq+mLV2Mw+Cru7l+nAhf6g6scykvS CyOmU//+0e1r94HNCD1RhlilF5TDfmJxqfxE6RufpkkVCZOakaa4O1t0F9bog91/ dsylEeldN0KuO6YCmLCDGMdG5MVJSV7fIU6bJdjmwrepQbWMvRtZOsjWqPt5BYIe Tr2y1WFdqUMW48LKh7xQOcYHCDELGsFjj0dIFABn9Z9DM3Z8p7qh4W+IeQt01QsA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudejgdeggecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedftehnughr vgifucflvghffhgvrhihfdcuoegrnhgurhgvfiesrghjrdhiugdrrghuqeenucfrrghrrg hmpehmrghilhhfrhhomheprghnughrvgifsegrjhdrihgurdgruhenucevlhhushhtvghr ufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id CAAE4E00A2; Wed, 26 Jun 2019 21:08:44 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-730-g63f2c3b-fmstable-20190622v1 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <20190626071430.28556-1-andrew@aj.id.au> Date: Thu, 27 Jun 2019 10:38:44 +0930 From: "Andrew Jeffery" To: "Linus Walleij" Cc: "open list:GPIO SUBSYSTEM" , "Ryan Chen" , "Rob Herring" , "Mark Rutland" , "Joel Stanley" , linux-aspeed@lists.ozlabs.org, "OpenBMC Maillist" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "Linux ARM" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 0/8] pinctrl: aspeed: Preparation for AST2600 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 26 Jun 2019, at 17:25, Linus Walleij wrote: > On Wed, Jun 26, 2019 at 9:15 AM Andrew Jeffery wrote: > > > The ASPEED AST2600 is in the pipeline, and we have enough information to start > > preparing to upstream support for it. This series lays some ground work; > > splitting the bindings and dicing the implementation up a little further to > > facilitate differences between the 2600 and previous SoC generations. > > All looks good to me, but Rob should have a glance at the DT bindings > and YAML syntax before I proceed to apply them. Thanks for the quick review. Rob's responded, looks like I'll need to send a v2 at least. Might need a hand sorting out describing generic pinctrl dt bits (subnodes with function and group properties). Cheers, Andrew