On 5/16/14, Doug Anderson <dianders@xxxxxxxxxxxx> wrote: > Kukjin, > > On Thu, May 15, 2014 at 12:38 PM, Kukjin Kim <kgene.kim@xxxxxxxxxxx> wrote: >> On 04/30/14 22:03, Ajay kumar wrote: >>> >>> Hi, >>> >> Hi, >> >>> On Tue, Apr 15, 2014 at 4:24 AM, Olof Johansson<olof@xxxxxxxxx> wrote: >>>> >>>> Hi Sachin, >>>> >>>> On Mon, Apr 14, 2014 at 6:16 AM, Sachin Kamat<sachin.kamat@xxxxxxxxxx> >>>> wrote: >>>>> >>>>> From: Doug Anderson<dianders@xxxxxxxxxxxx> >>>>> >>>>> Added nodes for ptn3460 driver to Snow board. >>>>> >>>>> Signed-off-by: Doug Anderson<dianders@xxxxxxxxxxxx> >>>>> Signed-off-by: Ajay Kumar<ajaykumar.rs@xxxxxxxxxxx> >>>>> Signed-off-by: Sachin Kamat<sachin.kamat@xxxxxxxxxx> >>>> >>>> >>>> I'm curious, how are you testing this code on the upstream kernel >>>> before you post the patches? >>>> >>>> Especially since Doug was referring to some of these containing parts >>>> that is needed for drivers that are not yet upstreamed. >>> >>> >>> Its better to ignore this patch as of now, since discussion is still >>> going >>> on, at http://www.spinics.net/lists/dri-devel/msg58474.html >>> I guess we will have few more DT bindings. Once it is finalized, >>> I shall resend this again. >>> >> This means this whole series? > > I think you can land everything except the last patch. I think you can take this ptn3460 DT patch also. Because, ptn3460 driver is already present in Inki's tree. Its true that the driver may need some changes, the discussions are still going on, and if we need to add a new DT binding, I will send that change as a seperate patch sometime down the line. As of now, this can go in (but I am sure we won't get the display until we keep FET1 and FET6 "always on" for snow) Ajay > The tps65090 charger portion of the MFD will fail to probe (assuming > it is configured) since we're still waiting for a review on > <https://patchwork.kernel.org/patch/4042741/>. ...but it doesn't hurt > to take the device tree part. > > -Doug > -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |