From mboxrd@z Thu Jan 1 00:00:00 1970 From: Srinivas Kandagatla Subject: Re: [PATCH v2 3/5] thermal: imx: Add support for reading OCOTP through nvmem Date: Tue, 8 Aug 2017 12:44:45 +0100 Message-ID: <9732c524-fbdc-d1be-cd03-089dbb2266c4@linaro.org> References: <20170725080835.GD20064@dragon> <1502176915.4296.1.camel@intel.com> <26407dd5-a9b1-67c0-c4ab-d97fa0b88b79@linaro.org> <1502192287.24350.9.camel@nxp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1502192287.24350.9.camel@nxp.com> Content-Language: en-US Sender: linux-pm-owner@vger.kernel.org To: Leonard Crestez , Zhang Rui , Shawn Guo Cc: Rob Herring , Eduardo Valentin , Mark Rutland , =?UTF-8?Q?Lothar_Wa=c3=9fmann?= , Dong Aisheng , Bai Ping , Anson Huang , Octavian Purdila , Fabio Estevam , linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: devicetree@vger.kernel.org On 08/08/17 12:38, Leonard Crestez wrote: > On Tue, 2017-08-08 at 12:00 +0100, Srinivas Kandagatla wrote: >> On 08/08/17 08:21, Zhang Rui wrote: >>> On Tue, 2017-07-25 at 16:08 +0800, Shawn Guo wrote: >>>> On Fri, Jul 14, 2017 at 05:11:08PM +0300, Leonard Crestez wrote: > >>>>> On newer imx SOCs accessing OCOTP directly is wrong because the >>>>> ocotp clock >>>>> needs to be enabled first. Add support for reading those same >>>>> values through >>>>> the nvmem API instead. >>>>> >>>>> The older path is preserved for compatibility with older dts and >>>>> because it >>>>> works correctly on imx6qdl chips. >>>>> >>>>> Signed-off-by: Leonard Crestez >>>> Acked-by: Shawn Guo > >>> I'm okay with the thermal change. >>> We still need ACK for the nvmem changes in this patch series. > >> NVMEM changes are already sent to Greg K H with other patches >> (https://lkml.org/lkml/2017/7/26/164), should appear in next. > > These patches have a compile-time dependency on each other. Wouldn't it > make more sense for the whole series to go through a single maintainer > tree, atomically? Most of the changes are in driver/thermal. I was expecting that the nvmem change go in as fix in a rc release so that you could apply the other patches after that. Let me ping Greg about this!! > > I'm really very confused about how series that touch multiple areas are > applied. It seems to be a mostly ad-hoc process. > > -- > Regards, > Leonard >