From: Vinod <vkoul@kernel.org>
To: Timur Tabi <timur@codeaurora.org>
Cc: timur@kernel.org, linux-arm-msm@vger.kernel.org,
swboyd@chromium.org, linux-crypto@vger.kernel.org,
Matt Mackall <mpm@selenic.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] hwrng: msm: add ACPI support
Date: Fri, 22 Jun 2018 10:18:20 +0530 [thread overview]
Message-ID: <20180622044819.GJ27187@vkoul-mobl> (raw)
In-Reply-To: <30b28a05-dd63-603c-d4cd-296b84072faf@codeaurora.org>
On 21-06-18, 23:46, Timur Tabi wrote:
> On 6/21/18 11:44 PM, Vinod wrote:
> > So this make me think you should do 2 level support for ACPI, one ACPI
> > support and one V2 support where we dont touch CONFIG register. That way
> > both regions will work
>
> The ACPI system is a v2 system. If you want, I can just remove the read of
> the CONFIG register.
Okay, so in this case who configures v2. My guess here is that firmware
hasn't locked access, default everyone can access per spec
--
~Vinod
next prev parent reply other threads:[~2018-06-22 4:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 15:17 [PATCH 1/2] hwrng: msm: add a spinlock and support for blocking reads Timur Tabi
2018-06-21 15:17 ` [PATCH 2/2] hwrng: msm: add ACPI support Timur Tabi
2018-06-22 4:23 ` Vinod
2018-06-22 4:26 ` Timur Tabi
2018-06-22 4:44 ` Vinod
2018-06-22 4:46 ` Timur Tabi
2018-06-22 4:48 ` Vinod [this message]
2018-06-22 4:17 ` [PATCH 1/2] hwrng: msm: add a spinlock and support for blocking reads Vinod
2018-06-22 4:18 ` Timur Tabi
2018-06-22 4:24 ` Vinod
2018-06-22 4:28 ` Timur Tabi
2018-06-22 5:36 ` Stephen Boyd
2018-06-22 13:11 ` Timur Tabi
2018-06-22 15:38 ` Stanimir Varbanov
2018-06-22 15:41 ` Timur Tabi
2018-06-22 17:51 ` Stephen Boyd
2018-06-22 18:03 ` Timur Tabi
2018-06-22 21:17 ` Timur Tabi
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=20180622044819.GJ27187@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=swboyd@chromium.org \
--cc=timur@codeaurora.org \
--cc=timur@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