From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cs-2000-cp: keep Reserved bit on each register
Date: Wed, 5 Apr 2017 12:04:23 -0700 [thread overview]
Message-ID: <20170405190423.GL18246@codeaurora.org> (raw)
In-Reply-To: <87y3vfxw3q.wl%kuninori.morimoto.gx@renesas.com>
On 04/05, Kuninori Morimoto wrote:
>
> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>
> Thus CS2000 datasheet is indicating below, this patch
> follows it.
>
> WARNING: All "Reserved" registers must maintain their default
> state to ensure proper functional operation.
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Is this v2? I see two of these from different days.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next parent reply other threads:[~2017-04-05 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y3vfxw3q.wl%kuninori.morimoto.gx@renesas.com>
2017-04-05 19:04 ` Stephen Boyd [this message]
2017-04-05 23:31 ` [PATCH] cs-2000-cp: keep Reserved bit on each register Kuninori Morimoto
2017-04-06 23:11 ` Stephen Boyd
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=20170405190423.GL18246@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).