From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932447AbcJXRyK (ORCPT ); Mon, 24 Oct 2016 13:54:10 -0400 Received: from mail-qk0-f181.google.com ([209.85.220.181]:32842 "EHLO mail-qk0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933951AbcJXRyE (ORCPT ); Mon, 24 Oct 2016 13:54:04 -0400 MIME-Version: 1.0 In-Reply-To: <20161024174322.GN17252@sirena.org.uk> References: <20161024164634.4330-1-ahaslam@baylibre.com> <20161024164634.4330-10-ahaslam@baylibre.com> <20161024174322.GN17252@sirena.org.uk> From: Axel Haslam Date: Mon, 24 Oct 2016 19:53:22 +0200 Message-ID: Subject: Re: [PATCH/RFT v2 09/17] regulator: fixed: Add over current event To: Mark Brown Cc: Greg KH , Johan Hovold , robh+dt@kernel.org, Sekhar Nori , Alan Stern , Kevin Hilman , Sergei Shtylyov , David Lechner , manjunath.goudar@linaro.org, Alexandre Bailon , linux-usb@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Mark, On Mon, Oct 24, 2016 at 7:43 PM, Mark Brown wrote: > On Mon, Oct 24, 2016 at 06:46:26PM +0200, ahaslam@baylibre.com wrote: >> From: Axel Haslam >> >> Some regulator supplies have an over-current pin that is >> activated when the hw detects an over current condition. >> When this happens, the hardware enters a current limited >> mode. > > Please don't mix random enhancements like this into bigger system > specific RFC serieses, send them separately so they're easier to spot > and there's no confusion with dependencies and then reference them from > the system specific series when you post that. Ok, sorry i had mixed feelings on how to post all of it. there are several dependencies on the series and i kept all together to give the context. Do you want me to repost the regulator changes seperatly? I can do that, but if you don't agree with regulator handling overcurrent, i will have to move the over current gpio into the driver, and there is no point on re-posting that seperatly. Regards Axel From mboxrd@z Thu Jan 1 00:00:00 1970 From: ahaslam@baylibre.com (Axel Haslam) Date: Mon, 24 Oct 2016 19:53:22 +0200 Subject: [PATCH/RFT v2 09/17] regulator: fixed: Add over current event In-Reply-To: <20161024174322.GN17252@sirena.org.uk> References: <20161024164634.4330-1-ahaslam@baylibre.com> <20161024164634.4330-10-ahaslam@baylibre.com> <20161024174322.GN17252@sirena.org.uk> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Mark, On Mon, Oct 24, 2016 at 7:43 PM, Mark Brown wrote: > On Mon, Oct 24, 2016 at 06:46:26PM +0200, ahaslam at baylibre.com wrote: >> From: Axel Haslam >> >> Some regulator supplies have an over-current pin that is >> activated when the hw detects an over current condition. >> When this happens, the hardware enters a current limited >> mode. > > Please don't mix random enhancements like this into bigger system > specific RFC serieses, send them separately so they're easier to spot > and there's no confusion with dependencies and then reference them from > the system specific series when you post that. Ok, sorry i had mixed feelings on how to post all of it. there are several dependencies on the series and i kept all together to give the context. Do you want me to repost the regulator changes seperatly? I can do that, but if you don't agree with regulator handling overcurrent, i will have to move the over current gpio into the driver, and there is no point on re-posting that seperatly. Regards Axel