From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: mvebu: Add support to get the ID and the revision of a SoC
Date: Sun, 12 Jan 2014 18:45:21 +0100 [thread overview]
Message-ID: <52D2D4B1.1080709@free-electrons.com> (raw)
In-Reply-To: <1389499027.3720.42.camel@deadeye.wl.decadent.org.uk>
Hi Ben,
On 12/01/2014 04:57, Ben Hutchings wrote:
> On Thu, 2014-01-02 at 17:01 +0100, Gregory CLEMENT wrote:
>> All the mvebu SoCs have information related to their variant and
>> revision that can be read from the PCI control register.
>>
>> This patch adds support for Armada XP and Armada 370. This reading of
>> the revision and the ID are done before the PCI initialization to
>> avoid any conflicts. Once these data are retrieved, the resources are
>> freed to let the PCI subsystem use it.
> [...]
>> --- /dev/null
>> +++ b/include/linux/mvebu-soc-id.h
>> @@ -0,0 +1,32 @@
>> +/*
>> + * Marvell EBU SoC ID and revision definitions.
>> + *
>> + * Copyright (C) 2014 Marvell Semiconductor
>> + *
>> + * This file is licensed under the terms of the GNU General Public
>> + * License version 2. This program is licensed "as is" without any
>> + * warranty of any kind, whether express or implied.
>> + */
>> +
>> +#ifndef __LINUX_MVEBU_SOC_ID_H
>> +#define __LINUX_MVEBU_SOC_ID_H
>> +
>> +/* Armada XP ID */
>> +#define MV78230_DEV_ID 0x7823
>> +#define MV78260_DEV_ID 0x7826
>> +#define MV78460_DEV_ID 0x7846
>> +
>> +/* Armada XP Revision */
>> +#define MV78XX0_A0_REV 0x1
>> +#define MV78XX0_B0_REV 0x2
>> +
>> +#ifdef CONFIG_ARCH_MVEBU
>> +int mvebu_get_soc_id(u32 *dev, u32 *rev);
>> +#else
>> +int mvebu_get_soc_id(u32 *dev, u32 *rev)
>
> This definition needs to be static inline, assuming anything will
> actually include this header when !defined(CONFIG_ARCH_MVEBU).
>
Your review is appreciate, however there was 4 more version sent
since this one. And this issue was already pointed and then fixed
in the 3rd version.
Thanks,
Gregory
> Ben.
>
>> +{
>> + return -1;
>> +}
>> +#endif
>> +
>> +#endif /* __LINUX_MVEBU_SOC_ID_H */
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2014-01-12 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 16:01 [PATCH 0/2] Fix i2c bus hang on A0 version of the Armada XP SoCs Gregory CLEMENT
2014-01-02 16:01 ` [PATCH 1/2] ARM: mvebu: Add support to get the ID and the revision of a SoC Gregory CLEMENT
2014-01-12 3:57 ` Ben Hutchings
2014-01-12 17:45 ` Gregory CLEMENT [this message]
2014-01-12 18:03 ` Ben Hutchings
2014-01-02 16:01 ` [PATCH 2/2] i2c: mv64xxx: Fix bus hang on A0 version of the Armada XP SoCs Gregory CLEMENT
2014-01-02 18:28 ` Jason Cooper
2014-01-02 18:41 ` Wolfram Sang
2014-01-03 8:48 ` Gregory CLEMENT
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=52D2D4B1.1080709@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).