From: Beleswar Prasad Padhi <b-padhi@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <nm@ti.com>,
<vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <u-kumar1@ti.com>, <tony@atomide.com>, <bb@ti.com>,
<d-gole@ti.com>, <afd@ti.com>, <hnagalla@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/7] arm64: dts: ti: k3-j7200-som-p0: Change timer nodes status to reserved
Date: Tue, 27 Aug 2024 10:24:39 +0530 [thread overview]
Message-ID: <2beb4f12-c485-4af5-86ef-a481f6f7ecae@ti.com> (raw)
In-Reply-To: <e7aa7d45-8d5f-4f5f-bba4-b9e0f77d8a6a@kernel.org>
On 26/08/24 18:07, Krzysztof Kozlowski wrote:
> On 26/08/2024 12:54, Krzysztof Kozlowski wrote:
>> On 26/08/2024 12:48, Beleswar Padhi wrote:
>>> The remoteproc firmware of R5F in the MAIN voltage domain use timers.
>>> Therefore, change the status of the timer nodes to "reserved" to avoid
>>> any clash. Usage is described as below:
>>>
>>> +===================+==========================+
>>> | Remoteproc node | Timer Node |
>>> +===================+==========================+
>>> | main_r5fss0_core0 | main_timer0, main_timer2 |
>>> +-------------------+--------------------------+
>>> | main_r5fss0_core1 | main_timer1 |
>>> +-------------------+--------------------------+
>>>
>>> Fixes: c8a28ed4837c ("arm64: dts: ti: k3-j7200: Add general purpose timers")
>>> Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
>> You keep sending the same. Where is the changelog? Why so many same
>> patchsets? Why so many resends without changes?
> OK, now cover letter came and I see the changelog. Some hickup on mail
> servers.
I understand the mistake. From next time, will mention changelogs in
patches as well as cover letter.
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2024-08-27 4:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 10:48 [PATCH v4 0/7] Reserve Timer Nodes to avoid clash with Remoteproc firmware Beleswar Padhi
2024-08-26 10:48 ` [PATCH v4 1/7] arm64: dts: ti: k3-j7200-som-p0: Change timer nodes status to reserved Beleswar Padhi
2024-08-26 10:54 ` Krzysztof Kozlowski
2024-08-26 12:37 ` Krzysztof Kozlowski
2024-08-27 4:54 ` Beleswar Prasad Padhi [this message]
2024-08-26 10:48 ` [PATCH v4 2/7] arm64: dts: ti: k3-j721e-som-p0: " Beleswar Padhi
2024-08-26 10:48 ` [PATCH v4 3/7] arm64: dts: ti: k3-j721e-sk: " Beleswar Padhi
2024-08-26 10:48 ` [PATCH v4 4/7] arm64: dts: ti: k3-j721s2-som-p0: " Beleswar Padhi
2024-08-26 10:48 ` [PATCH v4 5/7] arm64: dts: ti: k3-am68-sk-som: " Beleswar Padhi
2024-08-26 10:48 ` [PATCH v4 6/7] arm64: dts: ti: k3-j784s4-evm: " Beleswar Padhi
2024-08-26 10:48 ` [PATCH v4 7/7] arm64: dts: ti: k3-am69-sk: " Beleswar Padhi
2024-08-26 10:57 ` [PATCH v4 0/7] Reserve Timer Nodes to avoid clash with Remoteproc firmware Beleswar Prasad Padhi
2024-08-28 18:58 ` Nishanth Menon
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=2beb4f12-c485-4af5-86ef-a481f6f7ecae@ti.com \
--to=b-padhi@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=tony@atomide.com \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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).