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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D58B6C77B7C for ; Thu, 4 May 2023 05:52:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229668AbjEDFwC (ORCPT ); Thu, 4 May 2023 01:52:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55150 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229659AbjEDFwB (ORCPT ); Thu, 4 May 2023 01:52:01 -0400 Received: from muru.com (muru.com [72.249.23.125]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 828701731; Wed, 3 May 2023 22:51:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id CE41680C1; Thu, 4 May 2023 05:51:57 +0000 (UTC) Date: Thu, 4 May 2023 08:51:56 +0300 From: Tony Lindgren To: Andreas Kemnade Cc: Aaro Koskinen , linux-omap@vger.kernel.org, linux-gpio@vger.kernel.org, Bartosz Golaszewski , linux-kernel@vger.kernel.org, Linus Walleij Subject: Re: [BISECTED REGRESSION] OMAP1 GPIO breakage Message-ID: <20230504055156.GO14287@atomide.com> References: <20230425173241.GF444508@darkstar.musicnaut.iki.fi> <20230425201117.457f224c@aktux> <20230425183857.GG444508@darkstar.musicnaut.iki.fi> <20230425212040.5a4d5b09@aktux> <20230425193637.GH444508@darkstar.musicnaut.iki.fi> <20230425215848.247a936a@aktux> <20230426071910.GE14287@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230426071910.GE14287@atomide.com> Precedence: bulk List-ID: X-Mailing-List: linux-omap@vger.kernel.org * Tony Lindgren [230426 07:20]: > Seems that we should just revert this patch for now and try again after > the issues have been fixed. Looking at the proposed fixes being posted seems like they are quite intrusive.. How about we partially revert this patch so omap1 still uses static assigment of gpios? This way the later SoCs can avoid the warnings and the legacy board file and driver changes can get merged during the next merge window. Regards, Tony