From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752183AbbHMJnW (ORCPT ); Thu, 13 Aug 2015 05:43:22 -0400 Received: from mail-la0-f52.google.com ([209.85.215.52]:34675 "EHLO mail-la0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751962AbbHMJnP (ORCPT ); Thu, 13 Aug 2015 05:43:15 -0400 Date: Thu, 13 Aug 2015 11:42:53 +0200 From: Olof Johansson To: Hans Ulli Kroll Cc: arm@kernel.org, linux-kernel@vger.kernel.org, Arnd Bergmann , Roman Yeryomin , linus.walleij@linaro.org Subject: Re: ARM: gemini: clocksource update for 4.3 v2 Message-ID: <20150813094253.GI30160@localhost> References: <1438955763-17260-1-git-send-email-ulli.kroll@googlemail.com> <1439323745-8542-1-git-send-email-ulli.kroll@googlemail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1439323745-8542-1-git-send-email-ulli.kroll@googlemail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 11, 2015 at 10:09:02PM +0200, Hans Ulli Kroll wrote: > Hi, > > these is version 2 of the clocksource updates for 4.3 > > These patches are rebased on your arm-soc/for-next tree. > latest commit e4c4ce53a925146167a58cfd2e862952cdc316e1 > > arm-soc: document merges > > They is also a patch from Viresh Kumar in mach-gemini > ARM/gemini/time: Migrate to new 'set-state' interface > > The other patches affecting clocksource are going through the > clocksource tree. Thanks, applied now! > For the clocksource in general : > I'm planning to move to DT. mach-moxart locks promising. > Same CPU FA526 as mach-gemini. > But they are two devices they can't moved easily to DT. > - MISC global reg for differnt device settings > - ethernet, up to 2 irq's, shared address space (bitfield) > > Don't ask me why the engineers have done this ... > > So I need DT in conjunction with (one) board file(s). > Is this possible ?? It might be a bit messy to deal with a few things when you split between board files and DT. In general you might be interested in looking at the syscon bindings which tend to be used when there are "misc" registers on a SoC that multiple drivers need to share. See Documentation/devicetree/bindings/mfd/syscon.txt and other drivers and platforms for examples of that. -Olof