From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [REBASED 2/5] regulator: pwm-regulator: Separate voltage-table initialisation
Date: Wed, 10 Jun 2015 10:10:27 +0100 [thread overview]
Message-ID: <20150610091027.GB2982@x1> (raw)
In-Reply-To: <20150610110206.6194cc0f@ipc1.ka-ro>
Oh my ...
On Wed, 10 Jun 2015, Lothar Wa?mann wrote:
> > Take this out of the main .probe() routine in order to facilitate the
> > introduction of different ways to obtain 'duty cycle' information.
> >
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
> > ---
> > drivers/mfd/mfd-child.c | 47 ++++++++++++++++++++++++
> > drivers/regulator/pwm-regulator.c | 77 +++++++++++++++++++++++----------------
> > 2 files changed, 92 insertions(+), 32 deletions(-)
> > create mode 100644 drivers/mfd/mfd-child.c
> >
> > diff --git a/drivers/mfd/mfd-child.c b/drivers/mfd/mfd-child.c
> > new file mode 100644
> > index 0000000..f233add
> > --- /dev/null
> > +++ b/drivers/mfd/mfd-child.c
> > @@ -0,0 +1,47 @@
> > +#include <linux/interrupt.h>
> > +#include <linux/module.h>
> > +#include <linux/of_device.h>
> > +#include <linux/of_irq.h>
> > +
> > +static int simple_mfd_child_probe(struct platform_device *pdev)
> > +{
> > + struct resource *res;
> > + void __iomem *base;
> > + int irq;
> > +
> > + printk("LEE: %s %s()[%d]: Enter\n", __FILE__, __func__, __LINE__);
> > +
> Debugging remnant?
>
> > + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> > + dev_err(&pdev->dev, "Phys: %x: %x\n", res->start, resource_size(res));
> > +
> That's not an error message and thus shouldn't be printed with
> dev_err(). dev_dbg() would be more appropriate here.
This entire file is cruft and has nothing to do with this set.
It was knocked it up quickly to test something unrelated.
I will resubmit this patch with it removed.
Sorry for the noise.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: "Lothar Waßmann" <LW@KARO-electronics.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, broonie@kernel.org,
kernel@stlinux.com, lgirdwood@gmail.com
Subject: Re: [REBASED 2/5] regulator: pwm-regulator: Separate voltage-table initialisation
Date: Wed, 10 Jun 2015 10:10:27 +0100 [thread overview]
Message-ID: <20150610091027.GB2982@x1> (raw)
In-Reply-To: <20150610110206.6194cc0f@ipc1.ka-ro>
Oh my ...
On Wed, 10 Jun 2015, Lothar Waßmann wrote:
> > Take this out of the main .probe() routine in order to facilitate the
> > introduction of different ways to obtain 'duty cycle' information.
> >
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
> > ---
> > drivers/mfd/mfd-child.c | 47 ++++++++++++++++++++++++
> > drivers/regulator/pwm-regulator.c | 77 +++++++++++++++++++++++----------------
> > 2 files changed, 92 insertions(+), 32 deletions(-)
> > create mode 100644 drivers/mfd/mfd-child.c
> >
> > diff --git a/drivers/mfd/mfd-child.c b/drivers/mfd/mfd-child.c
> > new file mode 100644
> > index 0000000..f233add
> > --- /dev/null
> > +++ b/drivers/mfd/mfd-child.c
> > @@ -0,0 +1,47 @@
> > +#include <linux/interrupt.h>
> > +#include <linux/module.h>
> > +#include <linux/of_device.h>
> > +#include <linux/of_irq.h>
> > +
> > +static int simple_mfd_child_probe(struct platform_device *pdev)
> > +{
> > + struct resource *res;
> > + void __iomem *base;
> > + int irq;
> > +
> > + printk("LEE: %s %s()[%d]: Enter\n", __FILE__, __func__, __LINE__);
> > +
> Debugging remnant?
>
> > + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> > + dev_err(&pdev->dev, "Phys: %x: %x\n", res->start, resource_size(res));
> > +
> That's not an error message and thus shouldn't be printed with
> dev_err(). dev_dbg() would be more appropriate here.
This entire file is cruft and has nothing to do with this set.
It was knocked it up quickly to test something unrelated.
I will resubmit this patch with it removed.
Sorry for the noise.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-06-10 9:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 7:57 [REBASED 0/5] regulator: pwm-regulator: Introduce continuous-mode Lee Jones
2015-06-10 7:57 ` Lee Jones
2015-06-10 7:57 ` [REBASED 1/5] ARM: STi: STiH407: Add PWM Regulator node Lee Jones
2015-06-10 7:57 ` Lee Jones
2015-06-10 7:57 ` [REBASED 2/5] regulator: pwm-regulator: Separate voltage-table initialisation Lee Jones
2015-06-10 7:57 ` Lee Jones
2015-06-10 9:02 ` Lothar Waßmann
2015-06-10 9:02 ` Lothar Waßmann
2015-06-10 9:10 ` Lee Jones [this message]
2015-06-10 9:10 ` Lee Jones
2015-06-10 9:15 ` [REBASED v1.1 " Lee Jones
2015-06-10 7:57 ` [REBASED 3/5] regulator: pwm-regulator: Add support for continuous-voltage Lee Jones
2015-06-10 7:57 ` Lee Jones
2015-06-10 7:57 ` [REBASED 4/5] dt: regulator: pwm-regulator: Re-write bindings Lee Jones
2015-06-10 7:57 ` Lee Jones
2015-06-10 7:57 ` [REBASED 5/5] regulator: pwm-regulator: Don't assign structure attributes right away Lee Jones
2015-06-10 7:57 ` Lee Jones
2015-07-07 18:30 ` Applied "regulator: pwm-regulator: Don't assign structure attributes right away" to the regulator tree Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150610091027.GB2982@x1 \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.