Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1640388imm; Tue, 10 Jul 2018 05:35:23 -0700 (PDT) X-Google-Smtp-Source: AAOMgpco7JLEDrPtqALCX0WcEcr/CrbFygFBQzfPyReWSTSj6xbJ8dnQZDq1ffi22mWfKB9jRhmq X-Received: by 2002:a63:6604:: with SMTP id a4-v6mr13020606pgc.404.1531226123462; Tue, 10 Jul 2018 05:35:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531226123; cv=none; d=google.com; s=arc-20160816; b=kMH0k1lJ2zvQ8M9xg0MS0LSQCZqduHPicSvEYpA7D5RuUQK92wS+JxDl5FZw9mq1aU OmX6Wi3DfcntLrfQziqEsHMRflHTROEAPAQLjWaKO3X9GDahnp6H6PnWpQ68PIiTHPib k4x7Zc4Qw+qO+PBt76pxTeled1+Xuv23d8xNgJyU72KSP51rByWn8sBq2zXp501NWFhi nSSmkUx6ygiz5TFjDZlp3N/IAfya+mE+f59IJh4rqIAtWfhnmuB3ESPfF1RBXodlWTaY kXyxVntYKQInvaHakhOODkxIqkPon355YbVc9zNFlrkrZfdKdpdlsYW9okCYWO5tqLAQ PTtA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:from:cc:to:subject :content-transfer-encoding:mime-version:references:in-reply-to:date :arc-authentication-results; bh=DQMHleuaMDaaMbrjDSrukgnLEjxGwygn+XkS+2WI8As=; b=eh33KMsRbc2usPZSIoCgQo8WOoute7P982G1coNrjAnSMJUfczfAbZm87++baToy3E kWxYXc998gBoFaQJPDTOSFzD1Uv/dgj4R4SdfSChuSu32DZzKocJBFapYqK0zUGXOdyQ p1hmPtVs3Ugh/EsA4atuNyP61qmHV5OjaAMFFHf7pFSVcNaNCjtxFRwkCxr07ETW5xLO 4c1RgJ1mCw+hR+NbimWjASVUBz88tD6hxkysEPayDqHk25pljQSiGnc+1wvzDk6fq56G eGmSyD4e6FR+V9j0kjYZWDCpRiiCFXaGxHExS1Ytf5hdipyxSmhh02/88s9ey7pUq/x/ CsJw== 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 c187-v6si17528228pfa.152.2018.07.10.05.34.44; Tue, 10 Jul 2018 05:35:23 -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 S933307AbeGJMc7 convert rfc822-to-8bit (ORCPT + 99 others); Tue, 10 Jul 2018 08:32:59 -0400 Received: from hermes.aosc.io ([199.195.250.187]:59155 "EHLO hermes.aosc.io" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932752AbeGJMc5 (ORCPT ); Tue, 10 Jul 2018 08:32:57 -0400 Received: from localhost (localhost [127.0.0.1]) (Authenticated sender: icenowy@aosc.io) by hermes.aosc.io (Postfix) with ESMTPSA id 017AA6490A; Tue, 10 Jul 2018 12:32:45 +0000 (UTC) Date: Tue, 10 Jul 2018 20:32:27 +0800 In-Reply-To: <20180710122922.6sgmgfislqwhn3tt@flea> References: <1531149658-27030-1-git-send-email-clabbe@baylibre.com> <20180710122922.6sgmgfislqwhn3tt@flea> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Subject: Re: [PATCH v2 0/4] sun8i: r40: add AHCI To: Maxime Ripard , Corentin Labbe CC: linux@armlinux.org.uk, mark.rutland@arm.com, robh+dt@kernel.org, tj@kernel.org, wens@csie.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com From: Icenowy Zheng Message-ID: <3F7BD4FD-D8D8-4900-BC53-E2C1928616A4@aosc.io> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 于 2018年7月10日 GMT+08:00 下午8:29:22, Maxime Ripard 写到: >On Mon, Jul 09, 2018 at 03:20:54PM +0000, Corentin Labbe wrote: >> Hello >> >> With Moeicenowy's agreement, I have take leadership ot this patchset. >> >> There are no really changes appart renaming struct quirck to variant. >> >> Since the last serie is really old, I will answer comment here. >> The two regulator (1.2 and 2.5V) are not for the PHY since: >> - nothing in the schematic said that they are for the PHY, they seems >> only for controller >> - all other AHCI driver use 5V for the target/PHY (vs 1.2/2.5 which >> cannot be used for target) > >That's a pretty bad thing to do, especially for old series. You just >dropped all the context that you reply to, and there's no way for any >reviewer to tell if your answers make any kind of sense, or addresses >any question one might have had. > >> Furthermore, the AHCI binding support only one regulator per PHY, so >> using the "target" regulator is out of question for registring this >two >> non-phy regulator. > >Nothing is "out of question", we have the source code and can change >it if needed. The main problem is that he misunderstood the meaning of target regulator -- it's not for PHY but for disk. And if a device is designed to accept both 2.5" and 3.5" HDD at the same port multiple target regulator might really be useful -- one 5v and one 12v. > >Maxime