From: Christoph Hellwig <hch@infradead.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Vinayak Holikatti <vinholikatti@gmail.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH] scsi: ufs: Consider device limitations for dma_mask
Date: Mon, 14 Jan 2019 09:36:59 -0800 [thread overview]
Message-ID: <20190114173659.GA17788@infradead.org> (raw)
In-Reply-To: <20190114173051.GA9278@minitux>
On Mon, Jan 14, 2019 at 09:30:51AM -0800, Bjorn Andersson wrote:
> The problem here is that the capability bit states that the controller
> itself claim to be able to deal with 64-bit addresses, which is probably
> true. The thing that the struct device represents (the integrated
> controller, on a bus in this SoC) doesn't.
>
> The device model accurately handles this and carries a dma_mask that's
> appropriate for the device in this system - the capability is not.
>
> > You either need to introduce a quirk or a way to communicate the
> > different limit so that it can be set by the core.
>
> The system's limit is already communicated in hba->dev->dma_mask, but
> the ufshcd driver overwrites this. I expect that this would make sense
> if the device model claims we can do e.g. 40 bit addressing, but the
> 64-bit capability is not set in the controller - in which case ufshcd
> would accurately lower this to 32-bits.
No, that is absolutely not true. dev->dma_mask is set by the driver
to what the driver based on the device specsheet/register claims to
support. dev->bus_dma_mask contains any additional limits imposed
by the bus/system, but that is handled transparently by the dma mapping
code.
next prev parent reply other threads:[~2019-01-14 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 22:54 [PATCH] scsi: ufs: Consider device limitations for dma_mask Bjorn Andersson
2019-01-11 23:33 ` Doug Anderson
2019-01-12 17:46 ` Bjorn Andersson
2019-01-14 11:11 ` Christoph Hellwig
2019-01-14 17:30 ` Bjorn Andersson
2019-01-14 17:36 ` Christoph Hellwig [this message]
2019-01-14 20:23 ` Bjorn Andersson
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=20190114173659.GA17788@infradead.org \
--to=hch@infradead.org \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=jejb@linux.ibm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=vinholikatti@gmail.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.