From: Imran Khan <kimran@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: andy.gross@linaro.org, David Brown <david.brown@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"open list:ARM/QUALCOMM SUPPORT" <linux-arm-msm@vger.kernel.org>,
"open list:ARM/QUALCOMM SUPPORT" <linux-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] soc: qcom: Add SoC info driver
Date: Wed, 26 Oct 2016 19:42:08 +0530 [thread overview]
Message-ID: <2ae082c4-27c1-fbdd-cb7a-986716e15d18@codeaurora.org> (raw)
In-Reply-To: <3809309.oOnjdjqnN9@wuerfel>
On 10/26/2016 7:35 PM, Arnd Bergmann wrote:
>> > As we are talking about generic soc_device_attribute fields, I was hoping that
>> > having a vendor field would be helpful as along with family it would provide
>> > a more thorough information. Also as more than one foundries may be used for
>> > a soc, can we have a field say foundry_id to provide this information.
> My first feeling is that this 'vendor' information can should be
> derived from the family. It's also not clear what would happen
> to this when a company gets bought. E.g. the Oxnas product family
> was subsequently owned by Oxford, PLX, Avago and Broadcom, and the
> mxs family was Sigmatel, Freescale, now NXP and might soon be
> Qualcomm. What would you put in there in this case?
Okay, not having vendor field is fine for me. Could you also suggest
something about the foundry_id field.
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a\nmember of the Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2016-10-26 14:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 14:06 [PATCH] soc: qcom: Add SoC info driver Imran Khan
[not found] ` <1476972386-28655-1-git-send-email-kimran-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-10-20 14:09 ` Mark Rutland
2016-10-20 15:20 ` Andy Gross
2016-10-25 9:38 ` Imran Khan
2016-10-21 10:33 ` Arnd Bergmann
2016-10-25 9:53 ` Imran Khan
2016-10-25 20:49 ` Arnd Bergmann
2016-10-26 13:50 ` Imran Khan
2016-10-26 14:05 ` Arnd Bergmann
2016-10-26 14:12 ` Imran Khan [this message]
2016-10-26 14:46 ` Arnd Bergmann
2016-10-27 13:10 ` Imran Khan
2016-10-27 13:41 ` Arnd Bergmann
2016-11-02 7:49 ` Imran Khan
2016-11-02 13:11 ` Arnd Bergmann
2016-11-02 16:28 ` Bjorn Andersson
2016-11-09 14:44 ` Geert Uytterhoeven
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=2ae082c4-27c1-fbdd-cb7a-986716e15d18@codeaurora.org \
--to=kimran@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).