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 CEC9BC44508 for ; Wed, 15 Jul 2026 16:00:03 +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:Content-Transfer-Encoding: Content-Type:In-Reply-To:From:References:Cc:To:Subject:MIME-Version:Date: Message-ID:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=N+qVwV2aNltYFdxx/9mvVwz5Hq1QR+apcslhNzwT5x0=; b=To+MYgjYbdSX1WBGCa+iu48WL0 c7LQgzUVswegW0gDcF1kL+00NbXkxSPpctZvNv9+wivybEMvLFu81wieTUR9M+hZZOcGOCiVIF9tI gBhWw5dsDH0EWw+iOXa9qqhRuvOnuVmsUcBVI9VksCefIz/dvdKWPno2Vb4D1Tkf8EkLKebuG1nIN to98FAWKDWR5HCBhVpjoY1PTDXgwTqrZLaalW9NpOnnFuUzADOb1C4zEtsXxVpBu2brwml0nihPqt GmHFLUDUnk9nyAXucjBJkvER8Sz/yPqVZT59mwD+HWk4L0kCfNEqeydSQO3Nt5I3Be7JG+6SQsQ9j G0cciK8g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wk21d-0000000FOJb-1KJU; Wed, 15 Jul 2026 15:59:57 +0000 Received: from sea.source.kernel.org ([172.234.252.31]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wk21b-0000000FOIw-21I4 for linux-arm-kernel@lists.infradead.org; Wed, 15 Jul 2026 15:59:55 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by sea.source.kernel.org (Postfix) with ESMTP id 309FF432A7; Wed, 15 Jul 2026 15:59:55 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5971F1F000E9; Wed, 15 Jul 2026 15:59:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1784131195; bh=N+qVwV2aNltYFdxx/9mvVwz5Hq1QR+apcslhNzwT5x0=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=V+uYLfKrlDGoRE018a/ACM72eQ//ba/OxJxjMN+blpaRXH5vj+QPK/MWIKI7wF6DV JvqLQf/7seBAaUE4aKlC61cJjenMDGkJI9vTW46OYXS9O2lhlLdZ3r9o1+5MZz3N4A fMIaUUg7xMuXFZjS8u5Na1cjqthXymyVev0vfR5of0o8w3X8F64AvFPy3P5lhtLrRV Zng2+as+VzSKGmP1Wt3r7acB6aFmKMyQW5DcDMyxchEXb5uK5beVW4nZICqa6kCAl6 vDecircMkneRozZgJ1uMdP7C4QHnuI0OD7Pja8vPGTrTIv+Zx4tXvsx8Nfwo8eyaPl XxfT2iHuYXciQ== Message-ID: Date: Wed, 15 Jul 2026 17:59:49 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2 00/10] Initial Apple M3 Pro, Max and Ultra device trees To: Guenter Roeck , Janne Grunau , Neal Gompa , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Thomas Gleixner , Wim Van Sebroeck , Andi Shyti , =?UTF-8?Q?Uwe_Kleine-K=C3=B6nig?= , Sasha Finkelstein Cc: asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org, linux-i2c@vger.kernel.org, linux-pwm@vger.kernel.org, Conor Dooley References: <20260715-apple-t603x-initial-devices-v2-0-df65b2485710@jannau.net> Content-Language: en-US From: Sven Peter In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 On 7/15/26 17:55, Guenter Roeck wrote: > On 7/15/26 02:11, Janne Grunau wrote: >> This series adds device trees for Apple silicon devices with M3 Pro, Max >> and Ultra SoCs. The M3 generation has fewer devices than their M1 and M2 >> predecessors. The only non-laptop device is the M3 Ultra Mac Studio. The >> Laptops are the known 14 and 16-inch Macbook Pros now with M3 Pro and >> M3 Max SoCs. The M3 Max variant with fewer CPU and GPU cores has >> additionally only a 384-bit wide memory bus instead of 512-bit of the >> full M3 Max. It has a separate identifier (T6034) and so there are six >> laptop device trees. >> Another difference to M1 and M2 Pro/Max/Ultra is that the M3 Pro is >> distinct SoC design and not a smaller M3 Max. For this reason both M3 >> Max variants and the M3 Ultra will use "apple,t6030" as compatible >> prefix. In the M1 and M2 generations Pro, Max and Ultra SoCs shared >> "apple,t6000" / "apple,t6020" as common prefix. There is currently no >> known difference but M3 Pro and M3 Max are not as closely related as >> previously. >> >> This series adds the same level of hardware as the base M3 (T8122) has >> in v7.2-rc1. This includes CPU cores, interrupt controller, power >> states, watchdog, serial, pin controller, i2c and the boot framebuffer. >> This is intended as base so that support for additional hardware can be >> added to all M3 based devices at the same time. >> >> Merge strategy: >> Since the dt-binding add new compatible strings without driver changes >> it would be preferred if the whole [1] series would be merged through >> apple-soc/arm-soc. This will help ensuring a warning free >> `make dtbs_check` for followup series with additional M3* hardware >> support I hope to send for this cycle. >> >> This series will conflict with the M4 series [3] sent A couple of days >> ago. I would prefer if this could be merged first (in order of SoC >> release). >> >> [1]: I see that the M4 watchdog change was already picked up by Guenter >>       in [2] >> > > Whatever one does with individual patches in such series seems to be > wrong. Are you saying that I should drop the M4 (t8132) patch from > the watchdog-next branch ? Feel free to keep it. I'll just pick up everything that's left once this series is ready and make sure there are no duplicate patches in -next. Sven