Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1690932yba; Tue, 2 Apr 2019 13:53:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqzlsMt9camWHwdqPHxadhzh409+RNUTo6l90BOzzFu1Q0KcKg1Wzvd3BGuOUZ+BVRJjVaJ+ X-Received: by 2002:a63:6a45:: with SMTP id f66mr49181476pgc.7.1554238400366; Tue, 02 Apr 2019 13:53:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554238400; cv=none; d=google.com; s=arc-20160816; b=fkduf1CJOQifVi1kD1zFG7EiMbXELMndtbZc1YnFK77MNzbL5GyUkuXtmTU6vnIkHi p6v21ImgbpDq+S9qb6Znh9tig2nFerh+ySB8lOFbw+Fk7xSV67PhH/dGqnaL7jhrOQeT kylOTvv8Qaik031UiK3KLicSXZCnoWjbWtM4tJKkF6OE/LL/JSoTlcNslHJyz+uUmkHQ sABA1dTVVgrRH5XrLZdooeH8N1H/a3hLpfSl1txTSoW9yoTtSkBmXAJCwS3m/4BWVH78 3NpdzQqbW7QkyxvIqc2sTXAth1xLLypZEYDWHH3pJj42s3HF/g5yXMHE3R7k/H+V1+yD riGg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date; bh=1E5wn8vkpyrFjzESzxeBcpAZidf6YHl036efs/kOgKs=; b=04pwMg5hmRR7CoLBlQpP8IpyxXWIngZupZN4v697zKHvkTnWQG/oxkCuVToYxhtsX7 1b/0ATcSSA7pPVFvBtjFCoxbuK8+GsKy0omA61GiQDr2mUjIuhX/5bapmvfTwJ7OzVSv 1cQXXBgQMTotM/8SkHmH6x3FfucfqHlNWTnMGkJ4WMQx2AlNjJFcqMVLl4SGUQqzlN2P mVCcrysLOdMW55SEQ7sl+GChUGV7oJ/TEGptUyjr9W1nJnAqDzZzawlUrk022ectROS5 yAMws9l8RiAU0ow5lQ4y5yA4u+S7I0gimtwj99rN8YkFNwwdtiL9txoFE7Ff9gaC/ads lU3Q== ARC-Authentication-Results: i=1; mx.google.com; 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 h6si11997296pfd.115.2019.04.02.13.53.04; Tue, 02 Apr 2019 13:53:20 -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; 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 S1726411AbfDBUw0 (ORCPT + 99 others); Tue, 2 Apr 2019 16:52:26 -0400 Received: from volans.uberspace.de ([95.143.172.210]:35240 "EHLO volans.uberspace.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725842AbfDBUwZ (ORCPT ); Tue, 2 Apr 2019 16:52:25 -0400 X-Greylist: delayed 399 seconds by postgrey-1.27 at vger.kernel.org; Tue, 02 Apr 2019 16:52:25 EDT Received: (qmail 21952 invoked by uid 691); 2 Apr 2019 20:45:43 -0000 Received: from habor by volans.uberspace.de with BSMTP; 2 Apr 2019 20:45:43 -0000 Received: by habor.lkamp.de (Postfix, from userid 1000) id A04255A00B4; Tue, 2 Apr 2019 22:46:58 +0200 (CEST) Date: Tue, 2 Apr 2019 22:46:58 +0200 From: Christian =?iso-8859-1?Q?L=FCtke-Stetzkamp?= To: NeilBrown Cc: George Hilliard , Greg Kroah-Hartman , devel@driverdev.osuosl.org, Nishad Kamdar , linux-kernel@vger.kernel.org, Sergej Perschin , Matthias Brugger , John Crispin Subject: Re: [PATCH 03/16] staging: m57621-mmc: delete driver from the tree. Message-ID: <20190402204658.GA5187@habor.localdomain> Mail-Followup-To: NeilBrown , George Hilliard , Greg Kroah-Hartman , devel@driverdev.osuosl.org, Nishad Kamdar , linux-kernel@vger.kernel.org, Sergej Perschin , Matthias Brugger , John Crispin References: <20190402103203.14959-1-gregkh@linuxfoundation.org> <20190402103203.14959-4-gregkh@linuxfoundation.org> <87r2ak18yy.fsf@notabene.neil.brown.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87r2ak18yy.fsf@notabene.neil.brown.name> User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 03, 2019 at 06:51:49AM +1100, NeilBrown wrote: > People keep telling me that drivers/mmc/host/mtk-sd.c should be able to > handle the same hardware as this driver, with a little bit of work. > Unfortunately they haven't told me what the little bit of work involves. > > Have you explored that possibility at all? I might try to have a look > if I can make time. I have started to look into it, when I was working on that driver. First sorry for me doing nothing in the last few month. Generally the two drivers seem to be very similar, the main difference is the code for tuning. In the staging driver. this is a total mess. It tries to account for tuning itself, so it also tries to account which command was executed (succesfully) before a tuning is necessary and reexecutes it, when it was the APP_CMD. But there are still some differences in the tuning code, that are not due to handling it in the driver. If have mainly understand how to remove the 'in driver handling' of the tuning and thing I could prepare a patch for that. But the differences in the tuning code itself, I do not understand completely. There are two other larger differences that I found during my work. One is that drivers/mmc/host/mtk-sd.c has much more features, like voltage and clock handling and some support for high speed modes. I don't know if these features are required/useful for this device. The other thing is the card detect handling. This driver is doing the card detect / read only detection on its own, where the in tree one just uses some default gpio functions there and I don't know weather this must be changed or weather there is a gpio driver for the mt7621. That is all I currently remember. Hope it helps. Christian