Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753237Ab3DOPF0 (ORCPT ); Mon, 15 Apr 2013 11:05:26 -0400 Received: from mail-lb0-f180.google.com ([209.85.217.180]:50507 "EHLO mail-lb0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753161Ab3DOPFY (ORCPT ); Mon, 15 Apr 2013 11:05:24 -0400 MIME-Version: 1.0 In-Reply-To: <001701ce39d2$c0dbf8c0$4293ea40$%jun@samsung.com> References: <1365698338-27503-1-git-send-email-dianders@chromium.org> <001701ce39d2$c0dbf8c0$4293ea40$%jun@samsung.com> Date: Mon, 15 Apr 2013 08:05:22 -0700 X-Google-Sender-Auth: cwLJ4M2WCW8UYNDiSDu_zbzLQzc Message-ID: Subject: Re: [PATCH] mmc: dw_mmc: exynos: Turn SDIO interrupts on From: Doug Anderson To: Seungwon Jeon Cc: Chris Ball , Thomas Abraham , Bing Zhao , Jaehoon Chung , Sachin Kamat , Olof Johansson , "linux-mmc@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1472 Lines: 39 Seungwon, On Mon, Apr 15, 2013 at 5:14 AM, Seungwon Jeon wrote: >> + MMC_CAP_8_BIT_DATA | MMC_CAP_CMD23 | MMC_CAP_SDIO_IRQ, >> + MMC_CAP_CMD23 | MMC_CAP_SDIO_IRQ, > This line for [1] >> + MMC_CAP_CMD23 | MMC_CAP_SDIO_IRQ, >> + MMC_CAP_CMD23 | MMC_CAP_SDIO_IRQ, > [1] is for mshc1. mshc1 is only used for SDIO. > As I know, The others are improper for SDIO. I'm nearly certain that all of the ports are OK for SDIO. Specifically: * On the ARM Chromebook (exynos5250) we are using mmc3 (12230000) for the SDIO connection to WiFi. * I have plugged in an external WiFi module to the SD card slot on the ARM Chromebook and seen it work (including interrupts). This is mmc2 (12220000). * I have seen a board where mmc1 was wired up to WiFi and seen it work. It is possible that mmc0 wouldn't work for SDIO. I've never tested it since mmc0 is intended for eMMC and every system I've worked with has eMMC on that port. There is some evidence that mmc0 would work for SDIO, though: there is a muxing slot on GPC0[2] for SD_0_CARD_INT_n. That implies that mmc0 ought to also work for SDIO (and even could be configured for an external eSDIO interrupt, I guess). Thanks! -Doug -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/