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 BFB73C54EBE for ; Mon, 16 Jan 2023 12:00:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230271AbjAPMAW (ORCPT ); Mon, 16 Jan 2023 07:00:22 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41600 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230265AbjAPL7x (ORCPT ); Mon, 16 Jan 2023 06:59:53 -0500 Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CFBE41F90D for ; Mon, 16 Jan 2023 03:59:26 -0800 (PST) Received: by mail-ej1-x62a.google.com with SMTP id ud5so67570051ejc.4 for ; Mon, 16 Jan 2023 03:59:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=3TbZE6s5T+iMHYdoGXhzWjy9v7YEHa+ewLj/SKxwHQ4=; b=fSiDlrmb9wRKi8MDOOibxscvUq5gYtW+itGe6V6dT3adhzRz04tS0jMlBlOraE6dKo 67c7Y8jbU+2UAbUkHtWNW7pMv1JM6vieXm6BAAQ17HykhbZnlYil2HzVXdl2q+VWPoNE juzSeHeFvm1D5UruUeY29UbmvYn3j5oJofSS9gwTGwjYbYBhzrEB4FJhuo5iSH/Sl6eI 8JFXX0a9TNQgpSg6C1Df0keh0firzgN3FncFYivG3rdZHoEFuHf9GPsvF6ENk/R21I0P DThn0WQbAJVaJ9q8cL/FEHji4t67yncx5PJPs/hLEdliQ8bPbh9RXn018tXFA+ryFKnw D0cA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=3TbZE6s5T+iMHYdoGXhzWjy9v7YEHa+ewLj/SKxwHQ4=; b=2ovAPVoFzj47uIvQVUIYubelmECtG3RCiORB48j+ydnC8rW7DSGgGz7y9ZrdBoHwO5 EDpEt+Ac2sG+kHg6OiXwntsBgjBlN3pF/CDTlNHkxLwBi9yalXxi7SMvD6WI1mCiqqRo 8an6TyrHPEQGUvX9uV3Xig4NhiVl0cBsYCnw4Lbs0yvGWPSfaaTGrd0xogue6IbcdWtI q87f+fddhizVu4O5c8WWrEL2vLCntGDPXcWlAHcCO+ljyAMXN3jNtZsAWf6VrPB6sBlN m0Pw/jzsihjZodtqDHHInITCm8DTo3IU1ijYxg1ywmeT026Nhxuhxz60XTdfTzdFXyY/ npTg== X-Gm-Message-State: AFqh2kr/c3+EKyWMhBJfZujqrIjYgshJQBDF4TTR3TC8A/5V1Znlsb31 KMhR/vBelJr96t/Bc+SZ6vlVg9Z8dPpxPwDB X-Google-Smtp-Source: AMrXdXtOGYZiC+nvulbQhp3KktJk4riiE9SfEAy5zB73TBUbhQkIvOcsunA0sCmf+GVZXqpAxzPICQ== X-Received: by 2002:a17:907:8c0d:b0:7c1:d50:6dd3 with SMTP id ta13-20020a1709078c0d00b007c10d506dd3mr79542070ejc.36.1673870365378; Mon, 16 Jan 2023 03:59:25 -0800 (PST) Received: from [192.168.1.109] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id l10-20020a1709060cca00b0082ddfb47d06sm11885662ejh.148.2023.01.16.03.59.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 16 Jan 2023 03:59:25 -0800 (PST) Message-ID: <76f3a771-2283-4e6e-d3b8-fdfcf1f4291f@linaro.org> Date: Mon, 16 Jan 2023 12:59:23 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH v2.1 02/17] dt-bindings: media: fsl-pxp: convert to yaml Content-Language: en-US To: Michael Tretter , linux-media@vger.kernel.org, devicetree@vger.kernel.org, Philipp Zabel , Laurent Pinchart Cc: Mauro Carvalho Chehab , Rob Herring , Krzysztof Kozlowski , Fabio Estevam , Alexander Stein , kernel@pengutronix.de, linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org References: <20230112-imx-pxp-v2-1-e2281da1db55@pengutronix.de> <20230116113856.1445078-1-m.tretter@pengutronix.de> From: Krzysztof Kozlowski In-Reply-To: <20230116113856.1445078-1-m.tretter@pengutronix.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 16/01/2023 12:38, Michael Tretter wrote: > Convert the bindings of the Freescale Pixel Pipeline to YAML. > > The conversion drops the previously listed compatibles for several SoCs. > It is unclear, if the PXP on these SoCs is compatible to any of the PXPs > on the existing SoCs and would allow to reuse the already defined > compatibles. The missing compatibles should be brought back when the > support for the PXP on these SoCs is added. > > Reviewed-by: Laurent Pinchart > Reviewed-by: Philipp Zabel > Signed-off-by: Michael Tretter > --- > Changelog: > > v2: > > - add fsl,imx6sll-pxp and fsl,imx6sx-pxp compatibles > - restrict number of interrupts per variant > - cleanup syntax > > v2.1: > > - use enum for compatibles > - add power-domains property > - fix syntax for specifying the required number of interrupts > - fix number of interrupts for fsl,imx6ul-pxp Attaching some half-baked patch to existing thread is not the way. It might not be supported by workflows at all (b4, patchwork), it messes with threads. Don't do it. Send a v3 of entire patchset once you collect proper feedback. Reviewed-by: Krzysztof Kozlowski Best regards, Krzysztof