From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/4] sh: Add sh7264 device
Date: Wed, 11 Apr 2012 21:54:45 +0000 [thread overview]
Message-ID: <20120411215442.GA7368@linux-sh.org> (raw)
In-Reply-To: <1334062853-23045-3-git-send-email-phil.edworthy@renesas.com>
On Wed, Apr 11, 2012 at 05:28:43PM +0100, phil.edworthy@renesas.com wrote:
> Ok, I have reworked the patches, but without 16-bit div4 clock regs, the
> board runs really slowly (probably writing to another reg at the same
> time).
Note that the loops_per_jiffy value is calibrated from the clock
framework so if you have the CPU clock way off this could also lead to
odd behaviour.
> To test my patches, I just hacked the div4 functions to use ioread16/
> iowrite16.
>
> I used your patch for 8bit module stop, so should I wait for your 16bit
> div4 clock regs patch or send my patches now?
>
Yes, that's probably the easiest.
next prev parent reply other threads:[~2012-04-11 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 13:00 [PATCH 2/4] sh: Add sh7264 device Phil Edworthy
2012-04-11 3:43 ` Paul Mundt
2012-04-11 7:44 ` phil.edworthy
2012-04-11 16:28 ` phil.edworthy
2012-04-11 21:54 ` Paul Mundt [this message]
2012-05-04 15:00 ` Phil Edworthy
2012-05-09 2:56 ` Paul Mundt
2012-05-09 6:05 ` phil.edworthy
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=20120411215442.GA7368@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.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;
as well as URLs for NNTP newsgroup(s).