All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Rödel" <jroedel@suse.de>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	linux-usb@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
	Jon Grimm <jon.grimm@amd.com>,
	"Suthikulpanit, Suravee" <suravee.suthikulpanit@amd.com>
Subject: Re: DMA Faults with XHCI driver
Date: Mon, 4 Jul 2022 17:54:47 +0200	[thread overview]
Message-ID: <YsMNR9KtZVPMNC9Y@suse.de> (raw)
In-Reply-To: <cdd5b0b2-cfcd-3c25-6b77-2d20ebfc97c5@linux.intel.com>

Hi Mathias,

On Wed, Jun 29, 2022 at 05:39:49PM +0300, Mathias Nyman wrote:
> Anyway, maybe flushing the CRCR register by reading it back after writing it would help:

Thanks for your help and sorry for the delay. I tried the patch but it
didn't help, the io fault still appears and the device does not work.

I added some more debugging, actually printing the cmd_ring address read
by the calls you patch adds. Unfortunately they all returned 0, looks
like the register is write-only RAZ on this hardware.

Is it possible that the device actually can't handle a 64 bit DMA mask
and needs a smaller one, say 40 bits?

Regards,

-- 
Jörg Rödel
jroedel@suse.de

SUSE Software Solutions Germany GmbH
Frankenstraße 146
90461 Nürnberg
Germany

(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman


      reply	other threads:[~2022-07-04 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 14:38 DMA Faults with XHCI driver Jörg Rödel
2022-06-27 10:52 ` Mathias Nyman
2022-06-28  7:51   ` Jörg Rödel
2022-06-29 14:39     ` Mathias Nyman
2022-07-04 15:54       ` Jörg Rödel [this message]

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=YsMNR9KtZVPMNC9Y@suse.de \
    --to=jroedel@suse.de \
    --cc=jon.grimm@amd.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=mathias.nyman@linux.intel.com \
    --cc=robin.murphy@arm.com \
    --cc=suravee.suthikulpanit@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.