Re: Access to NVDIMM JEDEC registers

2017-09-25 Thread Dan Williams
On Mon, Sep 25, 2017 at 9:16 AM, Brian Stark wrote: > Really I am just trying to understand what is currently implemented. If > you take away the direct access functions I mention, the rest of the > functions should provide most functionality needed but implementing

Re: Access to NVDIMM JEDEC registers

2017-09-25 Thread Brian Stark
t; To: Dan Williams <dan.j.willi...@intel.com> > > > Cc: Raghu Kulkarni <raghu.kulka...@sanmina.com>; > linux-nvdimm@lists.01.org > > > Subject: Re: Access to NVDIMM JEDEC registers > > > > > > Thanks for the response Dan, > > > > > > As a

Re: Access to NVDIMM JEDEC registers

2017-09-25 Thread Brian Stark
..@sanmina.com>; > linux-nvdimm@lists.01.org > > Subject: Re: Access to NVDIMM JEDEC registers > > > > Thanks for the response Dan, > > > > As a developer of NVDIMMs we interface to our controller using the SMBUS > > interface, which is part of the JEDE

Re: Access to NVDIMM JEDEC registers

2017-09-21 Thread Dan Williams
20, 2017 11:11 AM > > To: Dan Williams <dan.j.willi...@intel.com> > > Cc: Raghu Kulkarni <raghu.kulka...@sanmina.com>; linux-nvdimm@lists.01.org > > Subject: Re: Access to NVDIMM JEDEC registers > > > > Thanks for the response Dan, > > > > As a dev

RE: Access to NVDIMM JEDEC registers

2017-09-20 Thread Elliott, Robert (Persistent Memory)
gt;; linux-nvdimm@lists.01.org > Subject: Re: Access to NVDIMM JEDEC registers > > Thanks for the response Dan, > > As a developer of NVDIMMs we interface to our controller using the SMBUS > interface, which is part of the JEDEC standard. In the past we have always > tested and acce

Re: Access to NVDIMM JEDEC registers

2017-09-20 Thread Dan Williams
On Wed, Sep 20, 2017 at 1:53 PM, Christoph Hellwig wrote: > On Wed, Sep 20, 2017 at 09:52:32AM -0700, Dan Williams wrote: >> What that means is that the utility to read the JEDEC registers would need >> to: >> >> 1/ Determine if the DIMM is standard JEDEC defined DIMM (the

Re: Access to NVDIMM JEDEC registers

2017-09-20 Thread Christoph Hellwig
On Wed, Sep 20, 2017 at 09:52:32AM -0700, Dan Williams wrote: > What that means is that the utility to read the JEDEC registers would need to: > > 1/ Determine if the DIMM is standard JEDEC defined DIMM (the ACPI NFIT > should indicate this) > > 2/ Determine if the BIOS provides a DSM command

Re: Access to NVDIMM JEDEC registers

2017-09-20 Thread Dan Williams
On Wed, Sep 20, 2017 at 9:10 AM, Brian Stark wrote: > Thanks for the response Dan, > > As a developer of NVDIMMs we interface to our controller using the SMBUS > interface, which is part of the JEDEC standard. In the past we have always > tested and accessed out NVDIMMs

Re: Access to NVDIMM JEDEC registers

2017-09-20 Thread Brian Stark
Thanks for the response Dan, As a developer of NVDIMMs we interface to our controller using the SMBUS interface, which is part of the JEDEC standard. In the past we have always tested and accessed out NVDIMMs by directly manipulating the SMBUS controller defined in the chipsets. As you may be

Re: Access to NVDIMM JEDEC registers

2017-09-19 Thread Dan Williams
On Tue, Sep 19, 2017 at 3:29 PM, Brian Stark wrote: > Where can I find documentation on accessing NVDIMM JEDEC registers, for > example if I want to read page 0 offset 0x80 (defined to be CSAVE_INFO in > the JEDEC specification. How do I do this through Linux given that

Access to NVDIMM JEDEC registers

2017-09-19 Thread Brian Stark
Where can I find documentation on accessing NVDIMM JEDEC registers, for example if I want to read page 0 offset 0x80 (defined to be CSAVE_INFO in the JEDEC specification. How do I do this through Linux given that the BIOS has locked the chipset? Brian -- CONFIDENTIALITY This e-mail message and