From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7E8E47C for ; Sat, 23 Apr 2022 21:31:47 +0000 (UTC) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 807475C00C3; Sat, 23 Apr 2022 17:31:46 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sat, 23 Apr 2022 17:31:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sholland.org; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; t=1650749506; x= 1650835906; bh=Dl4Gnii1lgQ3CuqDwJm6Ada66ZIg7WGp0sT4NijET4g=; b=a /iCwS1IcycZQFMyCZJPXqJBoDi8knnuTpxOkS0QNqrVgcZazrMU6me+qzJsNLN0g 6ymzf63HBnh7sRHkkTMA88xBNlbJp2eINv+C1qdAzTJmyAIdjEp1vAKnmchLPkil 7st52ELLVULgHo5NZu0PHf1D2m5D9pbJ7e/OBbri412iMIjDydqzPDhnCeBy3Fye kCvbHQFW69gIuWFYSw66bdUHIBG4o6aYlWQFY1U2H15/8J7uwBVLU1m1T8NCuJKi G9Dynumf2p4uBH151PT1+I377f5IJWocFXWCaCQakir9hZF8wd9p5addhVzPeokj gGoXKrbgPzq1+X+ZCdTJg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1650749506; x=1650835906; bh=Dl4Gnii1lgQ3C uqDwJm6Ada66ZIg7WGp0sT4NijET4g=; b=ZuZ36IQxtV8ZTl/R4Zxd9maMIyvZ7 EXZAaoMxtOVMr9V5aHrxcgRuwmlJQbcCcwx3K4a1sr2EkeR+W1XZ9GpdfP/iXJDq e8CuChhJWYNmZs/1NJ74bk/gixMYVqePKDZJmTXKqhhLdLpN5YNGPklgAs7CFgx3 jecvL+ZdgsOSgYcSClc+z8q87fCGYEuDXL7vrPVdQ2X1TJ+/+cppa66LiWketeJi k3oCUKbNyLr/KL82ie+ADOJA0phfY8ubidGMllxE4V2+ocruJN7Pij+fIX7ShnPR zYroca46yzjTtzkEhaaEsvEOLTDU68LmIcO+fKJqNpgHCISQSrcE8ws+g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrtdeigdduiedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvvehfhffkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefurghm uhgvlhcujfholhhlrghnugcuoehsrghmuhgvlhesshhhohhllhgrnhgurdhorhhgqeenuc ggtffrrghtthgvrhhnpeelteejffdvgeehkedtkeevueeuteffteffhedufeeujedvudef udetieeijeevleenucffohhmrghinhepkhgvrhhnvghlrdhorhhgnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepshgrmhhuvghlsehshhholhhl rghnugdrohhrgh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 23 Apr 2022 17:31:45 -0400 (EDT) Subject: Re: [PATCH 03/12] pinctrl: sunxi: add support for R329 R-PIO pin controller To: Icenowy Zheng Cc: Rob Herring , Chen-Yu Tsai , Jernej Skrabec , Ulf Hansson , Linus Walleij , Andre Przywara , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org, Icenowy Zheng References: <20220422140902.1058101-1-icenowy@aosc.io> From: Samuel Holland Message-ID: <5365b3af-a8c2-6f20-3ac1-6a4483ae2a52@sholland.org> Date: Sat, 23 Apr 2022 16:31:45 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 Precedence: bulk X-Mailing-List: linux-sunxi@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 4/22/22 10:41 AM, icenowy@outlook.com wrote: > From: Icenowy Zheng > > Allwinner R320 SoC has a pin controller in the CPUS power domain. This should be "R329". Also see my comments on the previous version, which still apply: https://lore.kernel.org/linux-sunxi/e9937a23-8a8a-ebec-0a44-0d15a06b7e89@sholland.org/ Regards, Samuel