From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] zynq: Update CLK in bdinfo
Date: Thu, 13 Feb 2014 16:21:42 +0100 [thread overview]
Message-ID: <52FCE306.2040007@monstr.eu> (raw)
In-Reply-To: <20140213155235.6575205c@lilith>
On 02/13/2014 03:52 PM, Albert ARIBAUD wrote:
> Hi Michal,
>
> On Wed, 5 Feb 2014 08:18:35 +0100, Michal Simek
> <michal.simek@xilinx.com> wrote:
>
>> ARM has specific clk entries which should be also setup.
>>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>> ---
>>
>> Changes in v2:
>> - Freq is expected to be in MHz
>> - Use different DDR clock input
>>
>> arch/arm/cpu/armv7/zynq/clk.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>
> This is assigned to me, but it seems to be V2 of
> http://patchwork.ozlabs.org/patch/313199/ which was assigned to you.
> Should I apply this in ARM as a standalone patch?
no. I will be/is the part of my zynq pull request.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140213/4f336010/attachment.pgp>
prev parent reply other threads:[~2014-02-13 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 7:18 [U-Boot] [PATCH v2] zynq: Update CLK in bdinfo Michal Simek
2014-02-13 14:52 ` Albert ARIBAUD
2014-02-13 15:21 ` Michal Simek [this message]
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=52FCE306.2040007@monstr.eu \
--to=monstr@monstr.eu \
--cc=u-boot@lists.denx.de \
/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