From: Roy Pledge <roy.pledge@nxp.com> To: Scott Wood <oss@buserror.net>, "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "robin.murphy@arm.com" <robin.murphy@arm.com> Cc: Madalin-Cristian Bucur <madalin.bucur@nxp.com> Subject: Re: [PATCH v2 07/11] soc/fsl/qbman: Rework ioremap() calls for ARM/PPC Date: Mon, 1 May 2017 19:00:14 +0000 [thread overview] Message-ID: <VI1PR04MB3216F7EC8657711225E30AAC86140@VI1PR04MB3216.eurprd04.prod.outlook.com> (raw) In-Reply-To: <1492998461.25397.16.camel@buserror.net> On 4/23/2017 9:47 PM, Scott Wood wrote: > On Wed, 2017-04-19 at 16:48 -0400, Roy Pledge wrote: >> Rework ioremap() for PPC and ARM. The PPC devices require a >> non-coherent mapping while ARM will work with a non-cachable/write >> combine mapping. >> >> Signed-off-by: Roy Pledge <roy.pledge@nxp.com> >> --- >> drivers/soc/fsl/qbman/bman_portal.c | 16 +++++++++++++--- >> drivers/soc/fsl/qbman/qman_portal.c | 16 +++++++++++++--- >> 2 files changed, 26 insertions(+), 6 deletions(-) >> >> diff --git a/drivers/soc/fsl/qbman/bman_portal.c >> b/drivers/soc/fsl/qbman/bman_portal.c >> index 8354d4d..a661f30 100644 >> --- a/drivers/soc/fsl/qbman/bman_portal.c >> +++ b/drivers/soc/fsl/qbman/bman_portal.c >> @@ -125,7 +125,18 @@ static int bman_portal_probe(struct platform_device >> *pdev) >> } >> pcfg->irq = irq; >> >> - va = ioremap_prot(addr_phys[0]->start, resource_size(addr_phys[0]), >> 0); >> +#ifdef CONFIG_PPC >> + /* PPC requires a cacheable/non-coherent mapping of the portal */ >> + va = ioremap_prot(addr_phys[0]->start, resource_size(addr_phys[0]), >> + (pgprot_val(PAGE_KERNEL) & ~_PAGE_COHERENT)); >> +#else >> + /* >> + * For ARM we can use write combine mapping. A cacheable/non >> shareable >> + * mapping will perform better but equires additional platform >> + * support which is not currently available >> + */ > s/equires/requires/ > > Would be nice to describe the platform support that is required. Thanks for your feedback Scott, going to try to get a v3 of this set ASAP. I think I will remove the above statement for now. We did send patches for do non-shareable support on DPAA2 and there was significant feedback so I'm in the process of discussing the issue with SOC architects here. We will follow up with ARM folks on this eventually but I'd like to get the basic DPAA1 support in before adding the more advanced features. Roy > > -Scott > >
next prev parent reply other threads:[~2017-05-01 19:00 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-19 20:48 [PATCH v2 00/11] soc/fsl/qbman: Enable QBMan on ARM Platforms Roy Pledge 2017-04-19 20:48 ` [PATCH v2 01/11] soc/fsl/qbman: Use shared-dma-pool for BMan private memory allocations Roy Pledge 2017-04-19 20:48 ` [PATCH v2 02/11] soc/fsl/qbman: Use shared-dma-pool for QMan " Roy Pledge 2017-04-24 1:44 ` Scott Wood 2017-04-19 20:48 ` [PATCH v2 03/11] dt-bindings: soc/fsl: Update reserved memory binding for QBMan Roy Pledge 2017-04-24 1:09 ` Scott Wood 2017-04-19 20:48 ` [PATCH v2 04/11] soc/fsl/qbman: Drop set/clear_bits usage Roy Pledge 2017-04-19 20:48 ` [PATCH v2 05/11] soc/fsl/qbman: Drop L1_CACHE_BYTES compile time check Roy Pledge 2017-04-19 20:48 ` [PATCH v2 06/11] soc/fsl/qbman: Fix ARM32 typo Roy Pledge 2017-04-19 20:48 ` [PATCH v2 07/11] soc/fsl/qbman: Rework ioremap() calls for ARM/PPC Roy Pledge 2017-04-24 1:47 ` Scott Wood 2017-05-01 19:00 ` Roy Pledge [this message] 2017-04-19 20:48 ` [PATCH v2 08/11] soc/fsl/qbman: add QMAN_REV32 Roy Pledge 2017-04-19 20:48 ` [PATCH v2 09/11] soc/fsl/qbman: different register offsets on ARM Roy Pledge 2017-04-19 20:48 ` [PATCH v2 10/11] soc/fsl/qbman: Add missing headers " Roy Pledge 2017-04-19 20:48 ` [PATCH v2 11/11] fsl/soc/qbman: Enable FSL_LAYERSCAPE config " Roy Pledge
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=VI1PR04MB3216F7EC8657711225E30AAC86140@VI1PR04MB3216.eurprd04.prod.outlook.com \ --to=roy.pledge@nxp.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=madalin.bucur@nxp.com \ --cc=oss@buserror.net \ --cc=robin.murphy@arm.com \ --subject='Re: [PATCH v2 07/11] soc/fsl/qbman: Rework ioremap() calls for ARM/PPC' \ /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
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).