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=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 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 3C6C9C43462 for ; Mon, 10 May 2021 13:15:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0DCAA611CE for ; Mon, 10 May 2021 13:15:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233214AbhEJNOo (ORCPT ); Mon, 10 May 2021 09:14:44 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:44429 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348857AbhEJNKK (ORCPT ); Mon, 10 May 2021 09:10:10 -0400 Received: from mail-qt1-f199.google.com ([209.85.160.199]) by youngberry.canonical.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1lg5ei-0007hn-AH for linux-kernel@vger.kernel.org; Mon, 10 May 2021 13:09:04 +0000 Received: by mail-qt1-f199.google.com with SMTP id d13-20020a05622a05cdb02901c2cffd946bso10353318qtb.23 for ; Mon, 10 May 2021 06:09:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=3EZlfL7z84grZikXYl9bmKb5sE14hGf3dWPqG5s9Xqg=; b=b7EfMzsPTt8JKHijgaumd98oE+fo/0rID95htCRNwzhEy/zUaKH4iX7g2tdeKjnTCw h+a0PCnYtxLosIMAc03W6AYV7uY8Q3cNCbf+AMFT8tU/7ohSYf1k83S93x9k8PaKM0FY bnKjlDbg5zRybaVfsQALSxQus6AUTZwfTE0kJF8F9GeiRo7TXT2r8JPRY8AKqyGwhyzh u8ALHY5NR+5NdT3EoPY/JvT1xQP/mbzoSgcp7vkk4ER1u4gDbGxfGU2HWG7l33UEuRNO syNpV/B7B54Lf01x5hAPWqdEEQtny3fnAX1SezweoGFqplYxG/ivCOIXkGjeagQOoTbP 30Ag== X-Gm-Message-State: AOAM533rvtLnDQq598FgqYwTEGLVPurJbwaTu+wglF3/H6GHj0/RZxCZ vXDBIetIichhgttlbJeiicbldw4bIM/dzoo+802slrOAIc3OYb9YdCf1qiWNMJx9ZJIOZKBn9JN daEVPzKRiA+cVdwxKd9Eg59AAzDFocaRM9RU65UhKzA== X-Received: by 2002:a37:e50e:: with SMTP id e14mr22088280qkg.117.1620652143174; Mon, 10 May 2021 06:09:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwwLP9GlKtI1WyA/nxy7DLVZK7IgyXSKBIhEvh2JTEwD5ovaV0XsMxwD2P69LAwyJBXGELSqA== X-Received: by 2002:a37:e50e:: with SMTP id e14mr22088259qkg.117.1620652143029; Mon, 10 May 2021 06:09:03 -0700 (PDT) Received: from [192.168.1.4] ([45.237.49.6]) by smtp.gmail.com with ESMTPSA id u27sm3847415qku.33.2021.05.10.06.09.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 10 May 2021 06:09:02 -0700 (PDT) Subject: Re: [PATCH 1/2] dt-bindings: pinctrl: Add DT bindings for apple,pinctrl To: Tomasz Figa , Linus Walleij Cc: Mark Kettenis , kettenis@openbsd.org, Marc Zyngier , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Hector Martin , Rob Herring , Linux ARM , "open list:GPIO SUBSYSTEM" , linux-kernel , Bartosz Golaszewski , sven@svenpeter.dev References: <20210508142000.85116-1-kettenis@openbsd.org> <20210508142000.85116-2-kettenis@openbsd.org> From: Krzysztof Kozlowski Message-ID: Date: Mon, 10 May 2021 09:09:00 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/05/2021 05:50, Tomasz Figa wrote: >>>> So is this an entirely Apple thing now, and not based on some Samsung >>>> block from S3C like what we have seen before? >>> >>> As far as I can tell, yes. This Apple controller has a single >>> register per pin that controls the muxing and gpio functions, whereas >>> the S3C controller seems to have 4 registers per pin. >> >> Fair enough. >> > > Right, doesn't sound like any Samsung pin controller I'm familiar > with, although I haven't followed new hardware developments since I > left Samsung a few years ago. I've stayed as a maintainer mostly to > help with the legacy SoCs I had worked with, e.g. s3c6410. :) I can confirm that it looks different than Samsung designs. Best regards, Krzysztof