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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 5580CC3DA64 for ; Tue, 6 Aug 2024 14:36:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=fGtGysqRw2M+SB4BHIAeHaD7D+DJXET7byhHYZ12njk=; b=bKv7+02g9txz0GSipF0DME4W2b xZ5VzA4MW4qLq7dxNqyKwdLO0C0Nys5NThHtp79FEfse3QTB+gJ2B0LXXVQ/jsaEA4EwT2UVh6cBb cE5rY1/s709ZSSkdjBN+92wUH5y5AFGvFXtG2EMHLuTcKRYUmpJIs3p57EnIxDm1kVtP0dFKeEq4f DOm9TIxhct5Ud63BQm2SPesgCx27Z/UQlwMXFV0F1sQ1qyJcE4UHq0qi3NmaehB6Zd2F34CLntyGe apBFj6WkLlDFjWt5KgEA0NvmTZmauRySIH4RAIA4OYvV4AVQGRU0RnUr5KbK+PwhL3QtcjI0bxu5O 50+1eSOA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sbLIC-00000001zAl-0Laf; Tue, 06 Aug 2024 14:36:04 +0000 Received: from mail11.truemail.it ([217.194.8.81]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sbLHe-00000001z29-0Jft for linux-arm-kernel@lists.infradead.org; Tue, 06 Aug 2024 14:35:32 +0000 Received: from francesco-nb (93-49-2-63.ip317.fastwebnet.it [93.49.2.63]) by mail11.truemail.it (Postfix) with ESMTPA id 98A3220284; Tue, 6 Aug 2024 16:35:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dolcini.it; s=default; t=1722954924; bh=fGtGysqRw2M+SB4BHIAeHaD7D+DJXET7byhHYZ12njk=; h=From:To:Subject; b=cE+AUJ4qwRpoqscFcQYUl597p/+2xAYsBs0yS78ta+rfpc83a74oRDlV1dp0+C83m dphzyJryQhUYJJRO6jufn6x8Glz9z244tud7rZUnVy9f8WmjMNpUZulOBvWbzm6J5I MywqLZ1LhltSIoK5m/addWAtXzZYDeKkDjuYJH3WBiuBaqdVsVllmiz7QmY3UxX6vK g40oXQfHt29ufPMte6s4UJkLWfN43sNWzL7gd18mgAV2V02Fh82aw8nhNnBKxHHo5x LMTIG6NT2QZocJ3ora97d7bdjngueLyRv1ccY+c83wmwiR1L/p3l0IgOGct5jHOG5p kCM4a2JV4zZtA== Date: Tue, 6 Aug 2024 16:35:19 +0200 From: Francesco Dolcini To: Francesco Dolcini , Lorenzo Pieralisi , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Bjorn Helgaas Cc: Nishanth Menon , Vignesh Raghavendra , Tero Kristo , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Siddharth Vadapalli , Francesco Dolcini , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, linux-pci@vger.kernel.org Subject: Re: [PATCH v1 0/2] PCI: ti: k3: Fix TI J721E PERST# polarity Message-ID: <20240806143519.GA176293@francesco-nb> References: <20240703100036.17896-1-francesco@dolcini.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240703100036.17896-1-francesco@dolcini.it> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240806_073531_023936_544F984E X-CRM114-Status: GOOD ( 11.18 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hello Bjorn, Krzysztof W., Lorenzo On Wed, Jul 03, 2024 at 12:00:34PM +0200, Francesco Dolcini wrote: > From: Francesco Dolcini > > Fix PCIe PERST# signal polarity in TI J721E used on TI K3 machines. > > PCIe PERST# needs to be de-asserted for PCIe to work, however, the driver is > doing the opposite and the device tree files are defining the signal with the > wrong polarity to cope with that. Fix both the driver and the affected DT > files. I just had a chat in IRC about this series with Nishanth. He agrees that this should be merged, even considering that this implies breaking the compatibility with old device tree blobs. However we should be sure that both patches get merged in a coordinated way, to avoid breaking stuff within the same kernel release. What would be your advise to move forward? Are you ok with the change? Should I split this series in 2 separated patch? Francesco