From: Christoph Hellwig <hch@lst.de>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Jens Axboe <axboe@kernel.dk>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH 17/17] mmc: pass queue_limits to blk_mq_alloc_disk
Date: Thu, 27 Jun 2024 13:19:41 +0200 [thread overview]
Message-ID: <20240627111941.GA4523@lst.de> (raw)
In-Reply-To: <23aa9894-f913-409d-a385-8813711e2898@nvidia.com>
On Thu, Jun 27, 2024 at 10:58:58AM +0100, Jon Hunter wrote:
>
> On 27/06/2024 10:49, Christoph Hellwig wrote:
>> On Thu, Jun 27, 2024 at 10:43:24AM +0100, Jon Hunter wrote:
>>> We have just noticed that since Linux v6.9 was released, that if we
>>> build the kernel with 64kB MMU pages, then we see the following WARNING
>>> and probe failure ...
>>
>> The old code upgraded the limits to the PAGE_SIZE for this case after
>> issunig a warning. Your driver probably incorrectly advertised the
>> lower max_segment_size. Try setting it to 64k. I would have sent you
>> a patch for that, but I can't see what mmc host driver you are using.
>
>
> We are using the sdhci-tegra.c driver. I don't see it set in there, but I
> see references to max_seg_size in the main sdhci.c driver.
sdhci-tegra.c sets SDHCI_QUIRK_BROKEN_ADMA_ZEROLEN_DESC for various
devices, I guess you have one od those? This sounds like the device
might not actually need it, but I'll need help from the SDHCI and
tegra maintainers here.
next prev parent reply other threads:[~2024-06-27 11:19 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 7:02 pass queue_limits to blk_mq_alloc_disk for simple drivers Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:02 ` [PATCH 01/17] ubd: pass queue_limits to blk_mq_alloc_disk Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:02 ` [PATCH 02/17] aoe: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:02 ` [PATCH 03/17] floppy: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-19 6:39 ` Denis Efremov (Oracle)
2024-02-15 7:02 ` [PATCH 04/17] mtip: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:02 ` [PATCH 05/17] nbd: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:02 ` [PATCH 06/17] ps3disk: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:02 ` [PATCH 07/17] rbd: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-20 11:18 ` Ilya Dryomov
2024-02-20 11:18 ` Ilya Dryomov
2024-02-15 7:02 ` [PATCH 08/17] rnbd-clt: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-16 7:49 ` Jinpu Wang
2024-02-16 7:49 ` Jinpu Wang
2024-02-15 7:02 ` [PATCH 09/17] sunvdc: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:02 ` [PATCH 10/17] gdrom: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:02 ` [PATCH 11/17] ms_block: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:02 ` [PATCH 12/17] mspro_block: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:02 ` [PATCH 13/17] mtd_blkdevs: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:02 ` [PATCH 14/17] ubiblock: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-18 2:33 ` Zhihao Cheng
2024-02-18 2:33 ` Zhihao Cheng
2024-02-15 7:02 ` [PATCH 15/17] scm_blk: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:02 ` [PATCH 16/17] ublk: " Christoph Hellwig
2024-02-15 7:02 ` Christoph Hellwig
2024-02-15 7:03 ` [PATCH 17/17] mmc: " Christoph Hellwig
2024-02-15 7:03 ` Christoph Hellwig
2024-02-15 16:40 ` Ulf Hansson
2024-02-15 16:40 ` Ulf Hansson
2024-02-15 16:49 ` Christoph Hellwig
2024-02-15 16:49 ` Christoph Hellwig
2024-02-15 16:53 ` Ulf Hansson
2024-02-15 16:53 ` Ulf Hansson
2024-02-20 22:01 ` Geert Uytterhoeven
2024-02-20 22:01 ` Geert Uytterhoeven
2024-02-20 22:14 ` Geert Uytterhoeven
2024-02-20 22:14 ` Geert Uytterhoeven
2024-02-21 5:44 ` Christoph Hellwig
2024-02-21 5:44 ` Christoph Hellwig
2024-02-21 9:37 ` Geert Uytterhoeven
2024-02-21 9:37 ` Geert Uytterhoeven
2024-06-27 9:43 ` Jon Hunter
2024-06-27 9:43 ` Jon Hunter
2024-06-27 9:49 ` Christoph Hellwig
2024-06-27 9:49 ` Christoph Hellwig
2024-06-27 9:58 ` Jon Hunter
2024-06-27 9:58 ` Jon Hunter
2024-06-27 11:19 ` Christoph Hellwig [this message]
2024-06-27 12:30 ` Jon Hunter
2024-06-27 12:44 ` Christoph Hellwig
2024-06-27 13:09 ` Jon Hunter
2024-06-27 13:44 ` Adrian Hunter
2024-06-27 14:47 ` Christoph Hellwig
2024-06-28 8:06 ` Adrian Hunter
2024-06-28 12:32 ` Christoph Hellwig
2024-06-28 12:37 ` Adrian Hunter
2024-06-28 12:51 ` Christoph Hellwig
2024-06-28 13:45 ` Adrian Hunter
2024-07-03 8:22 ` Jon Hunter
2024-07-04 7:24 ` Christoph Hellwig
2024-06-28 9:05 ` Jon Hunter
2024-02-20 13:22 ` pass queue_limits to blk_mq_alloc_disk for simple drivers Jens Axboe
2024-02-20 13:22 ` Jens Axboe
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=20240627111941.GA4523@lst.de \
--to=hch@lst.de \
--cc=adrian.hunter@intel.com \
--cc=axboe@kernel.dk \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.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 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.