From: dmitry_eremin@mentor.com (Dmitry Eremin-Solenikov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: sa1100: switch to COMMON_CLK framework
Date: Fri, 1 Nov 2013 15:21:07 +0400 [thread overview]
Message-ID: <52738EA3.2010701@mentor.com> (raw)
In-Reply-To: <20131101105933.GL16735@n2100.arm.linux.org.uk>
On 01/11/13 14:59, Russell King - ARM Linux wrote:
> On Fri, Nov 01, 2013 at 02:52:11PM +0400, Dmitry Eremin-Solenikov wrote:
>> +#include <linux/kernel.h>
>> +#include <linux/clk-provider.h>
>> +#include <linux/clkdev.h>
>> +
>> +#include <mach/hardware.h>
>
> If the aim of this patch set is to move SA11x0 towards multiplatform,
> then this has just failed with the above include. It would be better
> not to try this without first solving the problem of the SoC register
> definitions.
OK, still learning "new ARM" ways. Is it ok to remap fixed addresses in
that file?
And second question: what would be better: to leave that code as is,
or to convert that to 3M6864/32k768 multiplexer (TUCR bit) +
enable/disable (GAFR/GPDR)? I ain't sure that all other TUCR modes
were ever used.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2013-11-01 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 10:52 [PATCH 1/4] ARM: sa1100: add irq handler to prepare MULTI_IRQ_HANDLER Dmitry Eremin-Solenikov
2013-11-01 10:52 ` [PATCH 2/4] ARM: sa1100: enable MULTI_IRQ_HANDLER for all boards Dmitry Eremin-Solenikov
2013-11-01 10:52 ` [PATCH 3/4] ARM: sa1100: drop entry-macro.S Dmitry Eremin-Solenikov
2013-11-01 10:52 ` [PATCH 4/4] ARM: sa1100: switch to COMMON_CLK framework Dmitry Eremin-Solenikov
2013-11-01 10:59 ` Russell King - ARM Linux
2013-11-01 11:21 ` Dmitry Eremin-Solenikov [this message]
2013-11-01 19:54 ` Dmitry Eremin-Solenikov
2013-11-12 13:44 ` [PATCH 1/4] ARM: sa1100: add irq handler to prepare MULTI_IRQ_HANDLER Linus Walleij
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=52738EA3.2010701@mentor.com \
--to=dmitry_eremin@mentor.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.