mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Didier Lagard <didier.lagard@yahoo.fr>
To: linux-kernel@vger.kernel.org,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	Nicolas Ferre <nicolas.ferre@atmel.com>,
	Patrice VILCHEZ <patrice.vilchez@atmel.com>
Subject: Re : [PATCH] base: add sysfs socs info
Date: Wed, 15 Dec 2010 15:45:24 +0000 (GMT)	[thread overview]
Message-ID: <718694.20560.qm@web29214.mail.ird.yahoo.com> (raw)
In-Reply-To: <1292330417-13703-1-git-send-email-plagnioj@jcrosoft.com>

<plagnioj@jcrosoft.com> a écrit :
>
> this provide an easy way to register
> soc information
> 
> arch, family, model, id, revision
> 
> as this for at91sam9g20
> 
> $ cat /sys/devices/system/soc/soc0/arch
> current
> $ cat /sys/devices/system/soc/soc0/family
> at91
> $ cat /sys/devices/system/soc/soc0/id
> at91sam9g20
> $ cat /sys/devices/system/soc/soc0/model
> 0x00000000019905a0
> $ cat /sys/devices/system/soc/soc0/revision
> 1.1

Ouch, I've never seen so few explanations when it comes to add a new ABI...

Can you explain why this is needed at all ? How can it be usefull for an application for example ? Why make it a device ?

I mean there are plenty of SoC supports in the kernel (take a look to arch/arm) and none of them need that so far.

So at least we can expect some motivations to include this stuff in mailine.

Bye.


      

  parent reply	other threads:[~2010-12-15 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 12:40 Jean-Christophe PLAGNIOL-VILLARD
2010-12-14 16:11 ` Greg KH
2010-12-15  1:25   ` Jean-Christophe PLAGNIOL-VILLARD
2010-12-15  3:47     ` Greg KH
2010-12-15  7:39       ` Jean-Christophe PLAGNIOL-VILLARD
2010-12-15  8:17         ` Kay Sievers
2010-12-15 15:45 ` Didier Lagard [this message]
2010-12-15 20:17 ` Ryan Mallon
2010-12-15 20:24   ` Ryan Mallon

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=718694.20560.qm@web29214.mail.ird.yahoo.com \
    --to=didier.lagard@yahoo.fr \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=patrice.vilchez@atmel.com \
    --cc=plagnioj@jcrosoft.com \
    /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
Powered by JetHome