Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Vaibhav Hiremath Newsgroups: linux.kernel Subject: Re: [PATCH 0/5] mmc: sdhci-pxav3: Enable support for PXA1928 SDCHI controller Date: Mon, 07 Sep 2015 12:40:02 +0200 Message-ID: References: X-Original-To: linux-mmc@vger.kernel.org X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=R6a35GsNsmpx/l3r7VyS1E2UtwoyC1bzM6aLywqbujE=; b=cIU1IorwMANCEvW8oWq/hpYW/a/jIRlPR8sCuUEItpmHF7Mt4+AVuch/0YEcZODufC m9RlwR0dTa8ZK7dSqFSAJ/+LHJwPKQNJ7cqrXZxX2MVJIhW9G6U6BNs5qhD0tl8t0UDQ fgV+UMrE+WXWfJ0T0cJOlo449GF2oH1sd70sb3do/eUjf39yfMp5sBGUwTymZEOhL2aC 49onftoxE7g5os/6YV6M8AWr9Bjy3ywE69yazbZwZUtJrQDtj3e6SsQSx8Ej8ff1RTjw RLaHNZw5P036tBU1XaxhJayJrFHbFTMBFASyzkAhLV9p5/j9ZG+rAuTBVmJv5tH+vvSE g9Ew== X-Gm-Message-State: ALoCoQnLf8Q3FE9M4c+agZS+QH+80PVHJXXPddS9FexHBU3nWyJisGEeegWstwEWE4iJBRbADHnB X-Received: by 10.68.103.5 with SMTP id fs5mr44745471pbb.55.1441622170333; Mon, 07 Sep 2015 03:36:10 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: robomod@news.nic.it List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Approved: robomod@news.nic.it Lines: 69 Organization: linux.* mail to news gateway X-Original-Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kliu5@marvell.com, ulf.hansson@linaro.org X-Original-Date: Mon, 7 Sep 2015 16:06:05 +0530 X-Original-Message-ID: <55ED6895.7000404@linaro.org> X-Original-References: <1441380741-13115-1-git-send-email-vaibhav.hiremath@linaro.org> X-Original-Sender: linux-kernel-owner@vger.kernel.org Xref: csiph.com linux.kernel:1220043 On Friday 04 September 2015 09:02 PM, Vaibhav Hiremath wrote: > PXA1928 SDHCI controller has few differences, for example, > > PXAxxx PXA1928 > ====== ======= > SDCLK_DELAY field 0x10A 0x114 > SDCLK_DELAY mask 0x1F 0x3FF > SDCLK_DELAY shift 9 8 > SDCLK_SEL shift 8 2 (SEL1) > > So this patch series introduces new compatible device_id > (marvell,pxav3-1928-sdhci), and makes use of .data for handling > such differences. > > The series also adds support like, > > - independent ->set_clock() api, as we need to enable internal clock gate > and TX clock > - pinctrl configuration based on bus speed. > - introduce new quirk SDHCI_QUIRK2_MUST_SET_SDHCI_BUS_POWER > SD_BUS_POWER & SD_BUS_VLT bit-fields are used internally to gate the > clocks, so it is important to configure them as part of ->set_power() > More detailed description is written into commit log. > - Enable SDHCI_QUIRK_BROKEN_TIMEOUT_VAL for PXA1928 device_id > Please ignore this series, as one residual change (rather typo error). Mistakenly while checking in the code, instead of 1928 compatible property it was 988. I will submit the new series shortly. Thanks, Vaibhav > > Testing: > I have done basic testing on both eMMC and SD card on PXA1928 based > platform. > > Note: I tried to made sure that I do not break any other platform, which > used sdhci, except HS200 configuration. > Unfortunately I do not have access to any other datasheets, where I can > cross check the details on HS200 bit-fields. Probably someone who has > access can confirm [PATCH 4/5], whether it impacts other platforms. > > Kevin Liu (1): > mmc: sdhci-pxav3: Fix HS200 mode support > > Vaibhav Hiremath (4): > mmc: sdhci-pxav3: Enable pxa1928 device support > mmc: sdhci-pxav3: Add platform specific set_clock ops > mmc: sdhci-pxav3: Add pinctl setting according to bus clock > mmc: sdhci: add new quirk for setting BUS_POWER & BUS_VLT fields > > drivers/mmc/host/sdhci-pltfm.c | 3 + > drivers/mmc/host/sdhci-pxav3.c | 168 ++++++++++++++++++++++++++++++++++++++--- > drivers/mmc/host/sdhci.c | 3 +- > drivers/mmc/host/sdhci.h | 2 + > 4 files changed, 163 insertions(+), 13 deletions(-) > -- 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/