On Thu, Mar 29, 2018 at 4:06 AM, Rob Herring wrote:
> On Tue, Mar 27, 2018 at 9:53 AM, Oliver wrote:
>> On Tue, Mar 27, 2018 at 9:24 AM, Rob Herring wrote:
>>> On Fri, Mar 23, 2018 at 07:12:09PM +1100, Oliver O'Halloran wrote:
Add
On Wed, Mar 28, 2018 at 10:06 AM, Rob Herring wrote:
[..]
> >> Are DIMMs always going to be the only form factor for NV memory?
> >>
> >> And if you have multiple DIMMs, does each DT node correspond to a DIMM?
> >
> > A nvdimm-region might correspond to a single NVDIMM, a set of
On Tue, Mar 27, 2018 at 9:53 AM, Oliver wrote:
> On Tue, Mar 27, 2018 at 9:24 AM, Rob Herring wrote:
>> On Fri, Mar 23, 2018 at 07:12:09PM +1100, Oliver O'Halloran wrote:
>>> Add device-tree binding documentation for the nvdimm region driver.
>>>
>>> Cc:
On Tue, Mar 27, 2018 at 9:24 AM, Rob Herring wrote:
> On Fri, Mar 23, 2018 at 07:12:09PM +1100, Oliver O'Halloran wrote:
>> Add device-tree binding documentation for the nvdimm region driver.
>>
>> Cc: devicet...@vger.kernel.org
>> Signed-off-by: Oliver O'Halloran
On Fri, Mar 23, 2018 at 07:12:09PM +1100, Oliver O'Halloran wrote:
> Add device-tree binding documentation for the nvdimm region driver.
>
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Oliver O'Halloran
> ---
> .../devicetree/bindings/nvdimm/nvdimm-region.txt | 45
>
Add device-tree binding documentation for the nvdimm region driver.
Cc: devicet...@vger.kernel.org
Signed-off-by: Oliver O'Halloran
---
.../devicetree/bindings/nvdimm/nvdimm-region.txt | 45 ++
1 file changed, 45 insertions(+)
create mode 100644