From: Darren Stevens <darren@stevens-zone.net>
To: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Cc: LABBE Corentin <clabbe.montjoie@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
mpm@selenic.com, olof@lixom.net, linuxppc-dev@lists.ozlabs.org
Subject: Re: hwrng: pasemi_rng.c: Migrate to managed API
Date: Mon, 29 Aug 2016 18:52:15 +0100 (BST) [thread overview]
Message-ID: <48b8455031e.651d5701@auth.smtp.1and1.co.uk> (raw)
In-Reply-To: <CANc+2y4JqGRXCLUEpMo8EB8thW5jsweh0Lg2VjuvpNgSR-AwMA@mail.gmail.com>
Hello PrasannaKumar
On 25/08/2016, PrasannaKumar Muralidharan wrote:
>> I will propose to use devm_ioremap_resource() instead for removing this
>> hardcoded 0x100, but i cannot find any user of this driver in any dts.
>> (And so cannot check that this 0x100 is given in any DT resource node)
>
>> Is this normal ?
>
> I wanted to use devm_ioremap_resource but could not find DT entry
> required for this driver in any of the .dts files. So did not change
> that. I could not find any dts/dtsi for this platform. So I assume
> that the dtb is not present in the kernel, dtb is supplied by the
> bootloader. I may be wrong in this. Can anyone confirm this?
On mine (Amigaone X1000) that is correct, we boot linux with a vmlinux file,
and the bootloader (CFE) passes a fixed dtb. I think it is possible to dump
the tree from inside CFE, if it would help I can invetigate?
Regards
Darren
next prev parent reply other threads:[~2016-08-29 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 11:34 [PATCH] hwrng: pasemi_rng.c: Migrate to managed API PrasannaKumar Muralidharan
2016-08-25 12:15 ` LABBE Corentin
2016-08-25 13:25 ` PrasannaKumar Muralidharan
2016-08-29 17:52 ` Darren Stevens [this message]
2016-08-30 7:16 ` PrasannaKumar Muralidharan
2016-08-31 14:02 ` Darren Stevens
2016-09-01 6:59 ` PrasannaKumar Muralidharan
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=48b8455031e.651d5701@auth.smtp.1and1.co.uk \
--to=darren@stevens-zone.net \
--cc=clabbe.montjoie@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpm@selenic.com \
--cc=olof@lixom.net \
--cc=prasannatsmkumar@gmail.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).