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=-11.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable 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 8156DC6379F for ; Fri, 20 Nov 2020 10:12:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2914F22272 for ; Fri, 20 Nov 2020 10:12:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="XUGzQTO7" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727531AbgKTKLx (ORCPT ); Fri, 20 Nov 2020 05:11:53 -0500 Received: from mail.kernel.org ([198.145.29.99]:37908 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726122AbgKTKLx (ORCPT ); Fri, 20 Nov 2020 05:11:53 -0500 Received: from localhost (unknown [122.171.203.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 307AF22272; Fri, 20 Nov 2020 10:11:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1605867112; bh=oRF6mylMSIwIrnp3jROSzpmjuKuj4N8/pJejw/abE4E=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=XUGzQTO74JOY2cw/14EwGbV2iYSx5Xwk+O53czUoG/H6OmbX5fWBz3ZfJz/0z4OSX jOKBuQRIINCJlDvmDzkyA+LqABBA45Nws6GL3sbonDoJyyU4/F7FuGIQdcwmbWcA2K WrNo68KxOxOnzV4b2vpLaMoro9vhVSu+0iZtVxe8= Date: Fri, 20 Nov 2020 15:41:38 +0530 From: Vinod Koul To: Marek Szyprowski Cc: linux-samsung-soc@vger.kernel.org, linux-pci@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Jaehoon Chung , Jingoo Han , Krzysztof Kozlowski , Bjorn Helgaas , Lorenzo Pieralisi , Kishon Vijay Abraham I , Rob Herring , Bartlomiej Zolnierkiewicz Subject: Re: [PATCH v4 4/5] phy: samsung: phy-exynos-pcie: rework driver to support Exynos5433 PCIe PHY Message-ID: <20201120101138.GI2925@vkoul-mobl> References: <20201113170139.29956-1-m.szyprowski@samsung.com> <20201113170139.29956-5-m.szyprowski@samsung.com> <20201120094152.GC2925@vkoul-mobl> <8eaebd62-345f-4d13-1b65-055a2acc68bd@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8eaebd62-345f-4d13-1b65-055a2acc68bd@samsung.com> Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On 20-11-20, 10:58, Marek Szyprowski wrote: > Hi Vinod, > > On 20.11.2020 10:41, Vinod Koul wrote: > > On 13-11-20, 18:01, Marek Szyprowski wrote: > >> From: Jaehoon Chung > >> > >> Exynos5440 SoC support has been dropped since commit 8c83315da1cf ("ARM: > >> dts: exynos: Remove Exynos5440"). Rework this driver to support PCIe PHY > >> variant found in the Exynos5433 SoCs. > > I am expecting this series to go thru PCI tree, so: > > > > Acked-By: Vinod Koul > > Frankly, the PHY driver can also go via PHY tree without causing any > issue. The old driver is not used at all, so there is no runtime > dependency. This will help avoiding the merge conflict: yesterday I've > noticed that this patch conflicts with the commit 2f0c9fac3be6 ("phy: > samsung: convert to devm_platform_ioremap_resource") in phy-next. The > resolution is simple (use all the code from the new driver), but if > needed I can resend the PHY driver after a rebase onto the current next > tree. Okay do send me the rebase patch Thanks -- ~Vinod