From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Brugger Subject: Re: [PATCH v2 0/3] Mediatek EFUSE Support Date: Mon, 1 Feb 2016 11:23:34 +0100 Message-ID: <56AF3226.2070304@gmail.com> References: <1447930014-19579-1-git-send-email-andrew-ct.chen@mediatek.com> <566E94CA.1050700@linaro.org> <56A0A5E1.5050105@gmail.com> <56A0EBF0.2020703@linaro.org> <56A0EF61.5080500@gmail.com> <56A0EFEA.506@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <56A0EFEA.506@linaro.org> Sender: linux-kernel-owner@vger.kernel.org To: Srinivas Kandagatla , Daniel Kurtz , Andrew-CT Chen Cc: Maxime Ripard , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Sascha Hauer , "open list:OPEN FIRMWARE AND..." , "linux-arm-kernel@lists.infradead.org" , linux-mediatek@lists.infradead.org, "linux-kernel@vger.kernel.org" , srv_heupstream List-Id: devicetree@vger.kernel.org On 21/01/16 15:49, Srinivas Kandagatla wrote: > > > On 21/01/16 14:46, Matthias Brugger wrote: >> >> >> On 21/01/16 15:32, Srinivas Kandagatla wrote: >>> >>> >>> On 21/01/16 09:33, Matthias Brugger wrote: >>>> >>>> >>>> On 14/12/15 11:07, Srinivas Kandagatla wrote: >>>>> Hi Andrew, >>>>> >>>>> On 14/12/15 04:27, Daniel Kurtz wrote: >>>>>> Hi Srinivas, >>>>>> >>>>>> On Thu, Nov 19, 2015 at 6:46 PM, Andrew-CT Chen >>>>>> wrote: >>>>>>> This patch adds EFUSE support driver which is used by other drivers >>>>>>> like thermal sensor and HDMI impedance. >>>>>>> >>>>>>> There are some efuses these fuses store things like calibration >>>>>>> data, >>>>>>> speed bins.. etc. Drivers like thermal sensor, HDMI impedance would >>>>>>> read out this data for configuring the driver. >>>>>>> >>>>>>> Change in v2: >>>>>>> 1. Rebase to 4.4-rc1 >>>>>>> 2. Modify the driver Makefile for more consistent with other drivers >>>>>>> 3. Modify the compatible string to "mediatek,mt8173-efuse" and >>>>>>> "mediatek,efuse" >>>>>> >>>>>> Do you still plan to queue this for v4.5? >>>>>> >>>>> Sorry guys, for the long delay in replying your pings, got busy with >>>>> regular office stuff :-) >>>>> >>>>> Yes, It should go in v4.5, I did send request with my sign-off to >>>>> Greg, >>>>> he should take it via char-misc tree. >>>>> >>>> >>>> I can't see this patches in the char-misc tree [1]. >>>> Can you please double check? >>> >>> Hi Matthias, >>> Thanks for the patience. You should expect them to see after v4.5-rc1, >>> that's when Greg said he would push the patches. >>> >> >> I'm a bit puzzled. Wouldn't that mean that they will get into mainline >> for v4.6. > > The delay was due to Christmas holidays, this driver is 4.5 material, so > it would endup in v4.5-rc2 instead of v4.5-rc1. Sorry for bothering you on this again, but I just checked v4.5-rc2 and it is not present. I don't see it in char-misc-[next,testing] neither. Looks like as if this patch got forgotten. Can you please check. Regards, Matthias > > thanks > srini >> I just want to know if I can take patch 3/3 through my v4.5-next branch >> (which eventually will be merged into v4.6-rc1) or if I have to wait. > >> >> Thanks, >> Matthias