Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vignesh Raman <vignesh.raman@collabora.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	linux-mediatek@lists.infradead.org, chunkuang.hu@kernel.org,
	p.zabel@pengutronix.de, angelogioacchino.delregno@collabora.com,
	daniels@collabora.com, airlied@gmail.com, simona.vetter@ffwll.ch,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] arm64: defconfig: mediatek: enable PHY drivers
Date: Wed, 12 Mar 2025 09:07:16 +0530	[thread overview]
Message-ID: <e492a080-78e1-4694-9e84-a5373f3f23c7@collabora.com> (raw)
In-Reply-To: <717b84da-f307-41e9-9dc3-67ea653cac5f@notapiano>

Hi Nícolas,

On 12/03/25 01:15, Nícolas F. R. A. Prado wrote:
> On Tue, Mar 11, 2025 at 05:26:37PM +0530, Vignesh Raman wrote:
>> Hi Krzysztof,
>>
>> On 11/03/25 12:54, Krzysztof Kozlowski wrote:
>>> On 11/03/2025 07:16, Vignesh Raman wrote:
>>>> The mediatek display driver fails to probe on mt8173 and mt8183 in
>>>> v6.14-rc4, with the following errors:
>>>
>>> Which boards?
>>
>> These are the boards,
>> https://lava.pages.collabora.com/docs/boards/chromebooks/boards/hana/
>> https://lava.pages.collabora.com/docs/boards/chromebooks/boards/jacuzzi/
> 
> You can use the Devicetree name to identify them in a way that's meaningful for
> the kernel:
> 
> mt8173-elm-hana
> mt8183-kukui-jacuzzi-juniper-sku16

Thanks. Will use the device tree name.

Regards,
Vignesh

> 
> Thanks,
> Nícolas



      reply	other threads:[~2025-03-12  3:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11  6:16 [PATCH v1] arm64: defconfig: mediatek: enable PHY drivers Vignesh Raman
2025-03-11  7:24 ` Krzysztof Kozlowski
2025-03-11 11:56   ` Vignesh Raman
2025-03-11 19:45     ` Nícolas F. R. A. Prado
2025-03-12  3:37       ` Vignesh Raman [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=e492a080-78e1-4694-9e84-a5373f3f23c7@collabora.com \
    --to=vignesh.raman@collabora.com \
    --cc=airlied@gmail.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=daniels@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=nfraprado@collabora.com \
    --cc=p.zabel@pengutronix.de \
    --cc=simona.vetter@ffwll.ch \
    /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