From: Rohan Garg <rohan.garg@collabora.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3] rockchip: rk3399: derive ethaddr from cpuid
Date: Fri, 19 Jul 2019 16:56:45 +0200 [thread overview]
Message-ID: <1824154.9tn3IIiJ8K@solembum> (raw)
In-Reply-To: <05a83223-6f23-d363-f70b-4459ca6313a3@rock-chips.com>
Hey Kever
>
> This should be depends on CONFIG_MISC_INIT_R.
>
Ack.
>
> It's great to make these code as common code so that other SoCs
>
> can share it, is it possible to also make this function common?
>
> Not every SoC have efuse driver, so for those SoCs, we need a random
>
> serial No.
>
Do you think we can merge this as is for now and then move onto making it more
generic for other devices at a later date?
> > + const u32 cpuid_offset = 0x7;
> > + const u32 cpuid_length = 0x10;
> > + u8 cpuid[cpuid_length];
> > +
> > + rockchip_cpuid_from_efuse(cpuid_offset, cpuid_length, cpuid);
> > + rockchip_cpuid_set(cpuid, cpuid_length);
> > + rockchip_setup_macaddr();
>
> It will be better for these function calls with return value.
>
> There should be a blank line before 'return';
Ack.
Cheers
Rohan Garg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190719/8e070447/attachment.sig>
next prev parent reply other threads:[~2019-07-19 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 14:22 [U-Boot] [PATCH v2 1/3] rockchip: rk3399: derive ethaddr from cpuid Rohan Garg
2019-07-12 14:22 ` [U-Boot] [PATCH v2 2/3] rockchip: rk3399: Enable CONFIG_MISC_INIT_R for the Rock PI 4 Rohan Garg
2019-07-12 14:22 ` [U-Boot] [PATCH v2 3/3] board: puma: Use rockchip_* helpers to setup cpuid and macaddr Rohan Garg
2019-07-15 13:15 ` [U-Boot] [PATCH v2 1/3] rockchip: rk3399: derive ethaddr from cpuid Kever Yang
2019-07-19 14:56 ` Rohan Garg [this message]
2019-07-21 4:24 ` Kever Yang
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=1824154.9tn3IIiJ8K@solembum \
--to=rohan.garg@collabora.com \
--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