From: Macpaul Lin <macpaul.lin@mediatek.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Bernhard Rosenkränzer" <bero@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: Bear Wang <bear.wang@mediatek.com>,
Pablo Sun <pablo.sun@mediatek.com>,
Macpaul Lin <macpaul@gmail.com>
Subject: Re: [PATCH] dt-bindings: arm64: dts: mediatek: add description for mt8365-evk board
Date: Mon, 11 Sep 2023 16:16:44 +0800 [thread overview]
Message-ID: <e697a23e-e677-c97b-269a-a7a11d338d95@mediatek.com> (raw)
In-Reply-To: <649e89c3-343a-c00c-ae89-329833b38981@linaro.org>
On 9/11/23 15:06, Krzysztof Kozlowski wrote:
>
>
> External email : Please do not click links or open attachments until you
> have verified the sender or the content.
>
> On 11/09/2023 08:34, Macpaul Lin wrote:
>> On 9/11/23 14:09, Krzysztof Kozlowski wrote:
>>>
>>>
>>> External email : Please do not click links or open attachments until you
>>> have verified the sender or the content.
>>>
>>> On 10/09/2023 14:07, Macpaul Lin wrote:
>>>>
>>>>
>>>> On 9/10/23 17:09, Krzysztof Kozlowski wrote:
>>>>>> + - description: MediaTek Genio 350 Boards (Genio 350 EVK)
>>>>>
>>>>> That's a bit confusing. So all of the boards here will be Genio 350 EVK?
>>>>> I don't get what is the point of this description.
>>>>>
>>>>>
>>>>>> + items:
>>>>>> - enum:
>>>>>> - mediatek,mt8365-evk
>>>>>> - const: mediatek,mt8365
>>>>
>>>> Thes boards with compatible 'mediatek,mt8365-evk' is indeed used by
>>>
>>> Boards?
>>
>> I'm not sure if there will be more hardware version released to market.
>> Current the p1v3 is the final version of mt8365-evk.
>
> Then your code (enum) does not match description. The code is saying:
> this is for multiple boards based on mt8365.
>
> Your description is saying: this is only for 350 boards.
>
> Now your email is saying: there is only one 350 board.
>
> Three different versions. Sorry, I am confused.
>
Okay, this description has been modified to support single board.
Since there is only one type of the hardware is available on the market.
>>
>>>> Genio 350-EVK, which Baylibre helped to do upstream tasks. The only
>>>> production version of hardware will be available on the market. The
>>>> derived version of customer's hardware is not available yet.
>>>>
>>>> The separate patch for renaming mt8365-evk.dts file should be send next
>>>> week for aligning the naming rules.
>>>
>>> So the description is not correct.
>>>
>>> Anyway, this patch does not make much sense to me considering nothing
>>> like this was merged. You just sent v5 doing the same!
>>
>>
>> Sorry I'm confused now.
>> These are independent patches.
>> This patch is for SOC mt83'6'5 and board mt8365-evk, which is not relate
>> SOC mt83'9'5 and board mt8395-evk.
>
> OK, I see my confusion. mt8365 and mt8395.
>
> Still the description is not matching the code, at least to my limited
> understanding of the description.
>
patch v2 of this change has been send and rebase with that v5 change.
This will generate a different base line for the v2 patch for avoiding
confusion. :)
> Best regards,
> Krzysztof
>
Thanks
Macpaul Lin
next prev parent reply other threads:[~2023-09-11 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 6:28 [PATCH] dt-bindings: arm64: dts: mediatek: add description for mt8365-evk board Macpaul Lin
2023-09-10 9:09 ` Krzysztof Kozlowski
2023-09-10 12:07 ` Macpaul Lin
2023-09-11 6:09 ` Krzysztof Kozlowski
2023-09-11 6:34 ` Macpaul Lin
2023-09-11 7:06 ` Krzysztof Kozlowski
2023-09-11 8:16 ` Macpaul Lin [this message]
2023-09-11 9:47 ` Krzysztof Kozlowski
2023-09-11 9:49 ` Krzysztof Kozlowski
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=e697a23e-e677-c97b-269a-a7a11d338d95@mediatek.com \
--to=macpaul.lin@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bear.wang@mediatek.com \
--cc=bero@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=macpaul@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=pablo.sun@mediatek.com \
--cc=robh+dt@kernel.org \
/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).