From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Sekhar Nori <nsekhar@ti.com>, Kevin Hilman <khilman@baylibre.com>,
Russell King <linux@armlinux.org.uk>,
Santosh Shilimkar <santosh.shilimkar@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
arm-soc <linux-arm-kernel@lists.infradead.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH RESEND 0/2] ARM: davinci: improve the nand clock lookup
Date: Fri, 13 Jan 2017 11:00:24 +0100 [thread overview]
Message-ID: <1484301626-30345-1-git-send-email-bgolaszewski@baylibre.com> (raw)
Hi Greg,
Santosh acked patch 1/2, but suggested that it go through your tree.
Can you pick it up for 4.11?
Sekhar, will you pick up patch 2/2 for the davinci tree or should it
go together with 1/2?
---------
This is a follow-up to the series fixing the da850 clocks.
Instead of having a half-measure of leaving out the dev_id from the
clock lookup table, make the aemif driver capable of accessing it
over platform data.
Tested with da850-lcdk.
Bartosz Golaszewski (2):
memory: aemif: allow passing device lookup table as platform data
ARM: da850: add the nand dev_id to the clock lookup table
arch/arm/mach-davinci/da850.c | 10 +---------
arch/arm/mach-davinci/da8xx-dt.c | 12 +++++++++++-
drivers/memory/ti-aemif.c | 8 +++++++-
include/linux/platform_data/ti-aemif.h | 23 +++++++++++++++++++++++
4 files changed, 42 insertions(+), 11 deletions(-)
create mode 100644 include/linux/platform_data/ti-aemif.h
--
2.9.3
next reply other threads:[~2017-01-13 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 10:00 Bartosz Golaszewski [this message]
2017-01-13 10:00 ` [PATCH RESEND 1/2] memory: aemif: allow passing device lookup table as platform data Bartosz Golaszewski
2017-01-13 16:36 ` Santosh Shilimkar
2017-01-13 10:00 ` [PATCH RESEND 2/2] ARM: da850: add the nand dev_id to the clock lookup table Bartosz Golaszewski
2017-01-20 13:46 ` Sekhar Nori
2017-01-23 15:17 ` Sekhar Nori
2017-01-23 15:32 ` Bartosz Golaszewski
2017-01-23 15:59 ` Sekhar Nori
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=1484301626-30345-1-git-send-email-bgolaszewski@baylibre.com \
--to=bgolaszewski@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nsekhar@ti.com \
--cc=santosh.shilimkar@oracle.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
Powered by JetHome