public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] [usb] make xhci platform driver use 64 bit or 32 bit DMA
Date: Fri, 31 Oct 2014 16:49:38 +0100	[thread overview]
Message-ID: <2609633.oChO4mb7il@wuerfel> (raw)
In-Reply-To: <54539B22.9010606@redhat.com>

On Friday 31 October 2014 09:22:26 Mark Langsdorf wrote:
> On 10/30/2014 04:05 PM, Arnd Bergmann wrote:
> > On Thursday 30 October 2014 15:09:33 Mark Langsdorf wrote:
> >
> > You should not access pdev->dev.dma_mask here, that gets set
> > by the platform code. You should be able to just use
> > dma_set_mask_and_coherent to set both.
> 
> So:
> 
>         if (sizeof(dma_addr_t) < 8 ||
>                 dma_set_mask_and_coherent(&pdev->dev, DMA_BIT_MASK(64))) {
>                 ret = dma_set_mask_and_coherent(&pdev->dev, DMA_BIT_MASK(32));
>                 if (ret)
>                         return ret;
>         }
> 
> This doesn't actually work for me. I experimented a bit on the
> hardware and I always fail if I don't set the coherent mask
> first.

Very strange, the code looks right to me. What is the initial value
of dev->dma_mask?

> >>> Also, we should no longer need to worry about the case where
> >>> pdev->dev.dma_mask is NULL, as this now gets initialized from
> >>> the DT setup.
> >>
> >> I'm running this on a system with ACPI enabled and no DT. Does
> >> that make a difference?
> >
> > I don't know how the DMA mask gets initialized on ACPI, I assume it
> > doesn't at the moment, but that is something that should be fixed
> > in the ACPI code, not worked around in the driver.
> >
> > You should definitely make sure that this also works with DT, as
> > I don't think it's possible to support X-Gene with ACPI. I know
> > that Al Stone has experimented with it in the past, but he never
> > came back with any results, so I assume the experiment failed.
> 
> I'm running my test code on an X-Gene with ACPI. Al Stone, Mark
> Salter, and I got it working.

The question is whether that is in a form that we could merge upstream.
I haven't seen any patches being posted, so I can't know for sure, but
from all I know about the hardware it doesn't seem likely, unless
you leave out all the interesting bits such as power mangement, PCI
and networking.

	Arnd

  reply	other threads:[~2014-10-31 15:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 18:16 [usb] add support for APM X-Gene to xhci-platform Mark Langsdorf
2014-10-30 18:16 ` [PATCH 1/2] [usb] make xhci platform driver use 64 bit or 32 bit DMA Mark Langsdorf
2014-10-30 19:05   ` Arnd Bergmann
2014-10-30 20:09     ` Mark Langsdorf
2014-10-30 21:05       ` Arnd Bergmann
2014-10-31 14:22         ` Mark Langsdorf
2014-10-31 15:49           ` Arnd Bergmann [this message]
2014-10-31 17:32             ` Mark Langsdorf
2014-10-31 19:41               ` Arnd Bergmann
2014-11-03 14:15         ` Mark Salter
2014-11-03 17:14           ` Arnd Bergmann
2014-11-03 18:45             ` Mark Salter
2014-11-04 17:33             ` Al Stone
2014-11-06  0:03               ` Arnd Bergmann
2014-11-04 16:50   ` [PATCH v2 " Mark Langsdorf
2014-11-04 16:50     ` [PATCH v2 2/2] [usb] add support for ACPI identification to xhci-platform Mark Langsdorf
2014-11-04 17:12       ` Greg KH
2014-11-05 13:59         ` Mark Langsdorf
2014-11-05 19:11           ` Greg KH
2014-11-05 19:44             ` Mark Langsdorf
2014-11-05 19:55               ` Greg KH
2014-11-05 20:41                 ` Arnd Bergmann
2014-11-05 22:05                   ` Greg KH
2014-11-13 18:36         ` Mark Langsdorf
2014-11-13 19:08           ` Greg KH
2014-11-18 20:05           ` Feng Kan
2014-11-18 20:33             ` Mark Langsdorf
2014-11-18 21:11               ` Feng Kan
2014-10-30 18:16 ` [PATCH 2/2] [usb] add support for APM X-Gene " Mark Langsdorf
2014-10-30 19:07   ` Arnd Bergmann
2014-10-30 20:12     ` Mark Langsdorf
2014-10-30 20:53       ` Arnd Bergmann

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=2609633.oChO4mb7il@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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