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=-3.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 236FBC6369E for ; Wed, 18 Nov 2020 15:27:26 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (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 96979207D3 for ; Wed, 18 Nov 2020 15:27:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="nXJszplL" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 96979207D3 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bootlin.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+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=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=TVvLORLWV/i70NfYTU/cqDkEEVkfM/5pBlT47jN7myw=; b=nXJszplLPzsPlTou7gyxxFhHi N3irW9drRu3OduIQDFcfvrjFN3BUinYgV/2PEOhHGwGUFLTOlxA7y0jbRVfywKbHUq1byJ5wWThMr EEy72u/5dY//GSr+o/eH5ZHsfeLKMjwq36KcDNBs1kRztpqaIbTWFGfLteCTjxEujRoJfV/5BA2tG C6OBqLcSVRnUZ7t/OgwxGV6+fxFYrMPAEuJgPO65LhOiAFDhZeLjtlvizjWsCzu0nsVj5f/o9LZ+w EfjVmuvacjSZlU2elWq5tFQjoL+MbIKoQuNpekdZU26vlIbYbYQKsFCfzqshI2raOgNmKEUns1RUD mrh/aM6jw==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kfPMK-0003XS-Aw; Wed, 18 Nov 2020 15:27:00 +0000 Received: from relay1-d.mail.gandi.net ([217.70.183.193]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kfPMH-0003WZ-DR for linux-arm-kernel@lists.infradead.org; Wed, 18 Nov 2020 15:26:58 +0000 X-Originating-IP: 86.194.74.19 Received: from localhost (lfbn-lyo-1-997-19.w86-194.abo.wanadoo.fr [86.194.74.19]) (Authenticated sender: alexandre.belloni@bootlin.com) by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id 0D22624000C; Wed, 18 Nov 2020 15:26:52 +0000 (UTC) Date: Wed, 18 Nov 2020 16:26:52 +0100 From: Alexandre Belloni To: Ludovic Desroches Subject: Re: [PATCH 0/3] ARM: dts: at91: add pincontrol node for USB Host Message-ID: <20201118152652.GA11581@piout.net> References: <20201118120019.1257580-1-cristian.birsan@microchip.com> <20201118150336.g3u3ljuhrbrn2cko@sekiro> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20201118150336.g3u3ljuhrbrn2cko@sekiro> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201118_102657_573075_A6ECD196 X-CRM114-Status: GOOD ( 13.43 ) 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: devicetree@vger.kernel.org, linus.walleij@linaro.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, robh+dt@kernel.org, cristian.birsan@microchip.com, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hello, On 18/11/2020 16:03:36+0100, Ludovic Desroches wrote: > At first glance, there is no trivial way to register the pin range in the > pinctrl-at91 driver. There is one driver for the pinctrl and one for the gpio. > I am open to suggestions to fix it in the pinctrl-at91 driver as well if there > is an elegant way (I have some in mind, but there are not) without having to > refactor the driver. > But shouldn't that driver be refactored at some point anyway? I know you are moving away with new SoCs but it causes real issues. For example, gpio hogs are not working, this is impacting some of your customers. The other thing is the weird probe order preventing a nice cleanup of the platform code. -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel