All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Mark Brown <broonie@kernel.org>
Cc: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	Pawel Moll <pawel.moll@arm.com>, Rob Herring <robh+dt@kernel.org>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Shawn Guo <shawn.guo@linaro.org>,
	Fabio Estevam <festevam@gmail.com>,
	Sebastian Reichel <sre@kernel.org>,
	linux-pm@vger.kernel.org,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Mark Rutland <mark.rutland@arm.com>, Marek Vasut <marex@denx.de>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH RFC 2/3] power: mxs_power: add driver for mxs power subsystem
Date: Tue, 27 Jan 2015 19:35:09 +0100 (CET)	[thread overview]
Message-ID: <1954124242.301697.1422383709733.JavaMail.open-xchange@oxbaltgw09.schlund.de> (raw)
In-Reply-To: <20150127001629.GP21293@sirena.org.uk>

Hi Mark,

> Mark Brown <broonie@kernel.org> hat am 27. Januar 2015 um 01:16 geschrieben:
>
>
> On Mon, Jan 26, 2015 at 08:46:45PM +0100, Stefan Wahren wrote:
>
> > > > Does a common property name exists for the switching frequency or would
> > > > it be vendor specific?
>
> > > As far as I know most regulators have fixed switching frequencies,
> > > so there is no common property name so far. I added regulator
> > > framework people, since this property should be regulator specific.
>
> No, it's pretty common for there to be a couple of options - there's
> normally a performance tradeoff (power for regulation accuracy and/or
> cost) which can be selected. IIRC it's selected at design time as it
> affect the choice of passives on the board.
>
> > okay i understand. But doesn't it need a extra driver to set the switching
> > frequency because of the new compatible string?
>
> I don't understand this bit at all, sorry.

Sebastian suggested a new sub-node in the devicetree:

    powerpll {
        compatible = "fsl,imx28-power-pll"
        #clock-cells = <0>;
        clock-frequency = <12345>;
    }

and i think that the new compatible string needs a separate driver to take care
of the switching frequency.

Or is it okay to leave the handling of the switching frequency in the mxs-power
driver?

Btw if we add a new node to set switching frequency, i think it would be better
to describe the dc-dc convertor and not the pll:

    dcdc {
       compatible = "fsl,imx28-dcdc"
       frequency = <12345>;
    }

What do you think?

Best regards
Stefan

>
> >
> > At this point i think about moving this feature into the bootloader.
> >
> > @Fabio, @Marek:
> >
> > What's your opinion about that?
> >
> > >
> > > -- Sebastian
> >
> > Stefan
> >

WARNING: multiple messages have this Message-ID (diff)
From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 2/3] power: mxs_power: add driver for mxs power subsystem
Date: Tue, 27 Jan 2015 19:35:09 +0100 (CET)	[thread overview]
Message-ID: <1954124242.301697.1422383709733.JavaMail.open-xchange@oxbaltgw09.schlund.de> (raw)
In-Reply-To: <20150127001629.GP21293@sirena.org.uk>

Hi Mark,

> Mark Brown <broonie@kernel.org> hat am 27. Januar 2015 um 01:16 geschrieben:
>
>
> On Mon, Jan 26, 2015 at 08:46:45PM +0100, Stefan Wahren wrote:
>
> > > > Does a common property name exists for the switching frequency or would
> > > > it be vendor specific?
>
> > > As far as I know most regulators have fixed switching frequencies,
> > > so there is no common property name so far. I added regulator
> > > framework people, since this property should be regulator specific.
>
> No, it's pretty common for there to be a couple of options - there's
> normally a performance tradeoff (power for regulation accuracy and/or
> cost) which can be selected. IIRC it's selected at design time as it
> affect the choice of passives on the board.
>
> > okay i understand. But doesn't it need a extra driver to set the switching
> > frequency because of the new compatible string?
>
> I don't understand this bit at all, sorry.

Sebastian suggested a new sub-node in the devicetree:

    powerpll {
        compatible = "fsl,imx28-power-pll"
        #clock-cells = <0>;
        clock-frequency = <12345>;
    }

and i think that the new compatible string needs a separate driver to take care
of the switching frequency.

Or is it okay to leave the handling of the switching frequency in the mxs-power
driver?

Btw if we add a new node to set switching frequency, i think it would be better
to describe the dc-dc convertor and not the pll:

    dcdc {
       compatible = "fsl,imx28-dcdc"
       frequency = <12345>;
    }

What do you think?

Best regards
Stefan

>
> >
> > At this point i think about moving this feature into the bootloader.
> >
> > @Fabio, @Marek:
> >
> > What's your opinion about that?
> >
> > >
> > > -- Sebastian
> >
> > Stefan
> >

  reply	other threads:[~2015-01-27 18:35 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 20:14 [PATCH RFC 0/3] power: mxs_power: add driver for mxs power subsystem Stefan Wahren
2014-11-20 20:14 ` Stefan Wahren
2014-11-20 20:14 ` [PATCH RFC 1/3] DT: add binding " Stefan Wahren
2014-11-20 20:14   ` Stefan Wahren
2014-11-20 20:14 ` [PATCH RFC 2/3] power: mxs_power: add driver " Stefan Wahren
2014-11-20 20:14   ` Stefan Wahren
2015-01-21 23:01   ` Sebastian Reichel
2015-01-21 23:01     ` Sebastian Reichel
2015-01-22  8:08     ` Stefan Wahren
2015-01-22  8:08       ` Stefan Wahren
2015-01-22  9:37       ` Sébastien SZYMANSKI
2015-01-22  9:37         ` Sébastien SZYMANSKI
2015-01-22  9:48         ` Stefan Wahren
2015-01-22  9:48           ` Stefan Wahren
     [not found]       ` <54C0AFE4.3020701-eS4NqCHxEME@public.gmane.org>
2015-01-25 15:04         ` Sebastian Reichel
2015-01-25 15:04           ` Sebastian Reichel
     [not found]           ` <20150125150431.GE2719-SfvFxonMDyemK9LvCR3Hrw@public.gmane.org>
2015-01-26 19:46             ` Stefan Wahren
2015-01-26 19:46               ` Stefan Wahren
2015-01-27  0:16               ` Mark Brown
2015-01-27  0:16                 ` Mark Brown
2015-01-27 18:35                 ` Stefan Wahren [this message]
2015-01-27 18:35                   ` Stefan Wahren
     [not found]                   ` <1954124242.301697.1422383709733.JavaMail.open-xchange-h4m1HHXQYNE54XbDmwzAWMgmgJlYmuWJ@public.gmane.org>
2015-01-27 19:43                     ` Mark Brown
2015-01-27 19:43                       ` Mark Brown
2015-01-28 22:22                       ` Stefan Wahren
2015-01-28 22:22                         ` Stefan Wahren
2015-01-28 22:59                         ` Sebastian Reichel
2015-01-28 22:59                           ` Sebastian Reichel
     [not found]                           ` <20150128225937.GA12749-SfvFxonMDyemK9LvCR3Hrw@public.gmane.org>
2015-02-03 20:41                             ` Stefan Wahren
2015-02-03 20:41                               ` Stefan Wahren
2015-02-20 10:57                               ` Stefan Wahren
2015-02-20 10:57                                 ` Stefan Wahren
     [not found]                                 ` <1766258118.893447.1424429861770.JavaMail.open-xchange-h4m1HHXQYNGvCDav5jC2oMgmgJlYmuWJ@public.gmane.org>
2015-02-23 15:38                                   ` Sebastian Reichel
2015-02-23 15:38                                     ` Sebastian Reichel
2015-02-26 19:20                                     ` Stefan Wahren
2015-02-26 19:20                                       ` Stefan Wahren
2014-11-20 20:14 ` [PATCH RFC 3/3] ARM: dts: enable power subsystem for i.MX28 Stefan Wahren
2014-11-20 20:14   ` Stefan Wahren
2014-11-20 21:32   ` Fabio Estevam
2014-11-20 21:32     ` Fabio Estevam
2014-11-20 22:57     ` Stefan Wahren
2014-11-20 22:57       ` Stefan Wahren
2014-11-21 13:55       ` Fabio Estevam
2014-11-21 13:55         ` Fabio Estevam
2014-11-26 10:26 ` [PATCH RFC 0/3] power: mxs_power: add driver for mxs power subsystem Stefan Wahren
2014-11-26 10:26   ` Stefan Wahren

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=1954124242.301697.1422383709733.JavaMail.open-xchange@oxbaltgw09.schlund.de \
    --to=stefan.wahren@i2se.com \
    --cc=broonie@kernel.org \
    --cc=dbaryshkov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=festevam@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kernel@pengutronix.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawn.guo@linaro.org \
    --cc=sre@kernel.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.