linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "André Draszik" <andre.draszik@linaro.org>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Peter Griffin <peter.griffin@linaro.org>,
	Tudor Ambarus <tudor.ambarus@linaro.org>,
	Alim Akhtar <alim.akhtar@samsung.com>
Cc: Will McVicker <willmcvicker@google.com>,
	kernel-team@android.com,  devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Google Pixel 6 Pro support
Date: Fri, 20 Dec 2024 14:42:49 +0000	[thread overview]
Message-ID: <21d1605c49d7d6a0f7f0f532d99cd7d285bd2958.camel@linaro.org> (raw)
In-Reply-To: <20241220-gs101-simplefb-v2-0-c10a8f9e490b@linaro.org>

On Fri, 2024-12-20 at 11:27 +0000, André Draszik wrote:
> Hi,
> 
> This series enables support for Google Pixel 6 Pro.
> 
> Since Pixel 6 and Pixel 6 Pro use a different resolution display, we
> now need to add explicit support for it, we can not piggyback on the
> non-Pro version anymore. This means having to separate them into their
> respective DTs, and provide one for each of them.
> There are other differences between the two of course, like battery
> design capacity, etc., but they don't matter at this stage due to
> incomplete upstream support.
> 
> * dependency note *
> 
> Due to the renaming of the gs101-oriole.dts, this series will conflict
> with any pending patches touching the same file. I have therefore based
> this series on top of my USB series from
> https://lore.kernel.org/r/20241203-gs101-phy-lanes-orientation-dts-v2-0-1412783a6b01@linaro.org
> and the patch enabling framebuffer support for Pixel 6 from
> https://lore.kernel.org/r/20241220-gs101-simplefb-oriole-v2-1-df60e566932a@linaro.org

Actually, since this series was regenerated with git's
diff.renames=copies, it doesn't depend on my USB series
anymore, just on the framebuffer enablement for Pixel 6.

Cheers,
Andre'



      parent reply	other threads:[~2024-12-20 14:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 11:27 [PATCH v2 0/3] Google Pixel 6 Pro support André Draszik
2024-12-20 11:27 ` [PATCH v2 1/3] dt-bindings: arm: google: add gs101-raven and generic gs101-pixel André Draszik
2024-12-22 11:38   ` Krzysztof Kozlowski
2024-12-23  7:45     ` André Draszik
2024-12-23 14:14       ` Krzysztof Kozlowski
2024-12-23 15:31         ` André Draszik
2024-12-23 15:39           ` Krzysztof Kozlowski
2024-12-23 15:54             ` André Draszik
2024-12-23 15:58               ` Krzysztof Kozlowski
2024-12-20 11:27 ` [PATCH v2 2/3] arm64: dts: exynos: gs101-pixel: add generic gs101-based Pixel support André Draszik
2024-12-22 11:42   ` Krzysztof Kozlowski
2024-12-23  7:59     ` André Draszik
2024-12-23 14:18       ` Krzysztof Kozlowski
2024-12-20 11:27 ` [PATCH v2 3/3] arm64: dts: exynos: gs101-raven: add new board file André Draszik
2024-12-22 11:43   ` Krzysztof Kozlowski
2024-12-23 10:42     ` André Draszik
2024-12-20 14:42 ` André Draszik [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21d1605c49d7d6a0f7f0f532d99cd7d285bd2958.camel@linaro.org \
    --to=andre.draszik@linaro.org \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel-team@android.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=peter.griffin@linaro.org \
    --cc=robh@kernel.org \
    --cc=tudor.ambarus@linaro.org \
    --cc=willmcvicker@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).