Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp3380946imm; Mon, 8 Oct 2018 03:06:05 -0700 (PDT) X-Google-Smtp-Source: ACcGV61mz9oxTd0LWFit1JKnUO260BDt47/cqiAZ+mjedyFniYIiCOGXWV3x61I4fVDKIuwEE06J X-Received: by 2002:a17:902:8eca:: with SMTP id x10-v6mr23254257plo.336.1538993164962; Mon, 08 Oct 2018 03:06:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538993164; cv=none; d=google.com; s=arc-20160816; b=iGC4w5WHnditWsZcXafyr8bdXrJo/Pb1JF+KUQQ0USDZxKeQ/mGPl5tbn8BiL4U5Et ezMK9C3C1ESm9oHRpFLXY/dUcnhA7Qi5IE/KaLCVYK7dkcwWuQacy1hEaYIKWJzbHmcG jcnOHSYYMRDy2pl+EdPMyQq8lHwr/LkhUA7wN8LixFzmPoqng60g8VuocgJCOvxudTJv FcbShYghPh+kql+0LYbvQu+WHIPviniI7KFsLyV4Y/5NwcDHn2FvX2g9S0DjdkS8hkaR p8//Q67iCIlzW9dsVdgUNbsoyUpdzhYiC6A2rUu8mpCcMus9l3qOrnPIBA22jI2Cpz86 Hlmg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=TE7ND3CbogZXI3wMX4fx25bsWwEqcNyS2dExp0szfnk=; b=CfRHyxGtKYbvnNUu5SHYPLSxT0EOs91fnPLREHQDLMpwbZD5eFoAGy0VMYARmJW9g9 1v0Mie21csrjOsOfLJ/SEABvu7XjK1ji50MrSsACjhbOL1pjD600MHFJgTN0efjJ0ZVN BoHoz1L79+CE6hIKadHb7FuKDB5wJHWl0D0D0HAmOlq87QsAXKwF78bUR84IU3XZM/RQ cAovDEC6HSgfQ56ziF4Nqub9zmVawElhAwcW3bl1raZrMkt57JNe79w1s414eSfTd5j1 MY2y2sXbwCB/4xQGVgmiG5JyDDpHU7mE7R+JKiB0PtEKmpfYiZRF5grtA90ULgAgXRTT tgfg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@as-electronics.de header.s=strato-dkim-0002 header.b=j47aglD5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g12-v6si9341655pfi.184.2018.10.08.03.05.49; Mon, 08 Oct 2018 03:06:04 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@as-electronics.de header.s=strato-dkim-0002 header.b=j47aglD5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727132AbeJHRQg (ORCPT + 99 others); Mon, 8 Oct 2018 13:16:36 -0400 Received: from mo4-p05-ob.smtp.rzone.de ([85.215.255.136]:24840 "EHLO mo4-p05-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726511AbeJHRQg (ORCPT ); Mon, 8 Oct 2018 13:16:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1538993138; s=strato-dkim-0002; d=as-electronics.de; h=In-Reply-To:Date:Message-ID:From:References:Cc:To:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=TE7ND3CbogZXI3wMX4fx25bsWwEqcNyS2dExp0szfnk=; b=j47aglD5+3D0FlFeHuSAMKVGrOYCFbG0tCv/kscnDzROI4pqsTaOOQUPnrSw1LfBgH flx2K0mqC100FM9LIMs5TdmYqYVXogYyapZfZMss5p1mk06GrXX8dvZ5v827lWVIrOOF isftgKnOyeDyfxyG5qdSAUUl3TiDJnVYjReng1xEUdPEyNxg55D3VD19d+Is5xxBdHML H6BMAJC+z4lZDFBm0YdE2evbuZ/veNDTNu2VzJj/WLzzaxWQxIeh/pAnsGnUPJOJH6az HhF89sa3KNtSUBZMXwSwOXvYd3MeiUxICvM1RefxZ5rI6mYmlpJeNw78nvssQBIw9pH6 OsQg== X-RZG-AUTH: ":LX8JdEmkW/4tAFwMkcNJIloh1hrA5u3owhPk7bdT5Fx2zAOrX/r2ZbrrxoyMly7vtKoBCSu4zR9/f0shzjGSYbJY5KbsbrlTGd0CtJA=" X-RZG-CLASS-ID: mo05 Received: from [IPv6:2003:a:e7a:6200:246c:2a8b:f45a:a33d] by smtp.strato.de (RZmta 44.2 AUTH) with ESMTPSA id h039efu989rMGgx (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Mon, 8 Oct 2018 11:53:22 +0200 (CEST) Subject: Re: [PATCH 2/2] mmc: Add mmc_force_detect_change_begin / _end functions To: Maxime Ripard , Hans de Goede , quentin.schulz@free-electrons.com Cc: ulf.hansson@linaro.org, gregkh@linuxfoundation.org, linus.walleij@linaro.org, shawn.lin@rock-chips.com, adrian.hunter@intel.com, baolin.wang@linaro.org, thomas.petazzoni@free-electrons.com, linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org, devel@driverdev.osuosl.org, icenowy@aosc.xyz, wens@csie.org References: <20180927081452.a2xw25sdoqtadntu@flea> From: Frieder Schrempf Message-ID: <85c2baea-8dbb-ef1b-93d2-7749c5a100e6@exceet.de> Date: Mon, 8 Oct 2018 11:53:21 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180927081452.a2xw25sdoqtadntu@flea> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 27.09.2018 10:14, Maxime Ripard wrote: > On Wed, Sep 26, 2018 at 10:19:22PM +0200, Hans de Goede wrote: >> On 26-09-18 16:44, Frieder Schrempf wrote: >>> Hi, >>> >>> On Fri, Feb 09, 2018 at 03:01:00PM +0100, Ulf Hansson wrote: >>>> [...] >>>> >>>>>>> I'd like to know if any progress has been made on that problem >>> (I may >>>>>>> have missed patches). >>>>>>> Had you had the time to look at the issue? >>>>>> >>>>>> I have looked at the issue, but not manage to cook some patches >>> for it. >>>>>> >>>>>> However, it's on my top of my TODO list for mmc. No promises, but >>>>>> perhaps and hopefully I manage to get something posted during the >>>>>> coming release cycle. >>> >>> I would be interested in a ESP8089 driver in mainline and that's why I want to pick up this discussion. >>> >>> What is the current status of the "mmc_reprobe_device" implementation, that Hans was explaining and Ulf wanted to provide some months ago? >> >> Ulf did eventually write a new way to deal with this and then Quentin >> did manage to get the esp8089 driver to work with it, the new function >> to use for this is added by this commit: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/mmc/core?id=1433269c4d2461be1f36db5dbb453976b38996ff >> >> I'm not sure what the status of upstreaming the ep8089 driver is now >> that we've this in place. >> >> Quentin, do you have a version of the esp8089 driver somewhere >> which will work correctly with the new mmc_sw_reset() function? >> >> Also what is the status of adding this driver to say staging? > > IIRC, we tried to get it into staging, and we got told that it was too > nice for staging at this point. So we're basically stuck somewhere > between staging and !staging, with the driver being too nice for the > former, and not nice enough for the latter :) Ok, and is there someone willing to continue upstreaming the driver? Maybe someone can rebase and resend the latest approach? After all it looks like a lot of work has already been done. Thanks, Frieder