All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<michal.simek@xilinx.com>, <derek.kiernan@xilinx.com>,
	<dragan.cvetic@xilinx.com>, <arnd@arndb.de>,
	<gregkh@linuxfoundation.org>,
	<linux-arm-kernel@lists.infradead.org>
Cc: <git@amd.com>, <git@xilinx.com>
Subject: Re: [PATCH 1/4] dt-bindings: misc: tmr-manager: Add device-tree binding for TMR Manager
Date: Wed, 29 Jun 2022 13:59:32 +0200	[thread overview]
Message-ID: <a653cb16-4aa9-693a-ac32-cc7b1b999b92@amd.com> (raw)
In-Reply-To: <e43bede7-2a0a-5114-e9ec-9e1449bf4e47@linaro.org>



On 6/29/22 13:45, Krzysztof Kozlowski wrote:
> On 29/06/2022 13:23, Michal Simek wrote:
>>
>>
>> On 6/29/22 12:07, Krzysztof Kozlowski wrote:
>>> On 28/06/2022 07:43, Appana Durga Kedareswara rao wrote:
>>>> This commit adds documentation for Triple Modular Redundancy(TMR) Manager
>>>> IP. The Triple Modular Redundancy(TMR) Manager is responsible for handling
>>>> the TMR subsystem state, including fault detection and error recovery
>>>> provides soft error detection, correction and recovery features.
>>>>
>>>> Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
>>>> ---
>>>>    .../bindings/misc/xlnx,tmr-manager.yaml       | 48 +++++++++++++++++++
>>>
>>> This is not a misc device. Find appropriate subsystem for it. It's not
>>> EDAC, right?
>>
>> We were thinking where to put it but it is not EDAC driver.
>> If you have better suggestion for subsystem please let us know.
> 
> I don't know what's the device about. The description does not help:
> 
> "TMR Manager is responsible for TMR subsystem state..."

ok. let's improve commit message in v2.

TMR - triple module redundancy.

You design the system with one CPU which is default microblaze configuration 
with interrupt controller, timer and other IPs.

And then say I want to do it triple redundant with all that voting, etc.
If you want to get all details you can take a look at this guide

https://www.xilinx.com/content/dam/xilinx/support/documents/ip_documentation/tmr/v1_0/pg268-tmr.pdf

In short TMR manager is servicing all that 3 cores and making sure that they are 
all running in sync. If not it has capability recover the system. It means cpu 
gets to break handler (it is the part of microblaze series) and it restarts all 
cpus.

And TMR inject driver is module which is capable to inject error to internal 
memory to cause the exception to exercise that recovery code.

Kedar: Feel free to correct me or add more details.

Thanks,
Michal

WARNING: multiple messages have this Message-ID (diff)
From: Michal Simek <michal.simek@amd.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<michal.simek@xilinx.com>, <derek.kiernan@xilinx.com>,
	<dragan.cvetic@xilinx.com>, <arnd@arndb.de>,
	<gregkh@linuxfoundation.org>,
	<linux-arm-kernel@lists.infradead.org>
Cc: <git@amd.com>, <git@xilinx.com>
Subject: Re: [PATCH 1/4] dt-bindings: misc: tmr-manager: Add device-tree binding for TMR Manager
Date: Wed, 29 Jun 2022 13:59:32 +0200	[thread overview]
Message-ID: <a653cb16-4aa9-693a-ac32-cc7b1b999b92@amd.com> (raw)
In-Reply-To: <e43bede7-2a0a-5114-e9ec-9e1449bf4e47@linaro.org>



On 6/29/22 13:45, Krzysztof Kozlowski wrote:
> On 29/06/2022 13:23, Michal Simek wrote:
>>
>>
>> On 6/29/22 12:07, Krzysztof Kozlowski wrote:
>>> On 28/06/2022 07:43, Appana Durga Kedareswara rao wrote:
>>>> This commit adds documentation for Triple Modular Redundancy(TMR) Manager
>>>> IP. The Triple Modular Redundancy(TMR) Manager is responsible for handling
>>>> the TMR subsystem state, including fault detection and error recovery
>>>> provides soft error detection, correction and recovery features.
>>>>
>>>> Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
>>>> ---
>>>>    .../bindings/misc/xlnx,tmr-manager.yaml       | 48 +++++++++++++++++++
>>>
>>> This is not a misc device. Find appropriate subsystem for it. It's not
>>> EDAC, right?
>>
>> We were thinking where to put it but it is not EDAC driver.
>> If you have better suggestion for subsystem please let us know.
> 
> I don't know what's the device about. The description does not help:
> 
> "TMR Manager is responsible for TMR subsystem state..."

ok. let's improve commit message in v2.

TMR - triple module redundancy.

You design the system with one CPU which is default microblaze configuration 
with interrupt controller, timer and other IPs.

And then say I want to do it triple redundant with all that voting, etc.
If you want to get all details you can take a look at this guide

https://www.xilinx.com/content/dam/xilinx/support/documents/ip_documentation/tmr/v1_0/pg268-tmr.pdf

In short TMR manager is servicing all that 3 cores and making sure that they are 
all running in sync. If not it has capability recover the system. It means cpu 
gets to break handler (it is the part of microblaze series) and it restarts all 
cpus.

And TMR inject driver is module which is capable to inject error to internal 
memory to cause the exception to exercise that recovery code.

Kedar: Feel free to correct me or add more details.

Thanks,
Michal

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-06-29 11:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28  5:43 [PATCH 0/4] drivers: misc: Add support for TMR Manager and Inject IPs Appana Durga Kedareswara rao
2022-06-28  5:43 ` Appana Durga Kedareswara rao
2022-06-28  5:43 ` [PATCH 1/4] dt-bindings: misc: tmr-manager: Add device-tree binding for TMR Manager Appana Durga Kedareswara rao
2022-06-28  5:43   ` Appana Durga Kedareswara rao
2022-06-29 10:07   ` Krzysztof Kozlowski
2022-06-29 10:07     ` Krzysztof Kozlowski
2022-06-29 11:23     ` Michal Simek
2022-06-29 11:23       ` Michal Simek
2022-06-29 11:45       ` Krzysztof Kozlowski
2022-06-29 11:45         ` Krzysztof Kozlowski
2022-06-29 11:59         ` Michal Simek [this message]
2022-06-29 11:59           ` Michal Simek
2022-06-29 12:37           ` Rao, Appana Durga Kedareswara
2022-06-29 12:37             ` Rao, Appana Durga Kedareswara
2022-06-30 10:07             ` Krzysztof Kozlowski
2022-06-30 10:07               ` Krzysztof Kozlowski
2022-06-30 10:59               ` Michal Simek
2022-06-30 10:59                 ` Michal Simek
2022-06-29 12:32     ` Rao, Appana Durga Kedareswara
2022-06-29 12:32       ` Rao, Appana Durga Kedareswara
2022-06-28  5:43 ` [PATCH 2/4] drivers: misc: Add Support " Appana Durga Kedareswara rao
2022-06-28  5:43   ` Appana Durga Kedareswara rao
2022-07-01  8:19   ` Greg KH
2022-07-01  8:19     ` Greg KH
2022-07-04  4:07     ` Rao, Appana Durga Kedareswara
2022-07-04  4:07       ` Rao, Appana Durga Kedareswara
2022-07-05  2:39     ` Zhou Furong
2022-07-05  2:39       ` Zhou Furong
2022-06-28  5:43 ` [PATCH 3/4] dt-bindings: misc: tmr-inject: Add device-tree binding for TMR Inject Appana Durga Kedareswara rao
2022-06-28  5:43   ` Appana Durga Kedareswara rao
2022-06-29 10:08   ` Krzysztof Kozlowski
2022-06-29 10:08     ` Krzysztof Kozlowski
2022-06-29 11:29     ` Michal Simek
2022-06-29 11:29       ` Michal Simek
2022-06-29 10:09   ` Krzysztof Kozlowski
2022-06-29 10:09     ` Krzysztof Kozlowski
2022-06-29 12:32     ` Rao, Appana Durga Kedareswara
2022-06-29 12:32       ` Rao, Appana Durga Kedareswara
2022-06-28  5:43 ` [PATCH 4/4] drivers: misc: Add Support for TMR Inject IP Appana Durga Kedareswara rao
2022-06-28  5:43   ` Appana Durga Kedareswara rao

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=a653cb16-4aa9-693a-ac32-cc7b1b999b92@amd.com \
    --to=michal.simek@amd.com \
    --cc=appana.durga.rao@xilinx.com \
    --cc=arnd@arndb.de \
    --cc=derek.kiernan@xilinx.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dragan.cvetic@xilinx.com \
    --cc=git@amd.com \
    --cc=git@xilinx.com \
    --cc=gregkh@linuxfoundation.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=michal.simek@xilinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.