public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/2] soc: samsung: add exynos chipid driver support
Date: Fri, 12 Dec 2014 12:31:30 +0100	[thread overview]
Message-ID: <1521226.qVx3V7aJT6@wuerfel> (raw)
In-Reply-To: <548A9D27.1000504@samsung.com>

On Friday 12 December 2014 13:15:43 Pankaj Dubey wrote:
> >> +
> >> +static void __iomem *exynos_chipid_base;
> >> +
> >> +struct exynos_chipid_info exynos_soc_info;
> >> +EXPORT_SYMBOL(exynos_soc_info);
> >
> > The soc_device already has similar data.Why is this needed? Is it
> > temporary for compatibility?
> 
> struct soc_device_attribute can hold these two (product_id, and 
> revision) but they are defined as char * in soc_device_atttribute, and I 
> feel it's more specific for exposing via sysfs.
> Also existing code in mach-exynos compares them via product_id/revision 
> macros, so I can say to keep compatibility.

We had a similar discussion about the Marvell SoCs a while ago, and at
the time we concluded that it would be best to create a platform-
independent API to match the strings in soc_device_attribute against
a list of strings in the driver, either by matching the start of the
string, or using the glob_match() function. Would that work for you?

	Arnd

  reply	other threads:[~2014-12-12 11:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  8:07 [PATCH v5 0/2] Introducing Exynos ChipId driver Pankaj Dubey
2014-12-11  8:07 ` [PATCH v5 1/2] soc: samsung: add exynos chipid driver support Pankaj Dubey
2014-12-11 17:30   ` Rob Herring
2014-12-12  7:45     ` Pankaj Dubey
2014-12-12 11:31       ` Arnd Bergmann [this message]
2015-01-12  9:29         ` Pankaj Dubey
2014-12-13 17:58       ` Rob Herring
2014-12-11  8:07 ` [PATCH v5 2/2] ARM: EXYNOS: refactoring of mach-exynos to enable chipid driver Pankaj Dubey
2016-05-16 13:22 ` [PATCH v5 0/2] Introducing Exynos ChipId driver Krzysztof Kozlowski
2016-05-19 13:32   ` Pankaj Dubey

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=1521226.qVx3V7aJT6@wuerfel \
    --to=arnd@arndb.de \
    --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