Message ID | 20231205092229.19135-1-krzysztof.kozlowski@linaro.org |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:bcd1:0:b0:403:3b70:6f57 with SMTP id r17csp3307116vqy; Tue, 5 Dec 2023 01:22:53 -0800 (PST) X-Google-Smtp-Source: AGHT+IHVUPBE9MtXCN7CftH7F7P35hPOs1Z1vf/lwmxb/KevVgr06BnGM3c2fX0MJ8PTti6vD43m X-Received: by 2002:a17:90a:df15:b0:286:b47b:a5cd with SMTP id gp21-20020a17090adf1500b00286b47ba5cdmr680299pjb.98.1701768172818; Tue, 05 Dec 2023 01:22:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1701768172; cv=none; d=google.com; s=arc-20160816; b=xYzKE7+qonkAj3CfWfh7fZEqxJg5Nuv/FP5d0s6gNRiDsu5ZFYMqI+RaldlcGZCXcX joO7gX7EnA7q0hR/SBZQV2JOdZh1LDhQVS4i6sIccvwoLxJS0z7QoI8bOgFXbRATeK06 dMZWi2pPSczjDyS2+A348vZ6ikRcK2EF9rVmGqSqOE4ch6EavRRduXyGkIuTUhxVxmVF 2XJZvE1y7Lc4FOvsAaZKjos2F+r38Dh84HRQPxLpH2pTyyVjInME574UsXCwTXc7t3El LI6A75T3rmROPpM4Hvvy661RkCNNXZ+XaJxq9AF9FUGAg4WeM+CPo8M383uxTllvMQUX 8urg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=3C3srF3D8XYNvvxDZciqMxRHu1Pp1JgH8p2QBUBIXkw=; fh=AilG5DwEGuLqGl78/1nxyk0W4Li6L5QGIzTBumtkZas=; b=eXd3yWa/FUZhXKMirJ3gtxHbYgougLEfWW7ywoC83cA4l+xvhZ3j7kbXdklrpwDLqx LWCDPi1LPotM6uFRRbTG8bJBT217q8zmXWI5uts4Kys4bgzUYacCUEqPPYtmBIfUBQ29 OyROw465p92WwEfjkE8kGPT1Allg6ZhsDAZkIoHRShdbTKVUhV8A4L6JJCEv3VjF81N1 EqTtdlg96/OqW5roxGrVCB6/gbuqQaYCzL1pYY2giTGt7A6fwlDlhGZS9mY7LrCcSayS Yirnj/WEllvquIH5NULcFvWHM3BlaGRQdP1W1h/+HfuH2oLEjbH1g1EXRHaPxobvJzNw G/TQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=LbYbJvKC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: from groat.vger.email (groat.vger.email. [23.128.96.35]) by mx.google.com with ESMTPS id a14-20020a17090a70ce00b0028555ec82easi861208pjm.57.2023.12.05.01.22.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 Dec 2023 01:22:52 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) client-ip=23.128.96.35; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=LbYbJvKC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by groat.vger.email (Postfix) with ESMTP id A34C780A367D; Tue, 5 Dec 2023 01:22:46 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at groat.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234986AbjLEJWg (ORCPT <rfc822;chrisfriedt@gmail.com> + 99 others); Tue, 5 Dec 2023 04:22:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37562 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229980AbjLEJWc (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 5 Dec 2023 04:22:32 -0500 Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0BB71C9 for <linux-kernel@vger.kernel.org>; Tue, 5 Dec 2023 01:22:38 -0800 (PST) Received: by mail-wm1-x32c.google.com with SMTP id 5b1f17b1804b1-40c039e9719so34045185e9.1 for <linux-kernel@vger.kernel.org>; Tue, 05 Dec 2023 01:22:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1701768156; x=1702372956; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=3C3srF3D8XYNvvxDZciqMxRHu1Pp1JgH8p2QBUBIXkw=; b=LbYbJvKCyoR0fX5rvZXjbtu4Ybw/+a5FWhP1PP6BbHfKYbo5BNkewJ+hgygNuMbbfb /qMnER1RBlOQZrXr+KCsjIxu5BJOdE6ohdZDTv84hM1FRbKSPCf0sB/cDoB4gae9pBow P05/prW4TiUa6aQci9KMzvPu+MxruHziMYlf7TLGh/oFUGnRgaEDSHpQfwDvBSlee2/X SG7jSv7QkvV14QuPqcEC+sufy2rkeeb52uBzur/jTGQVDJiEPB4OT6fEJJqtApV2QPMd cupxxeuzX2AnkuogDC6qeh8KNyvRHVfpKLagAxtExy//vrFEowHSEaWJ6zzG2qt82ege pvvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701768156; x=1702372956; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3C3srF3D8XYNvvxDZciqMxRHu1Pp1JgH8p2QBUBIXkw=; b=knHtO0KEPEvifPUWX7PgM0LDo9K0cin4S3uTpZ6AYmCokkNXkZaO/IYqOrOdcla9St 36xIS0T7ku8sREi2XT4DADN68VrgrOGyDJC/v9u6uwgnP4U/S8v9soM+7kbXt52shQCP gZIpCjd8INiG9cTaTsY63pm0EkHtDSNkxh5IumiqwUNm/KarYC/FjpiPM276zGtc65ZO FYG0DRa8aM7+ENNEkU5HIO4dEbxVaJcdn9GfgwX6NsVemeaIvR3np0gVO2mD4JdmOpMM kvLL2/N6h0FfAof8T4syvqwSUYuJK7g04xpAPTiyJr83DEc4dj7c++VNBXyplvAonFhg 3b2g== X-Gm-Message-State: AOJu0YzpumNnUfOtRTjbsD2B0iL0PfO1/dQaMkV5o4L4mXKu8ZUtBFNq a+S8wcsWVRATyBNNRWKtEtNjng== X-Received: by 2002:a05:600c:1d83:b0:40b:5e21:ec3e with SMTP id p3-20020a05600c1d8300b0040b5e21ec3emr277886wms.112.1701768156506; Tue, 05 Dec 2023 01:22:36 -0800 (PST) Received: from krzk-bin.. ([178.197.218.27]) by smtp.gmail.com with ESMTPSA id g10-20020a05600c4eca00b0040596352951sm21692287wmq.5.2023.12.05.01.22.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 Dec 2023 01:22:36 -0800 (PST) From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> To: Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Alim Akhtar <alim.akhtar@samsung.com>, Thierry Reding <thierry.reding@gmail.com>, =?utf-8?q?Uwe_Kleine-K=C3=B6nig?= <u.kleine-koenig@pengutronix.de>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Jiri Slaby <jirislaby@kernel.org>, Wim Van Sebroeck <wim@linux-watchdog.org>, Guenter Roeck <linux@roeck-us.net>, linux-fsd@tesla.com, linux-i2c@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org, linux-serial@vger.kernel.org, linux-watchdog@vger.kernel.org Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Subject: [PATCH 0/6] dt-bindings: samsung: continued - add specific compatibles for Tesla FSD Hi, Date: Tue, 5 Dec 2023 10:22:23 +0100 Message-Id: <20231205092229.19135-1-krzysztof.kozlowski@linaro.org> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on groat.vger.email Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (groat.vger.email [0.0.0.0]); Tue, 05 Dec 2023 01:22:46 -0800 (PST) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1784433263415812768 X-GMAIL-MSGID: 1784433263415812768 |
Series |
dt-bindings: samsung: continued - add specific compatibles for Tesla FSD Hi,
|
|
Message
Krzysztof Kozlowski
Dec. 5, 2023, 9:22 a.m. UTC
Merging ======= I propose to take entire patchset through my tree (Samsung SoC), because: 1. I already took similar work this cycle: https://lore.kernel.org/all/169997520487.6747.17671551558724027958.b4-ty@linaro.org/ 2. Two new SoCs are coming (Google GS101 and ExynosAutov920) and they might touch the same lines. It is reasonable for me to take the bindings for the new SoCs, to have clean `make dtbs_check` on the new DTS. 3. Having it together helps me to have clean `make dtbs_check` within my tree on the existing DTS. 4. No drivers are affected by this change. If folks agree, please kindly Ack the patches. Description =========== See: https://lore.kernel.org/all/20231108104343.24192-1-krzysztof.kozlowski@linaro.org/ Best regards, Krzysztof Krzysztof Kozlowski (6): dt-bindings: i2c: exynos5: add specific compatible for Tesla FSD dt-bindings: pwm: samsung: add specific compatible for Tesla FSD dt-bindings: serial: samsung: add specific compatible for Tesla FSD dt-bindings: samsung: exynos-pmu: add specific compatible for Tesla FSD dt-bindings: watchdog: samsung: add specific compatible for Tesla FSD arm64: dts: fsd: add specific compatibles for Tesla FSD .../devicetree/bindings/i2c/i2c-exynos5.yaml | 1 + .../devicetree/bindings/pwm/pwm-samsung.yaml | 1 + .../bindings/serial/samsung_uart.yaml | 1 + .../bindings/soc/samsung/exynos-pmu.yaml | 1 + .../bindings/watchdog/samsung-wdt.yaml | 21 +++++++----- arch/arm64/boot/dts/tesla/fsd.dtsi | 32 +++++++++---------- 6 files changed, 33 insertions(+), 24 deletions(-)
Comments
On Tue, Dec 05, 2023 at 10:22:23AM +0100, Krzysztof Kozlowski wrote: > Merging > ======= > I propose to take entire patchset through my tree (Samsung SoC), because: > 1. I already took similar work this cycle: > https://lore.kernel.org/all/169997520487.6747.17671551558724027958.b4-ty@linaro.org/ > 2. Two new SoCs are coming (Google GS101 and ExynosAutov920) and they might > touch the same lines. It is reasonable for me to take the bindings for the new > SoCs, to have clean `make dtbs_check` on the new DTS. > 3. Having it together helps me to have clean `make dtbs_check` within my tree > on the existing DTS. > 4. No drivers are affected by this change. > > If folks agree, please kindly Ack the patches. Acked-by: Conor Dooley <conor.dooley@microchip.com> Cheers, Conor.
On Tue, 05 Dec 2023 10:22:23 +0100, Krzysztof Kozlowski wrote: > Merging > ======= > I propose to take entire patchset through my tree (Samsung SoC), because: > 1. I already took similar work this cycle: > https://lore.kernel.org/all/169997520487.6747.17671551558724027958.b4-ty@linaro.org/ > 2. Two new SoCs are coming (Google GS101 and ExynosAutov920) and they might > touch the same lines. It is reasonable for me to take the bindings for the new > SoCs, to have clean `make dtbs_check` on the new DTS. > 3. Having it together helps me to have clean `make dtbs_check` within my tree > on the existing DTS. > 4. No drivers are affected by this change. > > [...] Applied, thanks! [1/6] dt-bindings: i2c: exynos5: add specific compatible for Tesla FSD https://git.kernel.org/krzk/linux/c/7677fdbc036b93a882f660ca2484a6807e72f0be [2/6] dt-bindings: pwm: samsung: add specific compatible for Tesla FSD https://git.kernel.org/krzk/linux/c/edb32ec3cea79b518e6af841ecb01c839818f562 [3/6] dt-bindings: serial: samsung: add specific compatible for Tesla FSD https://git.kernel.org/krzk/linux/c/921f4f1db7f5bf6798349db8a4382c032f144b98 [4/6] dt-bindings: samsung: exynos-pmu: add specific compatible for Tesla FSD https://git.kernel.org/krzk/linux/c/54772f1d61cd99ea1ed0febd4187bf24ef63bccd [5/6] dt-bindings: watchdog: samsung: add specific compatible for Tesla FSD https://git.kernel.org/krzk/linux/c/bf1e24c5330af06b2f7f1a166a1011d8d48e8651 [6/6] arm64: dts: fsd: add specific compatibles for Tesla FSD https://git.kernel.org/krzk/linux/c/5f257922c5948c58669346d5cda371632108f266 Best regards,