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=-16.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 0FD1EC56202 for ; Thu, 26 Nov 2020 17:46:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B06A721D7F for ; Thu, 26 Nov 2020 17:46:23 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="nAacdcqv" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404489AbgKZRqG (ORCPT ); Thu, 26 Nov 2020 12:46:06 -0500 Received: from mail.kernel.org ([198.145.29.99]:40436 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2403877AbgKZRqF (ORCPT ); Thu, 26 Nov 2020 12:46:05 -0500 Received: from mail-ej1-f43.google.com (mail-ej1-f43.google.com [209.85.218.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A735321D81; Thu, 26 Nov 2020 17:46:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1606412765; bh=fyJHGLRkPZJEpMLdSXJSRtm+BxF+vyx330eISFxAeu0=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=nAacdcqv3vuvKHUe5JctwDywjxu4UCDFQMjTws7kNRUOFnaCRcBPFwjKCggbFEEKu QsTkwKNORE9diKCKDKNVNyP4SnQrRnYaLOJBqBK5IfpYe0PJTaEd+Zf1EE5xnmR3Yj 6/CG9NTx9VZJil7lnQbVWrS+e7pYWVyY3kx5FB6U= Received: by mail-ej1-f43.google.com with SMTP id f9so1836543ejw.4; Thu, 26 Nov 2020 09:46:04 -0800 (PST) X-Gm-Message-State: AOAM531t77Rm2KyAmq2WF01CT7N7m2MLCm31RoDfaGmydYWSXPQx6jpl sc4VIzWGhikih8GHNVCCIReraLb/fyVgZbZT5F0= X-Google-Smtp-Source: ABdhPJySK2fWPNkkM5b6roHtaPGIS+dT06U+qMA2Q7ghOf7qik1PlIxU6ky2ZKUepWH1qNCM2fQckwm1YaXARvChzK4= X-Received: by 2002:a17:906:c298:: with SMTP id r24mr3653647ejz.381.1606412763243; Thu, 26 Nov 2020 09:46:03 -0800 (PST) MIME-Version: 1.0 References: <20201104164923.21238-1-digetx@gmail.com> <20201104164923.21238-18-digetx@gmail.com> <20201126173922.GA7048@kozik-lap> In-Reply-To: <20201126173922.GA7048@kozik-lap> From: Krzysztof Kozlowski Date: Thu, 26 Nov 2020 18:45:51 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v7 17/47] dt-bindings: memory: tegra20: Add memory client IDs To: Thierry Reding Cc: Dmitry Osipenko , Jonathan Hunter , Georgi Djakov , Rob Herring , Michael Turquette , Stephen Boyd , Peter De Schrijver , MyungJoo Ham , Kyungmin Park , Chanwoo Choi , Mikko Perttunen , Viresh Kumar , Peter Geis , Nicolas Chauvet , linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org, "linux-kernel@vger.kernel.org" , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-tegra@vger.kernel.org On Thu, 26 Nov 2020 at 18:39, Krzysztof Kozlowski wrote: > > On Thu, Nov 26, 2020 at 06:26:05PM +0100, Thierry Reding wrote: > > On Wed, Nov 04, 2020 at 07:48:53PM +0300, Dmitry Osipenko wrote: > > > Each memory client has unique hardware ID, add these IDs. > > > > > > Acked-by: Rob Herring > > > Signed-off-by: Dmitry Osipenko > > > --- > > > include/dt-bindings/memory/tegra20-mc.h | 53 +++++++++++++++++++++++++ > > > 1 file changed, 53 insertions(+) > > > > Is there any chance you could drop these dt-bindings include patches > > (17, 18 and 19) so that I can pick them up into the Tegra tree? The > > device tree changes that I was going to pick up depend on this and > > fail to build if applied as-is. > > > > I was looking at your linux-mem-ctrl tree and had initially thought I > > could just pull in one of the branches to get these dependencies, but it > > looks like the dt-bindings patches are on the for-v5.11/tegra-mc branch, > > which the ARM SoC maintainers wouldn't like to see me pull in for a > > dependency on device tree changes. > > Partially you answered here. :) Since you should not pull my branch into > a DT branch, you also should not put these include/dt-bindings patches > there. SoC guys will complain about this as well. > > These patches are also needed for the driver, so if you take them, I > would need them back in a pull request. SoC folks could spot it as well > and point that such merge should not happen. It seems I was wrong - these patches are not needed for the driver code. Neither in applied parts nor in upcoming Dmitry's work. In such case I could rework my branches and send a new pull request. The patches would stay only in your tree. Best regards, Krzysztof 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=-13.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 7AF69C64E75 for ; Thu, 26 Nov 2020 17:46:08 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (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 20CD421D7E for ; Thu, 26 Nov 2020 17:46:07 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="nAacdcqv" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 20CD421D7E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 21EFD6E9B0; Thu, 26 Nov 2020 17:46:07 +0000 (UTC) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by gabe.freedesktop.org (Postfix) with ESMTPS id 5D2CF6E9B0 for ; Thu, 26 Nov 2020 17:46:05 +0000 (UTC) Received: from mail-ej1-f44.google.com (mail-ej1-f44.google.com [209.85.218.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A710421D7E for ; Thu, 26 Nov 2020 17:46:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1606412765; bh=fyJHGLRkPZJEpMLdSXJSRtm+BxF+vyx330eISFxAeu0=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=nAacdcqv3vuvKHUe5JctwDywjxu4UCDFQMjTws7kNRUOFnaCRcBPFwjKCggbFEEKu QsTkwKNORE9diKCKDKNVNyP4SnQrRnYaLOJBqBK5IfpYe0PJTaEd+Zf1EE5xnmR3Yj 6/CG9NTx9VZJil7lnQbVWrS+e7pYWVyY3kx5FB6U= Received: by mail-ej1-f44.google.com with SMTP id lt17so4053016ejb.3 for ; Thu, 26 Nov 2020 09:46:04 -0800 (PST) X-Gm-Message-State: AOAM532aszo1NwWmaWOQZNPkRWks3iQTDqrmi0Eb5nsImJmCrlbM9nQg IgGa/NUpTMifGxXngPp6A+XrQDmRSMEll8m2q38= X-Google-Smtp-Source: ABdhPJySK2fWPNkkM5b6roHtaPGIS+dT06U+qMA2Q7ghOf7qik1PlIxU6ky2ZKUepWH1qNCM2fQckwm1YaXARvChzK4= X-Received: by 2002:a17:906:c298:: with SMTP id r24mr3653647ejz.381.1606412763243; Thu, 26 Nov 2020 09:46:03 -0800 (PST) MIME-Version: 1.0 References: <20201104164923.21238-1-digetx@gmail.com> <20201104164923.21238-18-digetx@gmail.com> <20201126173922.GA7048@kozik-lap> In-Reply-To: <20201126173922.GA7048@kozik-lap> From: Krzysztof Kozlowski Date: Thu, 26 Nov 2020 18:45:51 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v7 17/47] dt-bindings: memory: tegra20: Add memory client IDs To: Thierry Reding X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Peter De Schrijver , Mikko Perttunen , Nicolas Chauvet , Stephen Boyd , Viresh Kumar , Michael Turquette , linux-pm@vger.kernel.org, "linux-kernel@vger.kernel.org" , dri-devel@lists.freedesktop.org, Jonathan Hunter , Chanwoo Choi , Kyungmin Park , Rob Herring , MyungJoo Ham , Peter Geis , linux-tegra@vger.kernel.org, Dmitry Osipenko , Georgi Djakov , devicetree@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Thu, 26 Nov 2020 at 18:39, Krzysztof Kozlowski wrote: > > On Thu, Nov 26, 2020 at 06:26:05PM +0100, Thierry Reding wrote: > > On Wed, Nov 04, 2020 at 07:48:53PM +0300, Dmitry Osipenko wrote: > > > Each memory client has unique hardware ID, add these IDs. > > > > > > Acked-by: Rob Herring > > > Signed-off-by: Dmitry Osipenko > > > --- > > > include/dt-bindings/memory/tegra20-mc.h | 53 +++++++++++++++++++++++++ > > > 1 file changed, 53 insertions(+) > > > > Is there any chance you could drop these dt-bindings include patches > > (17, 18 and 19) so that I can pick them up into the Tegra tree? The > > device tree changes that I was going to pick up depend on this and > > fail to build if applied as-is. > > > > I was looking at your linux-mem-ctrl tree and had initially thought I > > could just pull in one of the branches to get these dependencies, but it > > looks like the dt-bindings patches are on the for-v5.11/tegra-mc branch, > > which the ARM SoC maintainers wouldn't like to see me pull in for a > > dependency on device tree changes. > > Partially you answered here. :) Since you should not pull my branch into > a DT branch, you also should not put these include/dt-bindings patches > there. SoC guys will complain about this as well. > > These patches are also needed for the driver, so if you take them, I > would need them back in a pull request. SoC folks could spot it as well > and point that such merge should not happen. It seems I was wrong - these patches are not needed for the driver code. Neither in applied parts nor in upcoming Dmitry's work. In such case I could rework my branches and send a new pull request. The patches would stay only in your tree. Best regards, Krzysztof _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel