Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp536469ybl; Wed, 8 Jan 2020 01:26:39 -0800 (PST) X-Google-Smtp-Source: APXvYqwEg1ysM/aafZhM/0jiqd4QTDezYqCYNdTzoCWoJ3j3SKiUkLwxamdd5K2vW0hYo+b2QDlf X-Received: by 2002:aca:cf58:: with SMTP id f85mr2376717oig.6.1578475599319; Wed, 08 Jan 2020 01:26:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578475599; cv=none; d=google.com; s=arc-20160816; b=nqqvOMFBPt4/w119sDBN1s9K3tCj5X+ZspwpzGrVu7eLAuajFumxnzb3hFnkbsRCiZ HUNP4jlyXRWq9TmFHQqBx/bJh58i07rT2rOxLJQfd7HRwPKg7pQxY+DxaxfrG0pVjJWV ZO3bikY1Hwl2xG9x4TZ3YXlq9rqb6gwKRYIVzC6VwLv4zsrYwpWrlcQb2z3y2z4ygFrw 7N2Qtmoo7llqZWA0Jkc361w2YzbFiSk3N7QcGIBOUr1Whr+4xVce+yRyeOgyoJg0ViA6 gUWtjlHLOYFaG4Sk7AVyG5q2Kp/sjVzKxTpTG2CGNyibiiyr5KXXLF4RP/CMob+SMBYD zQ0A== 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:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=+CsYxoJH/YqtLAViqGMTjYWTn78rzbKILW+jWukpKUY=; b=tZnqF7hJtLluU1EXIiHjlkK3OlRhtVI9yNPU/2knknlxANJ6/TWusqdnJMGTjlziKh 5XJYwVy+pOpBW09S3edn34MDssDR7dLHsK7QDIMI/oLb5STGx9RDjQxaUiLoBYOtlku6 g8fCwM0xm+BYjMg7aCEDtCgoUrCXK9nNRGlCsyGBtHKGoIQAr/J/JwNhuTtj+BXcnjVX uiID3ISD/mJc3z/AF54iJrqdOiPqYQCLW8cVXOYsEG4gTC4z6YFpSYUFnwb8xhGLJf0+ +MAb0fIcIOzkgJyuqwWHb5Exks5V46EqF5QAu74J0wreD3LW0fvrOjRQzZVcIUNhmXe8 VdAg== 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 h3si1561803otq.203.2020.01.08.01.26.23; Wed, 08 Jan 2020 01:26:39 -0800 (PST) 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 S1727557AbgAHJZG (ORCPT + 99 others); Wed, 8 Jan 2020 04:25:06 -0500 Received: from metis.ext.pengutronix.de ([85.220.165.71]:38393 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726913AbgAHJZG (ORCPT ); Wed, 8 Jan 2020 04:25:06 -0500 Received: from lupine.hi.pengutronix.de ([2001:67c:670:100:3ad5:47ff:feaf:1a17] helo=lupine) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1ip7aK-0008O9-E7; Wed, 08 Jan 2020 10:25:04 +0100 Message-ID: Subject: Re: [PATCH v3 0/3] ata: ahci_brcm: Follow-up changes for BCM7216 From: Philipp Zabel To: Florian Fainelli , linux-kernel@vger.kernel.org Cc: bcm-kernel-feedback-list@broadcom.com, Jens Axboe , Rob Herring , Mark Rutland , Hans de Goede , Tejun Heo , Jaedon Shin , "open list:LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" Date: Wed, 08 Jan 2020 10:25:03 +0100 In-Reply-To: <20200107183022.26224-1-f.fainelli@gmail.com> References: <20200107183022.26224-1-f.fainelli@gmail.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5-1.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:100:3ad5:47ff:feaf:1a17 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Florian, On Tue, 2020-01-07 at 10:30 -0800, Florian Fainelli wrote: > Hi Jens, Philipp, > > These three patches are a follow-up to my previous series titled: ata: > ahci_brcm: Fixes and new device support. > > After submitting the BCM7216 RESCAL reset driver, Philipp the reset > controller maintained indicated that the reset line should be self > de-asserting and so reset_control_reset() should be used instead. > > These three patches update the driver in that regard. It would be great if > you could apply those and get them queued up for 5.6 since they are > directly related to the previous series. > > Changes in v3: > - introduced a preliminary patch making use of the proper reset control > API in order to manage the optional reset controller line > - updated patches after introducing that preliminary patch The third patch could be simplified by storing the rescal reset control in a separate struct member and relying on the optional reset control API more. This is just a suggestion though, the series looks fine as-is. Reviewed-by: Philipp Zabel regards Philipp