linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: mvebu: Add support to get the ID and the revision of a SoC
Date: Mon, 06 Jan 2014 01:05:01 +0100	[thread overview]
Message-ID: <52C9F32D.5080007@gmail.com> (raw)
In-Reply-To: <20140105234009.GC11280@obsidianresearch.com>

On 01/06/2014 12:40 AM, Jason Gunthorpe wrote:
> On Mon, Jan 06, 2014 at 12:12:16AM +0100, Sebastian Hesselbarth wrote:
>> On 01/06/2014 12:07 AM, Jason Gunthorpe wrote:
>>> On Sun, Jan 05, 2014 at 06:37:21PM +0100, Sebastian Hesselbarth wrote:
>>>
>>>> If you mean clock-gated with "powered down", the code is safe. It
>>>> enables the clock gate prior reading from the controller. Or is there
>>>> another way to power down the controller, so you cannot read from the
>>>> controller registers?
>>>
>>> There is a clock gate and a power down on kirkwood at least, Linux has
>>> no code for controlling the powerdown
>>
>> Does that power down really disable reading from PCIe controller
>> registers or is it just PHY power down?
>
> I haven't experimented with it, but every block that has a clock gate
> has a power down, so I doubt it is just a phy power down.

Ok, I see. But it isn't documented in the public FS, is it? If there is
an extra powerdown register for each ip block, I guess it will also
break reading from its registers.

>>> In any event, I think processing a disabled DT node is not great..
>>
>> Yeah, but you see another way to get the PCIe controller registers
>> instead? Or any other common id register to read? IMHO PCIe ids are
>> the best we can find here and Gregory found the first IP that really
>> depends on the SoC revision..
>
> I don't know of another option off hand, unless something is encoded
> in the CPU ID register set.
>
> Encoding the IP block version in the I2C DT compatible string is the
> next best choice, but it obviously isn't automatic..

True. But I still wonder how many users will find the correct dtb
without knowing the SoC revision. Having it probed would be best for
users, but I see the difficulties.

We should really work harder on proper u-boot/barebox for all those
Orion SoCs to have at least the option to update it with DT support.

Sebastian

  reply	other threads:[~2014-01-06  0:05 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03  9:59 [PATCH v2 0/2] Fix i2c bus hang on A0 version of the Armada XP SoCs Gregory CLEMENT
2014-01-03  9:59 ` [PATCH v2 1/2] ARM: mvebu: Add support to get the ID and the revision of a SoC Gregory CLEMENT
2014-01-03 14:47   ` Andrew Lunn
2014-01-03 14:51     ` Gregory CLEMENT
2014-01-03 15:13       ` Gregory CLEMENT
2014-01-03 16:41         ` Andrew Lunn
2014-01-03 19:30           ` Gregory CLEMENT
2014-01-03 18:48   ` Thomas Petazzoni
2014-01-03 19:25     ` Gregory CLEMENT
2014-01-03 18:59   ` Jason Gunthorpe
2014-01-03 19:35     ` Gregory CLEMENT
2014-01-05 14:25   ` Arnd Bergmann
2014-01-05 15:40     ` Andrew Lunn
2014-01-05 17:27       ` Jason Gunthorpe
2014-01-05 17:37         ` Sebastian Hesselbarth
2014-01-05 23:07           ` Jason Gunthorpe
2014-01-05 23:12             ` Sebastian Hesselbarth
2014-01-05 23:40               ` Jason Gunthorpe
2014-01-06  0:05                 ` Sebastian Hesselbarth [this message]
2014-01-06  0:17                   ` Andrew Lunn
2014-01-06  9:55                     ` Gregory CLEMENT
2014-01-06 10:10                       ` Gregory CLEMENT
2014-01-05 19:17       ` Arnd Bergmann
2014-01-05 23:51         ` Andrew Lunn
2014-01-06 15:37           ` Arnd Bergmann
2014-01-06 16:24             ` Andrew Lunn
2014-01-07 14:41               ` Arnd Bergmann
2014-01-06 10:28     ` Gregory CLEMENT
2014-01-03  9:59 ` [PATCH v2 2/2] i2c: mv64xxx: Fix bus hang on A0 version of the Armada XP SoCs Gregory CLEMENT
2014-01-03 12:20   ` Gregory CLEMENT
2014-01-03 18:49   ` Thomas Petazzoni
2014-01-03 19:31     ` Gregory CLEMENT
2014-01-05 14:33   ` Arnd Bergmann
2014-01-06  9:09     ` Gregory CLEMENT
2014-01-07  9:03       ` Arnd Bergmann
2014-01-07 13:17         ` Gregory CLEMENT
2014-01-07 20:50           ` Arnd Bergmann

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=52C9F32D.5080007@gmail.com \
    --to=sebastian.hesselbarth@gmail.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).