From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 155] a PLL is needed for the SoC
Date: Tue, 26 May 2020 10:24:38 +0000
Message-ID: <bug-155-13-LdjhBBlDeP@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-155-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=155
--- Comment #14 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Dimitri Galayko from comment #13)
> Dear all, I'm following the discussion by mail with Luke. There is a need to
> create a "open-source" and generic PLL with the following specifications:
>
> Technology: TSMC 180 nm
> Input: 24 MHz XTAL
> Output Frequency: ~300 MHz (~x12), with fractional intermediate frequencies
> x2, x3, x4, x5, x6.
as taps, this would be very helpful, so as to be able to do further
counter-dividers to create a wide frequency range for peripherals.
> A double of the frequency needs to be generated, in
> order to have a 300 MHz well-balanced 1 and 0 phases.
interesting. 600mhz in 180nm.
> My first simulations in a 180 nm technology (not TSMC, but equivalent) shows
> that a 8 bits DCO may ensure a 600 MHz output frequency for all corners with
> a resolution able to provide a reasonably good jitter performance, with the
> power consumption of ~5mW.
this sounds perfectly reasonable.
> So, regarding the specifications, the most important point determining the
> overall architecture is :
> -- Jitter
> -- power consumption.
>
> Is there any idea about what is expected for these two specifications ?
5mW is perfectly acceptable. we do not have enough experience to say if jitter
is an issue, and for this first chip, being a noncritical test chip, if it is
unstable due to jitter we simply run tests at a slower speed, incrementally,
until it is.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-155-13@https.bugs.libre-soc.org/>
2020-05-26 9:00 ` bugzilla-daemon
2020-05-26 10:24 ` bugzilla-daemon [this message]
2020-05-26 20:12 ` bugzilla-daemon
2020-05-26 21:30 ` bugzilla-daemon
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=bug-155-13-LdjhBBlDeP@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git