From: Linus Walleij <linus.walleij@linaro.org>
To: Joel Stanley <joel@jms.id.au>
Cc: "Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Jonas Jensen" <jonas.jensen@gmail.com>,
"Janos Laube" <janos.dev@gmail.com>,
"Paulius Zaleckas" <paulius.zaleckas@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Hans Ulli Kroll" <ulli.kroll@googlemail.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Ryan Chen" <ryan_chen@aspeedtech.com>,
"Cédric Le Goater" <clg@kaod.org>
Subject: Re: [PATCH 7/8] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010
Date: Thu, 18 May 2017 14:43:27 +0200 [thread overview]
Message-ID: <CACRpkdaWoGYh4D3D0+3mzVDTy78O2idyDmg9+U5zJc_mfn+WLQ@mail.gmail.com> (raw)
In-Reply-To: <CACPK8XdRe8Khnj3YFoQYKpKHM-5PHTqkP8Nt+jZ=eo-FThN-aw@mail.gmail.com>
On Thu, May 18, 2017 at 9:22 AM, Joel Stanley <joel@jms.id.au> wrote:
> On Wed, May 17, 2017 at 10:05 PM, Linus Walleij
> <linus.walleij@linaro.org> wrote:
>> This merges the Moxa Art timer driver into the Faraday FTTMR010
>> driver and replaces all Kconfig symbols to use the Faraday
>> driver instead. We are now so similar that the drivers can
>> be merged by just adding a few lines to the Faraday timer.
>
> Nice work!
>
> I gave this a spin on hardware and it didn't work :(
How typical.
> Thanks for the rework! Unfortunately the Aspeed IP does not have bits
> to control the direction of counting, and the timers only count down.
> Bits 3, 7 and 11 are marked reserved in the data sheet. Can you rework
> the patch to count down?
How unintuitive.
I guess I will just make it handle the Aspeed separately, so we
count up on Gemini and Moxa and down on Aspeed if that is all
it can do.
> As an aside, we have a pretty decent model for the Aspeed SoCs in
> Qemu. If you want to use it to smoketest your rework:
>
> $ qemu-system-arm -m 512 -M ast2500-evb -nodefaults -nographic
> -serial stdio -kernel arch/arm/boot/zImage -dtb
> arch/arm/boot/dts/aspeed-ast2500-evb.dtb
>
> I tested with Ubuntu's qemu v2.8. It looks like we have a bug when the
> kernel tries to use the clock the way your driver works, so we will
> look at that. It does function properly for the current upstream code.
Oh that's sweet! I'll test it if I can get it working like this.
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-05-18 12:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 14:05 [PATCH 0/8] clocksource: Generalize Faraday timer Linus Walleij
2017-05-17 14:05 ` [PATCH 1/8] clocksource/drivers/fttmr010: Fix the clock handling Linus Walleij
2017-05-17 14:05 ` [PATCH 2/8] clocksource/drivers/fttmr010: Merge FTTMR010 DT bindings Linus Walleij
2017-05-23 0:51 ` Rob Herring
2017-05-17 14:05 ` [PATCH 3/8] clocksource/drivers/fttmr010: Drop Gemini specifics Linus Walleij
2017-05-17 14:05 ` [PATCH 4/8] clocksource/drivers/fttmr010: Use state container Linus Walleij
2017-05-17 14:05 ` [PATCH 5/8] clocksource/drivers/fttmr010: Switch to use bitops Linus Walleij
2017-05-17 14:05 ` [PATCH 6/8] clocksource/drivers/fttmr010: Switch to use TIMER2 src Linus Walleij
2017-05-17 14:05 ` [PATCH 7/8] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010 Linus Walleij
2017-05-18 7:22 ` Joel Stanley
2017-05-18 12:43 ` Linus Walleij [this message]
2017-05-18 13:12 ` Cédric Le Goater
2017-05-18 20:20 ` Linus Walleij
2017-05-18 21:09 ` Cédric Le Goater
2017-05-19 7:59 ` Cédric Le Goater
2017-05-17 14:05 ` [PATCH 8/8] ARM: dts: augment Moxa and Aspeed DTS for FTTMR010 Linus Walleij
2017-05-18 10:32 ` [PATCH 0/8] clocksource: Generalize Faraday timer Jonas Jensen
2017-05-18 12:11 ` Linus Walleij
2017-05-18 13:31 ` Daniel Lezcano
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=CACRpkdaWoGYh4D3D0+3mzVDTy78O2idyDmg9+U5zJc_mfn+WLQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=benh@kernel.crashing.org \
--cc=clg@kaod.org \
--cc=daniel.lezcano@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=janos.dev@gmail.com \
--cc=joel@jms.id.au \
--cc=jonas.jensen@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulius.zaleckas@gmail.com \
--cc=ryan_chen@aspeedtech.com \
--cc=tglx@linutronix.de \
--cc=ulli.kroll@googlemail.com \
/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).