Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751491AbdCOIWF convert rfc822-to-8bit (ORCPT ); Wed, 15 Mar 2017 04:22:05 -0400 Received: from mx1.redhat.com ([209.132.183.28]:53302 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751113AbdCOIWC (ORCPT ); Wed, 15 Mar 2017 04:22:02 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com B167580462 Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=kraxel@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com B167580462 Message-ID: <1489566118.15659.27.camel@redhat.com> Subject: Re: [PATCH v3 0/7] mmc: bcm2835: Add new driver for the sdhost controller From: Gerd Hoffmann To: Peter Robinson Cc: linux-rpi-kernel@lists.infradead.org, mark.rutland@arm.com, devicetree@vger.kernel.org, ulf.hansson@linaro.org, f.fainelli@gmail.com, sbranden@broadcom.com, rjui@broadcom.com, lee@kernel.org, will.deacon@arm.com, linux@armlinux.org.uk, linux-kernel@vger.kernel.org, robh+dt@kernel.org, bcm-kernel-feedback-list@broadcom.com, catalin.marinas@arm.com, linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org Date: Wed, 15 Mar 2017 09:21:58 +0100 In-Reply-To: References: <1487668026-7100-1-git-send-email-kraxel@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Mime-Version: 1.0 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Wed, 15 Mar 2017 08:22:02 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3555 Lines: 77 Hi, > First the flipping of the mmc host driver for the SD card slot will > cause issues for users that build it as a module. When I tested this > on Fedora the first update I ended up with a system that didn't boot. Yep, switching drivers is a pain point here indeed. Possibly we could fix that by adding a MODULE_SOFTDEP() to the iproc driver? Comments? Better ideas? > Also i often see the device hang for a long period when systemd probes > for rfkill status, sometimes it needs to be reset but it generally > gets there. What device is that? rpi3 with wifi? > [ 6.529079] Hardware name: Generic DT based system > [ 6.529106] [] (unwind_backtrace) from [] > (show_stack+0x18/0x1c) > [ 6.529122] [] (show_stack) from [] > (dump_stack+0x80/0xa0) > [ 6.529137] [] (dump_stack) from [] (__warn+0xe4/0x104) > [ 6.529150] [] (__warn) from [] > (warn_slowpath_fmt+0x3c/0x4c) > [ 6.529166] [] (warn_slowpath_fmt) from [] > (check_flush_dependency+0xac/0x134) > [ 6.529184] [] (check_flush_dependency) from [] > (flush_work+0xa0/0x178) > [ 6.529201] [] (flush_work) from [] > (drain_all_pages+0x1a8/0x1cc) > [ 6.529221] [] (drain_all_pages) from [] > (start_isolate_page_range+0x168/0x1b4) > [ 6.529239] [] (start_isolate_page_range) from > [] (alloc_contig_range+0xd4/0x314) > [ 6.529258] [] (alloc_contig_range) from [] > (cma_alloc+0x188/0x300) > [ 6.529275] [] (cma_alloc) from [] > (__alloc_from_contiguous+0x40/0xd8) > [ 6.529290] [] (__alloc_from_contiguous) from > [] (cma_allocator_alloc+0x3c/0x44) > [ 6.529303] [] (cma_allocator_alloc) from [] > (__dma_alloc+0x1d4/0x2f0) > [ 6.529317] [] (__dma_alloc) from [] > (arm_dma_alloc+0x3c/0x48) > [ 6.529331] [] (arm_dma_alloc) from [] > (dma_pool_alloc+0x124/0x240) > [ 6.529356] [] (dma_pool_alloc) from [] > (bcm2835_dma_create_cb_chain+0xb0/0x1dc [bcm2835_dma]) > [ 6.529385] [] (bcm2835_dma_create_cb_chain > [bcm2835_dma]) from [] (bcm2835_dma_prep_slave_sg+0xf0/0x25c > [bcm2835_dma]) > [ 6.529418] [] (bcm2835_dma_prep_slave_sg [bcm2835_dma]) > from [] (bcm2835_request+0x2a4/0x3f4 [bcm2835]) > [ 6.529548] [] (bcm2835_request [bcm2835]) from > [] (mmc_start_request+0x1f8/0x264 [mmc_core]) > [ 6.529756] [] (mmc_start_request [mmc_core]) from > [] (mmc_start_areq+0x2c8/0x318 [mmc_core]) > [ 6.529890] [] (mmc_start_areq [mmc_core]) from > [] (mmc_blk_issue_rw_rq+0xc0/0x308 [mmc_block]) > [ 6.529943] [] (mmc_blk_issue_rw_rq [mmc_block]) from > [] (mmc_blk_issue_rq+0x418/0x428 [mmc_block]) > [ 6.529997] [] (mmc_blk_issue_rq [mmc_block]) from > [] (mmc_queue_thread+0x148/0x1bc [mmc_block]) > [ 6.530031] [] (mmc_queue_thread [mmc_block]) from > [] (kthread+0x120/0x138) > [ 6.530049] [] (kthread) from [] > (ret_from_fork+0x14/0x3c) > [ 6.530055] ---[ end trace 221a5a14ca55fa22 ]--- > [ 6.545765] mmcblk0: p1 p2 p3 p4 > [ 6.566015] random: fast init done > [ 6.623699] mmc1: new high speed SDIO card at address 0001 Looks more like a cma allocator issue on a quick glance. cheers, Gerd