From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] Framework for exporting System-on-Chip information via sysfs
Date: Thu, 21 Apr 2011 12:56:07 +0100 [thread overview]
Message-ID: <4DB01B57.9090909@linaro.org> (raw)
In-Reply-To: <201104211303.04043.arnd@arndb.de>
Hi Arnd,
</snip>
>>> (I believe this would be Copyright Linaro Ltd, not ST-Ericsson SA,
>>> but better ask internally in ST-Ericsson about what your rules are)
>>
>> We've had internal discussions about this. I believe this is the correct
>> thing to do. The Copyright should stay with ST-Ericsson.
>
> Ok, in that case, I'd suggest you use your ST-Ericsson address for
> Signed-off-by and the author statement above.
I'm not an ST-Ericsson employee, thus do not have an associated address.
I work for Linaro, currently on assignment to ST-Ericsson.
</snip>
> I would prefer to standardise the attributes as much as possible. Ideally,
> all SOCs should export the same set of attributes, and in no case should
> there be multiple SOCs that have the same attribute name but with a
> slightly different interface (e.g. one writable, or one root-only readable),
> or the same contents in attributes of different names.
>
> The best way to ensure this is to give less flexiblity to the person
> implementing the individual SOC code. All attributes that are documented
> to be available across SOCs can simply be automatically created and
> filled with the data provided by the platform.
>
> Having interfaces specific to one SOC should be the absolute exception,
> so I'd try to make that as hard as possible.
Well your word overrides mine.
I'll completely rewrite the driver again. It may be some time before
it's complete (post-UDS/LDS), as I have a lot on 'till then. I would
like to see this to the end though, so leave it with me.
Kind regards,
Lee
next prev parent reply other threads:[~2011-04-21 11:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 14:49 [PATCH 0/3] Export valuable System-on-Chip information to user-space via sysfs Lee Jones
2011-04-14 14:49 ` [PATCH 1/3] Framework for exporting System-on-Chip information " Lee Jones
2011-04-17 18:36 ` Arnd Bergmann
2011-04-21 9:44 ` Lee Jones
2011-04-21 11:03 ` Arnd Bergmann
2011-04-21 11:56 ` Lee Jones [this message]
2011-04-27 20:48 ` Russell King - ARM Linux
2011-04-28 6:46 ` Lee Jones
2011-04-14 14:49 ` [PATCH 2/3] mach-ux500: export " Lee Jones
2011-04-17 18:40 ` Arnd Bergmann
2011-04-14 14:49 ` [PATCH 3/3] Add documenation for new sysfs devices/soc functionallity Lee Jones
2011-04-17 18:41 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2011-07-12 13:08 [PATCH 1/3] Framework for exporting System-on-Chip information via sysfs Lee Jones
2011-07-12 14:13 ` Baruch Siach
2011-07-12 16:08 ` Greg KH
2011-07-13 7:16 ` Lee Jones
2011-07-13 7:53 ` Greg KH
2011-07-13 8:27 ` Lee Jones
2011-07-15 14:02 ` Arnd Bergmann
2011-04-11 18:01 Lee Jones
2011-04-12 12:46 ` Jamie Iles
2011-04-13 7:43 ` Lee Jones
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=4DB01B57.9090909@linaro.org \
--to=lee.jones@linaro.org \
--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).