[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b0d1eee4a8684153baac4f2aea099fa4@CY1PR0301MB0748.namprd03.prod.outlook.com>
Date: Sat, 20 Sep 2014 15:36:59 +0000
From: Stuart Yoder <stuart.yoder@...escale.com>
To: Alexander Graf <agraf@...e.de>,
Scott Wood <scottwood@...escale.com>
CC: Kim Phillips <Kim.Phillips@...escale.com>,
Jose Rivera <German.Rivera@...escale.com>,
"<gregkh@...uxfoundation.org>" <gregkh@...uxfoundation.org>,
"<arnd@...db.de>" <arnd@...db.de>,
"<linux-kernel@...r.kernel.org>" <linux-kernel@...r.kernel.org>,
"<linuxppc-release@...ux.freescale.net>"
<linuxppc-release@...ux.freescale.net>
Subject: RE: [PATCH 1/4] drivers/bus: Added Freescale Management Complex APIs
> Speaking of which, how does Linux find this new bus? I couldn't find
> anything that describes the device tree bindings, but maybe I just
> missed them.
There is a separate thread on the ARM mailing list with the device tree
and binding (device tree will be in arch/arm64):
http://www.spinics.net/lists/arm-kernel/msg354635.html
Stuart
Powered by blists - more mailing lists