Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20190606172845.16864-1-festevam@gmail.com> <f166aeb5-bde2-1721-d7d8-bc19245a324a@c-s.fr>
In-Reply-To: <f166aeb5-bde2-1721-d7d8-bc19245a324a@c-s.fr>
From:   Fabio Estevam <festevam@gmail.com>
Date:   Thu, 6 Jun 2019 14:51:32 -0300
Message-ID: <CAOMZO5D7nWw-+mwuNny3nJe-buz0dhGY2M=e6nSQgjOJDKkBaw@mail.gmail.com>
Subject: Re: [PATCH v2] crypto: talitos - Use devm_platform_ioremap_resource()
To:     Christophe Leroy <christophe.leroy@c-s.fr>
Cc:     Herbert Xu <herbert@gondor.apana.org.au>,
        "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" 
        <linux-crypto@vger.kernel.org>,
        Horia Geanta Neag <horia.geanta@nxp.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

Hi Christophe,

On Thu, Jun 6, 2019 at 2:45 PM Christophe Leroy <christophe.leroy@c-s.fr> wrote:

> Have you checked that it has no impact ?
>
> On SOCs, areas of memory are often shared between several drivers.
> devm_ioremap_ressource() can only be used if we are 100% sure that this
> area of memory is not shared with any other driver.

Thanks for the clarification. I think we should stay on the safe side
and discard this patch then.