From: David Lechner <david@lechnology.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Sekhar Nori <nsekhar@ti.com>, Kevin Hilman <khilman@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH 1/9] clk: davinci: psc-dm365: use two lookup entries for the aemif clock
Date: Mon, 25 Jun 2018 11:06:46 -0500 [thread overview]
Message-ID: <c8d28664-e0fb-5a02-3c5b-b78684f87648@lechnology.com> (raw)
In-Reply-To: <CAMRc=MdTdoL9qsrMAxhCTaQM7HGrAPpTVjDuHQ81Q5O-QMNcYQ@mail.gmail.com>
On 06/25/2018 11:01 AM, Bartosz Golaszewski wrote:
> 2018-06-25 17:53 GMT+02:00 David Lechner <david@lechnology.com>:
>> On 06/25/2018 10:29 AM, Bartosz Golaszewski wrote:
>>>
>>> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>>
>>> We want to be able to get the clock both from the board file by its
>>> con_id and from the aemif driver by dev_id.
>>
>>
>> What about the other SoCs? Don't they need this change as well?
>>
>
> So I double checked and turns out I missed one other board that's
> affected by this series and calls clk_get() from machine code:
> dm644x-evm.
>
> I'll fix it in v2.
The ti-aemif platform driver also does clk_get(). Don't you need
lookups to make that work as well? For example, DA830 doesn't have
a clock lookup for aemif at all.
next prev parent reply other threads:[~2018-06-25 16:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 15:29 [PATCH 0/9] ARM: davinci: deduplicate aemif support Bartosz Golaszewski
2018-06-25 15:29 ` [PATCH 1/9] clk: davinci: psc-dm365: use two lookup entries for the aemif clock Bartosz Golaszewski
2018-06-25 15:53 ` David Lechner
2018-06-25 16:01 ` Bartosz Golaszewski
2018-06-25 16:06 ` David Lechner [this message]
2018-06-25 16:09 ` Bartosz Golaszewski
2018-06-26 8:27 ` Bartosz Golaszewski
2018-06-25 15:29 ` [PATCH 2/9] ARM: davinci: omapl138-hawk: add aemif & nand support Bartosz Golaszewski
2018-06-25 16:08 ` David Lechner
2018-06-25 15:29 ` [PATCH 3/9] ARM: davinci: da850-evm: use aemif platform driver in legacy mode Bartosz Golaszewski
2018-06-25 16:00 ` David Lechner
2018-06-25 16:04 ` David Lechner
2018-06-25 15:29 ` [PATCH 4/9] ARM: davinci: dm365-evm: use the ti-aemif soc driver Bartosz Golaszewski
2018-06-25 15:29 ` [PATCH 5/9] ARM: davinci: dm644x-evm: use aemif platform driver Bartosz Golaszewski
2018-06-25 15:29 ` [PATCH 6/9] ARM: davinci: da830-evm: " Bartosz Golaszewski
2018-06-25 16:20 ` David Lechner
2018-06-25 16:23 ` Bartosz Golaszewski
2018-06-25 16:29 ` David Lechner
2018-06-25 15:29 ` [PATCH 7/9] ARM: davinci: dm646x-evm: " Bartosz Golaszewski
2018-06-25 15:29 ` [PATCH 8/9] ARM: davinci: mityomapl138: " Bartosz Golaszewski
2018-06-25 15:29 ` [PATCH 9/9] ARM: davinci: kill davinci_aemif_setup() Bartosz Golaszewski
2018-06-25 16:23 ` David Lechner
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=c8d28664-e0fb-5a02-3c5b-b78684f87648@lechnology.com \
--to=david@lechnology.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mturquette@baylibre.com \
--cc=nsekhar@ti.com \
--cc=sboyd@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