| Message ID | 1437393151-5362-1-git-send-email-vaibhav.hiremath@linaro.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Mon, 20 Jul 2015, Vaibhav Hiremath wrote: > Add chip identification support for 88PM860 device > to the pm80x_chip_mapping table. > > Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org> > Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com> > --- > drivers/mfd/88pm80x.c | 2 ++ > include/linux/mfd/88pm80x.h | 1 + > 2 files changed, 3 insertions(+) Acked-by: Lee Jones <lee.jones@linaro.org> > diff --git a/drivers/mfd/88pm80x.c b/drivers/mfd/88pm80x.c > index 5e72f65..63445ea 100644 > --- a/drivers/mfd/88pm80x.c > +++ b/drivers/mfd/88pm80x.c > @@ -33,6 +33,8 @@ static struct pm80x_chip_mapping chip_mapping[] = { > {0x3, CHIP_PM800}, > /* 88PM805 chip id number */ > {0x0, CHIP_PM805}, > + /* 88PM860 chip id number */ > + {0x4, CHIP_PM860}, > }; > > /* > diff --git a/include/linux/mfd/88pm80x.h b/include/linux/mfd/88pm80x.h > index 9c5773b..2e25fb1 100644 > --- a/include/linux/mfd/88pm80x.h > +++ b/include/linux/mfd/88pm80x.h > @@ -21,6 +21,7 @@ enum { > CHIP_INVALID = 0, > CHIP_PM800, > CHIP_PM805, > + CHIP_PM860, > CHIP_MAX, > }; >
On Monday 20 July 2015 05:22 PM, Vaibhav Hiremath wrote: > Add chip identification support for 88PM860 device > to the pm80x_chip_mapping table. > > Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org> > Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com> > --- > drivers/mfd/88pm80x.c | 2 ++ > include/linux/mfd/88pm80x.h | 1 + > 2 files changed, 3 insertions(+) > Mark, Last update/understanding which I have on this patch is, Lee is OK with taking this patch from regulator tree. Lee please let me know if you think otherwise. With this patch in, the build dependency will go away. Request to pick this patch into your topic/88pm800 branch and run build test. Thanks, Vaibhav
On Mon, Aug 24, 2015 at 12:32:17PM +0530, Vaibhav Hiremath wrote: > On Monday 20 July 2015 05:22 PM, Vaibhav Hiremath wrote: > >Add chip identification support for 88PM860 device > >to the pm80x_chip_mapping table. > Last update/understanding which I have on this patch is, > > Lee is OK with taking this patch from regulator tree. > Lee please let me know if you think otherwise. > > With this patch in, the build dependency will go away. > > Request to pick this patch into your topic/88pm800 branch and run build > test. Please don't send content free pings, they just waste time. I can't review or apply content free pings. Please submit patches following the process in SubmittingPatches. The chances are I deleted this mail unread since it is a MFD patch...
On Tuesday 25 August 2015 12:08 PM, Mark Brown wrote: > On Mon, Aug 24, 2015 at 12:32:17PM +0530, Vaibhav Hiremath wrote: >> On Monday 20 July 2015 05:22 PM, Vaibhav Hiremath wrote: >>> Add chip identification support for 88PM860 device >>> to the pm80x_chip_mapping table. > >> Last update/understanding which I have on this patch is, >> >> Lee is OK with taking this patch from regulator tree. >> Lee please let me know if you think otherwise. >> >> With this patch in, the build dependency will go away. >> >> Request to pick this patch into your topic/88pm800 branch and run build >> test. > > Please don't send content free pings, they just waste time. I can't > review or apply content free pings. Please submit patches following the > process in SubmittingPatches. > > The chances are I deleted this mail unread since it is a MFD patch... > Hmmm Ok, Resending now... Thanks, Vaibhav
diff --git a/drivers/mfd/88pm80x.c b/drivers/mfd/88pm80x.c index 5e72f65..63445ea 100644 --- a/drivers/mfd/88pm80x.c +++ b/drivers/mfd/88pm80x.c @@ -33,6 +33,8 @@ static struct pm80x_chip_mapping chip_mapping[] = { {0x3, CHIP_PM800}, /* 88PM805 chip id number */ {0x0, CHIP_PM805}, + /* 88PM860 chip id number */ + {0x4, CHIP_PM860}, }; /* diff --git a/include/linux/mfd/88pm80x.h b/include/linux/mfd/88pm80x.h index 9c5773b..2e25fb1 100644 --- a/include/linux/mfd/88pm80x.h +++ b/include/linux/mfd/88pm80x.h @@ -21,6 +21,7 @@ enum { CHIP_INVALID = 0, CHIP_PM800, CHIP_PM805, + CHIP_PM860, CHIP_MAX, };