Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1590801

Re: [PATCH 1/1] drivers/misc: Add Intel System ID driver

Path csiph.com!news.redatomik.org!aioe.org!bofh.it!news.nic.it!robomod
From "Loh, Tien Hock" <tien.hock.loh@intel.com>
Newsgroups linux.kernel
Subject Re: [PATCH 1/1] drivers/misc: Add Intel System ID driver
Date Thu, 02 Mar 2017 03:20:01 +0100
Message-ID <tgovv-3Ky-7@gated-at.bofh.it> (permalink)
References <tbcEG-3vT-33@gated-at.bofh.it> <tbcEG-3vT-31@gated-at.bofh.it> <tbdU5-4d3-9@gated-at.bofh.it> <tdULf-5DE-7@gated-at.bofh.it> <tdWN4-731-23@gated-at.bofh.it> <tdWN4-731-21@gated-at.bofh.it> <tg71D-894-11@gated-at.bofh.it> <tg8qK-Tq-21@gated-at.bofh.it> <tg9Zw-1Pu-17@gated-at.bofh.it> <tgaVz-2rn-3@gated-at.bofh.it>
X-Original-To "arnd@arndb.de" <arnd@arndb.de>
X-Extloop1 1
X-Ironport-Av E=Sophos;i="5.35,228,1484035200"; d="scan'208";a="231287174"
Thread-Topic [PATCH 1/1] drivers/misc: Add Intel System ID driver
Thread-Index AQHSh3xEV1UiWY2US02NwdEQuVXhNaFpybMAgAArIICAC6nLgIAAI4+AgAACs4CACV+bAIAAG0wA///8/ACAAC3dgP//5QyA
Accept-Language en-US
Content-Language en-US
X-Originating-IP [10.226.241.207]
Content-Type text/plain; charset="utf-8"
Content-ID <170ADE58F7E7A541B7B518D6A1629454@intel.com>
Content-Transfer-Encoding base64
MIME-Version 1.0
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 42
Organization linux.* mail to news gateway
X-Original-Cc "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "Nguyen, Dinh" <dinh.nguyen@intel.com>, "thloh85@gmail.com" <thloh85@gmail.com>, "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>, "Gerlach, Matthew" <matthew.gerlach@intel.com>
X-Original-Date Thu, 2 Mar 2017 02:17:36 +0000
X-Original-Message-ID <1488362309.4010.23.camel@intel.com>
X-Original-References <1487156981-4550-1-git-send-email-user@thloh-VirtualBox> <20170215171732.GA4548@kroah.com> <CAK8P3a2gBiX+_e4nfG5t2SDgfY-=py00yMztMDHJtwHiRmSUfw@mail.gmail.com> <1487829507.2961.5.camel@intel.com> <CAK8P3a3n57ST2G8vXR8tzMrhLb7Fut6xUw3aNQEi-wi=hum8LQ@mail.gmail.com> <1487837723.2961.7.camel@intel.com> <1488353034.3544.3.camel@intel.com> <CAK8P3a1iH=+D7X0MR3DUDWDAytjs3X5xbWq3qUAcK07Us-5fcw@mail.gmail.com> <1488358248.4010.17.camel@intel.com> <CAK8P3a1Xiq2YrkxY9T-+-DsHzMSj5Dk7E-MQ4AF-7+zZBDrdpA@mail.gmail.com>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1590801

Show key headers only | View raw


On Rab, 2017-03-01 at 12:34 +0100, Arnd Bergmann wrote:
> On Wed, Mar 1, 2017 at 11:42 AM, Loh, Tien Hock <tien.hock.loh@intel.
> com> wrote:
> > 
> > On Rab, 2017-03-01 at 10:01 +0100, Arnd Bergmann wrote:
> > > 
> > > On Wed, Mar 1, 2017 at 8:23 AM, Loh, Tien Hock <tien.hock.loh@int
> > > el.c
> > > Another option would be to fold the timestamp into the revision
> > > attribute,
> > > but whether that is a reasonable place for it would in turn
> > > depend on
> > > what the timestamp signifies.
> > > 
> > > Can you explain what the timestamp is used for? Does it identify
> > > the
> > > time that the hardware revision was made, the time that a
> > > software
> > > was built which was loaded into it, or something else?
> > > What kind of user space application would need this information?
> > I just checked, and it seems like we can't put this into soc
> > subsystem.
> > In FPGA, we now can do partial reconfiguration, which
> > "reconfigures"
> > the hardware to have an updated sysid and timestamp value, and the
> > base
> > address of the Intel System ID may also be changed. This would
> > require
> > the driver to be a module that will be removed, probed again. The
> > soc
> > subsystem doesn't seem to be a suitable place to add this driver.
> Ah, I had not realized this is for fpga_manager.
> 
> Why not put the attributes into /sys/class/fpga_manager/*/ then
> along with the other attributes that exist there? That way, we have
> an interface that works for all users of drivers/fpga/
> 

Well, this is not only for fpga_manager, but often time used to ensure
that the correct hardware is programmed into the FPGA by checking the
sysid after fpga_manager reconfigures the hardware. Systems without
fpga_manager can still use sysid and timestamp to ensure the hardware
is as expected value.

What do you think of /sys/class/fpga_sysid/*/id and
/sys/class/fpga_sysid/*/timestamp?

> > 
> > A note on the timestamp, in the old days this is used to check that
> > the
> > BSP is using the correct FPGA hardware. I believe in Linux we
> > should do
> > the same in the driver, and if it not, the driver should print a
> > warning. The timestamp's print is not exactly needed. I'll add the
> > feature into the driver in the next patch.
> Ok.
> 
>      Arnd

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Re: [PATCH 1/1] drivers/misc: Add Intel System ID driver "Loh, Tien Hock" <tien.hock.loh@intel.com> - 2017-03-01 08:40 +0100
  Re: [PATCH 1/1] drivers/misc: Add Intel System ID driver Arnd Bergmann <arnd@arndb.de> - 2017-03-01 10:10 +0100
    Re: [PATCH 1/1] drivers/misc: Add Intel System ID driver "Loh, Tien Hock" <tien.hock.loh@intel.com> - 2017-03-01 11:50 +0100
      Re: [PATCH 1/1] drivers/misc: Add Intel System ID driver Arnd Bergmann <arnd@arndb.de> - 2017-03-01 12:50 +0100
        Re: [PATCH 1/1] drivers/misc: Add Intel System ID driver "Loh, Tien Hock" <tien.hock.loh@intel.com> - 2017-03-02 03:20 +0100

csiph-web