From: Lee Jones <lee.jones@linaro.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 2/2] mfd: twl6040: Register child device for twl6040-pdmclk
Date: Tue, 27 Sep 2016 19:50:21 +0100 [thread overview]
Message-ID: <20160927185021.GH21388@dell> (raw)
In-Reply-To: <3edeea3c-e9a0-f397-e1ec-204393383823@ti.com>
On Tue, 27 Sep 2016, Peter Ujfalusi wrote:
> On 08/31/16 17:39, Lee Jones wrote:
> > On Wed, 31 Aug 2016, Peter Ujfalusi wrote:
> >
> >> The McPDM in OMAP4/5 is using the pdmclk from twl6040 as functional clock.
> >> The twl6040-pdmclk driver provides a clock which can be used to make sure
> >> that the pdmclk is active when the McPDM is in use.
> >>
> >> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> >> Acked-by: Rob Herring <robh@kernel.org>
> >> ---
> >> Documentation/devicetree/bindings/mfd/twl6040.txt | 1 +
> >> drivers/mfd/twl6040.c | 5 +++++
> >> include/linux/mfd/twl6040.h | 2 +-
> >> 3 files changed, 7 insertions(+), 1 deletion(-)
> >
> > Applied, thanks.
>
> Lee, for some reason this patch is not found in linux-next (20160927). I can
> see patch 1, but this one is missing.
You're right, it had been dropped. My apologies.
It's been applied now.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2016-09-27 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 11:46 [PATCH RESEND 0/2] mfd: twl6040: bulk access fix and pdmclk registration Peter Ujfalusi
2016-08-31 11:46 ` [PATCH RESEND 1/2] mfd: twl6040: The chip does not support bulk access Peter Ujfalusi
2016-08-31 14:39 ` Lee Jones
2016-08-31 11:46 ` [PATCH RESEND 2/2] mfd: twl6040: Register child device for twl6040-pdmclk Peter Ujfalusi
2016-08-31 14:38 ` Lee Jones
2016-08-31 14:39 ` Lee Jones
2016-09-27 8:14 ` Peter Ujfalusi
2016-09-27 18:50 ` Lee Jones [this message]
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=20160927185021.GH21388@dell \
--to=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
/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).