From: Michael Zoran <mzoran@crowfest.net>
To: Eric Anholt <eric@anholt.net>, gregkh@linuxfoundation.org
Cc: swarren@wwwdotorg.org, lee@kernel.org, daniels@collabora.com,
noralf@tronnes.org, popcornmix@gmail.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vc04_services: setup DMA and coherent mask
Date: Mon, 31 Oct 2016 11:40:58 -0700 [thread overview]
Message-ID: <1477939258.30971.1.camel@crowfest.net> (raw)
In-Reply-To: <87twbsqsb4.fsf@eliezer.anholt.net>
On Mon, 2016-10-31 at 11:36 -0700, Eric Anholt wrote:
> Michael Zoran <mzoran@crowfest.net> writes:
>
> > Setting the DMA mask is optional on 32 bit but
> > is mandatory on 64 bit. Set the DMA mask and coherent
> > to force all DMA to be in the 32 bit address space.
> >
> > This is considered a "good practice" and most drivers
> > already do this.
> >
> > Signed-off-by: Michael Zoran <mzoran@crowfest.net>
> > ---
> > .../staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.c |
> > 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git
> > a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.
> > c
> > b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.
> > c
> > index a5afcc5..6fa2b5a 100644
> > ---
> > a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.
> > c
> > +++
> > b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_2835_arm.
> > c
> > @@ -97,6 +97,16 @@ int vchiq_platform_init(struct platform_device
> > *pdev, VCHIQ_STATE_T *state)
> > int slot_mem_size, frag_mem_size;
> > int err, irq, i;
> >
> > + /*
> > + * Setting the DMA mask is necessary in the 64 bit
> > environment.
> > + * It isn't necessary in a 32 bit environment but is
> > considered
> > + * a good practice.
> > + */
> > + err = dma_set_mask_and_coherent(dev, DMA_BIT_MASK(32));
>
> I think a better comment here would be simply:
>
> /* VCHI messages between the CPU and firmware use 32-bit bus
> addresses. */
>
> explaining why the value is chosen (once you know that the 32 bit
> restriction exists, reporting it is obviously needed). I'm curious,
> though: what failed when you didn't set it?
>
The comment is easy to change.
I don't have the log available ATM, but if I remember the DMA API's
bugcheck the first time that are used.
I think this was a policy decision or something because the information
should be available in the dma-ranges.
If it's important, I can setup a test again without the change and e-
mail the logs.
If you look at the DWC2 driver you will see that it also sets this
mask.
next prev parent reply other threads:[~2016-10-31 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 17:11 [PATCH] staging: vc04_services: setup DMA and coherent mask Michael Zoran
2016-10-31 18:36 ` Eric Anholt
2016-10-31 18:40 ` Michael Zoran [this message]
2016-10-31 19:53 ` Michael Zoran
2016-10-31 19:57 ` Michael Zoran
2016-11-01 9:31 ` Russell King - ARM Linux
2016-11-01 12:56 ` Robin Murphy
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=1477939258.30971.1.camel@crowfest.net \
--to=mzoran@crowfest.net \
--cc=daniels@collabora.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=noralf@tronnes.org \
--cc=popcornmix@gmail.com \
--cc=swarren@wwwdotorg.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