Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Penny Chiu <pchiu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	AMartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [tegrarcm PATCH 1/1] tegrarcm: Add odm production secure mode support
Date: Wed, 02 Apr 2014 11:06:54 -0600	[thread overview]
Message-ID: <533C43AE.1090502@wwwdotorg.org> (raw)
In-Reply-To: <1396403868-14479-1-git-send-email-pchiu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

On 04/01/2014 07:57 PM, Penny Chiu wrote:
> tegrarcm should work if the operating mode is ODM production
> secure mode. Add the operating mode definition and description.

> diff --git a/src/main.c b/src/main.c

>  	if (info.op_mode != RCM_OP_MODE_DEVEL &&
>  	    info.op_mode != RCM_OP_MODE_ODM_OPEN &&
> +	    info.op_mode != RCM_OP_MODE_ODM_SECURE &&
>  	    info.op_mode != RCM_OP_MODE_PRE_PRODUCTION)

Are there even more modes beyond those? I wonder if that check is even
necessary any more, or whether tegrarcm should just try to communicate
no matter what.

Still, any changes here can be addressed in a separate patch.

Acked-by:
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

Allen, will you apply this or do you want me to?

  parent reply	other threads:[~2014-04-02 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02  1:57 [tegrarcm PATCH 1/1] tegrarcm: Add odm production secure mode support Penny Chiu
     [not found] ` <1396403868-14479-1-git-send-email-pchiu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-04-02 17:06   ` Stephen Warren [this message]
     [not found]     ` <533C43AE.1090502-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-04-02 18:15       ` Allen Martin

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=533C43AE.1090502@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=AMartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pchiu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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