Messages in this thread | | | Date | Mon, 19 May 2014 23:33:00 +0530 | Subject | Re: [PATCHv5 2/4] mailbox: Introduce framework for mailbox | From | Jassi Brar <> |
| |
On 19 May 2014 18:38, Arnd Bergmann <arnd@arndb.de> wrote: > On Friday 16 May 2014 19:03:25 Jassi Brar wrote:
> >> Also, some platform might need to communicate with remote master >> during very early boot like for initializing system timers and clocks. >> The API isn't working then. > > Do you have an example for a platform like that? I'd expect that normally > we can have a boot loader that sets up the system timer to work good > enough for us to get into normal driver initialization. > My platform. We choose to keep bootloader to the minimum and make kernel not depend upon any goodies provided. Second, which I don't think can be helped by a bootloader, the remote master has gate & rate control of clocks to peripheral IPs. The clk-api driver simply maps Linux requests onto mailbox commands. So the mailbox is needed as early as CLK_OF_DECLARE (when kernel reads the rate of every registered clock). Any suggestions?
Thanks Jassi
| |