Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp367967pxj;
        Fri, 11 Jun 2021 00:55:59 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJzEWQlWX9f6pcMhErPgeBqBuK00Li6Ho+v+Qelw2TCyRv60XOL7098jGSVIXEBpQ2+alRqw
X-Received: by 2002:a17:907:7848:: with SMTP id lb8mr2542976ejc.494.1623398158882;
        Fri, 11 Jun 2021 00:55:58 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1623398158; cv=none;
        d=google.com; s=arc-20160816;
        b=WoME3WYIr3G+9RKUrVYtJbWdcdCNN4p+1xmBIb2F/hE1rJQpLr4v3IKoGm9YN15Sgc
         4VKEF+6RKUW7tbPRUaUqq1PQqvVRONr2CNJCeeFlNdp4/EM+72l3tcXMWKqd8MY9gduY
         k243SftGfNXhYxaOxdarLk3nlO19ssihCDGBfT+QIsPn9q2ZHTmVrvPx1egDgYy4kLYA
         PS8Lx4h586pMDNFyWXJd3hkNr9s1cCVUZ/vNDAPZAZU25M21yAOS14g8SO0So6elSLOd
         qNQmHWgxOajZeDh9uZOfsP++EGIraku//SDrqj9i+sb8jw3ySwpg272H8VGDXzYCAW4C
         R3TA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:organization:in-reply-to:content-disposition
         :mime-version:references:message-id:subject:cc:to:from:date
         :ironport-sdr:ironport-sdr;
        bh=VULAZDb98zLqDMZBjTRkZqoQqd7SUCip9T4+aqbf3zU=;
        b=VoYsyxGajmTFnK7sJmnHAsq6o1eaCRMj1PiNL9jafoomFLHrGfqDWS2gkhKN8Aorfs
         gpxObWYPm0sW9SGp3knxQ5nb6pZBtEM1JhrKssfthNSdr/KUYmu+EXnuR/sL8YLasYje
         u/g/D+ZZtj5Q4cBHN61ZLxBZ8U2hUo13Rj3marbxOmMHrwutwTytNNofpM4qTnGD4/m4
         YRfSsIc53YEj0mb9RzSz15Po1AY8eHxo9xRa2JnSe+zkaoOLkDaaRRtkzTG/xg2JluwU
         vDxQyXUkQVaImrgFS6eVLfMtFwdq46A+5J8jp43qxnsQ52yIe4hiRL9YiUUt61DIeOQb
         aOJQ==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org;
       dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18])
        by mx.google.com with ESMTP id ck28si4459967edb.315.2021.06.11.00.55.35;
        Fri, 11 Jun 2021 00:55:58 -0700 (PDT)
Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org;
       dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S231284AbhFKHyz (ORCPT <rfc822;ly15351151@gmail.com> + 99 others);
        Fri, 11 Jun 2021 03:54:55 -0400
Received: from mga02.intel.com ([134.134.136.20]:46226 "EHLO mga02.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S231132AbhFKHyz (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 11 Jun 2021 03:54:55 -0400
IronPort-SDR: QjN74uPTYsuvLUf2xjNkV4O1Nbc8Hftbe7l40Vw8GpWeZ4yrPruTfV64lyOs37FtK9mxLO2DoU
 CoB/ZboSYcKQ==
X-IronPort-AV: E=McAfee;i="6200,9189,10011"; a="192591960"
X-IronPort-AV: E=Sophos;i="5.83,265,1616482800"; 
   d="scan'208";a="192591960"
Received: from fmsmga004.fm.intel.com ([10.253.24.48])
  by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Jun 2021 00:52:57 -0700
IronPort-SDR: 0/iQilxv405MBQIjcBmXiDqeFnA22qRIjx5bOMuE6qInGN3bI+hCagpBGUZSHowyXeIqdrzIA1
 3TuW9VNSgBjQ==
X-IronPort-AV: E=Sophos;i="5.83,265,1616482800"; 
   d="scan'208";a="470550810"
Received: from lahna.fi.intel.com (HELO lahna) ([10.237.72.163])
  by fmsmga004-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Jun 2021 00:52:54 -0700
Received: by lahna (sSMTP sendmail emulation); Fri, 11 Jun 2021 10:52:51 +0300
Date:   Fri, 11 Jun 2021 10:52:51 +0300
From:   Mika Westerberg <mika.westerberg@linux.intel.com>
To:     Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc:     linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
        Andy Shevchenko <andy@kernel.org>,
        Linus Walleij <linus.walleij@linaro.org>,
        Henning Schild <henning.schild@siemens.com>
Subject: Re: [PATCH v1 1/1] pinctrl: intel: Check against matching data
 instead of ACPI companion
Message-ID: <YMMWU1ZMqGoCKOoj@lahna>
References: <20210610152823.1653-1-andriy.shevchenko@linux.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210610152823.1653-1-andriy.shevchenko@linux.intel.com>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Jun 10, 2021 at 06:28:23PM +0300, Andy Shevchenko wrote:
> In some cases we may get a platform device that has ACPI companion
> which is different to the pin control described in the ACPI tables.
> This is primarily happens when device is instantiated by board file.

Can you point which board file in the mainline kernel has this issue? If
not then I don't think it makes sense to add code like this.