linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sre@kernel.org (Sebastian Reichel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 2/3] power: mxs_power: add driver for mxs power subsystem
Date: Sun, 25 Jan 2015 16:04:31 +0100	[thread overview]
Message-ID: <20150125150431.GE2719@earth.universe> (raw)
In-Reply-To: <54C0AFE4.3020701@i2se.com>

Hi,

[add maintainers from regulator framework]

On Thu, Jan 22, 2015 at 09:08:04AM +0100, Stefan Wahren wrote:
> Am 22.01.2015 um 00:01 schrieb Sebastian Reichel:
> > On Thu, Nov 20, 2014 at 08:14:36PM +0000, Stefan Wahren wrote:
> >> This patch adds a minimal driver for the Freescale i.MX23, i.MX28
> >> power subsystem. It's required to trigger the probing of the underlying
> >> drivers like on-chip regulators. Additionally the drivers supports
> >> the configuration of the DC-DC clock frequency to avoid possible
> >> interferences.
> > I would expect PLL to be board specific and part of DT. Why is it
> > specified as parameter?
> 
> I think the switching frequency of the DC-DC belongs to the
> configuration and don't describe how the hardware is connected. But i
> don't have a problem to change it into a DT property.
> 
> 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.

Apart from introducing a custom/common switching-frequency property
the dts could also expose the PLL like this and use the common
clock-frequency property:

power: power at 80044000 {
    compatible = "fsl,imx28-power";
    #address-cells = <1>;
    #size-cells = <1>;
    reg = <0x80044000 0x2000>;
    interrupts = <6>;
    ranges;

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

-- Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150125/5af2c464/attachment.sig>

  parent reply	other threads:[~2015-01-25 15:04 UTC|newest]

Thread overview: 23+ 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 ` [PATCH RFC 1/3] DT: add binding " Stefan Wahren
2014-11-20 20:14 ` [PATCH RFC 2/3] power: mxs_power: add driver " Stefan Wahren
2015-01-21 23:01   ` Sebastian Reichel
2015-01-22  8:08     ` Stefan Wahren
2015-01-22  9:37       ` Sébastien SZYMANSKI
2015-01-22  9:48         ` Stefan Wahren
2015-01-25 15:04       ` Sebastian Reichel [this message]
2015-01-26 19:46         ` Stefan Wahren
2015-01-27  0:16           ` Mark Brown
2015-01-27 18:35             ` Stefan Wahren
2015-01-27 19:43               ` Mark Brown
2015-01-28 22:22                 ` Stefan Wahren
2015-01-28 22:59                   ` Sebastian Reichel
2015-02-03 20:41                     ` Stefan Wahren
2015-02-20 10:57                       ` Stefan Wahren
2015-02-23 15:38                         ` Sebastian Reichel
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 21:32   ` Fabio Estevam
2014-11-20 22:57     ` Stefan Wahren
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

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=20150125150431.GE2719@earth.universe \
    --to=sre@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).