devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Assmann <sassmann@kpanic.de>
To: Mark Brown <broonie@kernel.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	linux@arm.linux.org.uk, pawel.moll@arm.com,
	ijc+devicetree@hellion.org.uk, robh+dt@kernel.org,
	galak@codeaurora.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC 2/2] regulator: twl: Re-add clk32kg to get wifi working
Date: Mon, 14 Jul 2014 14:05:19 +0200	[thread overview]
Message-ID: <53C3C77F.7080208@kpanic.de> (raw)
In-Reply-To: <20140714120051.GF6800@sirena.org.uk>

On 14.07.2014 14:00, Mark Brown wrote:
> On Mon, Jul 14, 2014 at 01:50:55PM +0200, Stefan Assmann wrote:
>> This partly reverts the following commits to get the wifi working on
>> the Pandaboard OMAP4430 ES2.2.
>
>> 0e8e5c34cf1a8beaaf0a6a05c053592693bf8cb4 regulator: twl: Remove references to 32kHz clock from DT bindings
>> d1924519fe1dada0cfd9a228bf2ff1ea15840c84 regulator: twl: Remove TWL6030_FIXED_RESOURCE
>> 029dd3cefa46ecdd879f9b4e2df3bdf4371cc22c regulator: twl: Remove another unused variable warning
>> e76ab829cc2d8b6350a3f01fffb208df4d7d8c1b regulator: twl: Remove references to the twl4030 regulator
>
> No, you need to implement clocks using the clock API.  Please read the
> changelogs for the above commits...
>

Yes, that's what I expected. Got any pointers for me how to do this?
Never done that before, a little help would be appreciated.

   Stefan

  reply	other threads:[~2014-07-14 12:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 11:50 [PATCH RFC 0/2] Enable wifi on pandaboard Stefan Assmann
     [not found] ` <1405338655-18415-1-git-send-email-sassmann-llIHtaV5axyzQB+pC5nmwQ@public.gmane.org>
2014-07-14 11:50   ` [PATCH RFC 1/2] dts: regulator-clk32kg should always be enabled Stefan Assmann
2014-07-14 11:50   ` [PATCH RFC 2/2] regulator: twl: Re-add clk32kg to get wifi working Stefan Assmann
     [not found]     ` <1405338655-18415-3-git-send-email-sassmann-llIHtaV5axyzQB+pC5nmwQ@public.gmane.org>
2014-07-14 12:00       ` Mark Brown
2014-07-14 12:05         ` Stefan Assmann [this message]
     [not found]           ` <53C3C77F.7080208-llIHtaV5axyzQB+pC5nmwQ@public.gmane.org>
2014-07-14 18:13             ` Mark Brown
     [not found]               ` <20140714181338.GR6800-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-07-15 12:59                 ` Stefan Assmann
     [not found]                   ` <53C525A2.8080609-llIHtaV5axyzQB+pC5nmwQ@public.gmane.org>
2014-07-16 21:23                     ` Mark Brown
     [not found]                       ` <20140716212340.GZ17528-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-07-17  8:36                         ` Stefan Assmann
     [not found]                           ` <53C78B20.6010602-llIHtaV5axyzQB+pC5nmwQ@public.gmane.org>
2014-07-17  9:58                             ` Mark Brown
2014-07-24 15:03                         ` Stefan Assmann
     [not found]                           ` <53D12044.1060500-llIHtaV5axyzQB+pC5nmwQ@public.gmane.org>
2014-07-24 17:39                             ` Mark Brown
2014-07-29  1:27                             ` Mike Turquette

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=53C3C77F.7080208@kpanic.de \
    --to=sassmann@kpanic.de \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@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 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).