On Fri, May 30, 2014 at 06:17:49PM +0200, Stephen Warren wrote:
> On 05/30/2014 02:23 AM, Peter De Schrijver wrote:
> > On Thu, May 29, 2014 at 09:01:27PM +0200, Stephen Warren wrote:
> >> On 05/28/2014 06:54 AM, Peter De Schrijver wrote:
> >>> This driver allows userspace to read the raw efuse
On Fri, May 30, 2014 at 06:17:49PM +0200, Stephen Warren wrote:
On 05/30/2014 02:23 AM, Peter De Schrijver wrote:
On Thu, May 29, 2014 at 09:01:27PM +0200, Stephen Warren wrote:
On 05/28/2014 06:54 AM, Peter De Schrijver wrote:
This driver allows userspace to read the raw efuse data. Its
On 05/30/2014 02:23 AM, Peter De Schrijver wrote:
> On Thu, May 29, 2014 at 09:01:27PM +0200, Stephen Warren wrote:
>> On 05/28/2014 06:54 AM, Peter De Schrijver wrote:
>>> This driver allows userspace to read the raw efuse data. Its userspace
>>> interface is modelled after the sunxi_sid driver
On Thu, May 29, 2014 at 09:01:27PM +0200, Stephen Warren wrote:
> On 05/28/2014 06:54 AM, Peter De Schrijver wrote:
> > This driver allows userspace to read the raw efuse data. Its userspace
> > interface is modelled after the sunxi_sid driver which provides similar
> > functionality for some
On Thu, May 29, 2014 at 09:01:27PM +0200, Stephen Warren wrote:
On 05/28/2014 06:54 AM, Peter De Schrijver wrote:
This driver allows userspace to read the raw efuse data. Its userspace
interface is modelled after the sunxi_sid driver which provides similar
functionality for some Allwinner
On 05/30/2014 02:23 AM, Peter De Schrijver wrote:
On Thu, May 29, 2014 at 09:01:27PM +0200, Stephen Warren wrote:
On 05/28/2014 06:54 AM, Peter De Schrijver wrote:
This driver allows userspace to read the raw efuse data. Its userspace
interface is modelled after the sunxi_sid driver which
On 05/28/2014 07:16 AM, Andrew Morton wrote:
> On Wed, 28 May 2014 15:54:32 +0300 Peter De Schrijver
> wrote:
>
>> This driver allows userspace to read the raw efuse data.
>
> The patchset uses an inexplicable mixture of "fuse" and "efuse".
> Given that the kernel already has a "fuse", it
On 05/28/2014 06:54 AM, Peter De Schrijver wrote:
> This driver allows userspace to read the raw efuse data. Its userspace
> interface is modelled after the sunxi_sid driver which provides similar
> functionality for some Allwinner SoCs. It has been tested on
> Tegra20 (ventana), Tegra30
On 05/28/2014 06:54 AM, Peter De Schrijver wrote:
This driver allows userspace to read the raw efuse data. Its userspace
interface is modelled after the sunxi_sid driver which provides similar
functionality for some Allwinner SoCs. It has been tested on
Tegra20 (ventana), Tegra30
On 05/28/2014 07:16 AM, Andrew Morton wrote:
On Wed, 28 May 2014 15:54:32 +0300 Peter De Schrijver
pdeschrij...@nvidia.com wrote:
This driver allows userspace to read the raw efuse data.
The patchset uses an inexplicable mixture of fuse and efuse.
Given that the kernel already has a
On Wed, 28 May 2014 15:54:32 +0300 Peter De Schrijver
wrote:
> This driver allows userspace to read the raw efuse data.
The patchset uses an inexplicable mixture of "fuse" and "efuse".
Given that the kernel already has a "fuse", it would be nice if
this code could use "efuse" everywhere.
--
To
This driver allows userspace to read the raw efuse data. Its userspace
interface is modelled after the sunxi_sid driver which provides similar
functionality for some Allwinner SoCs. It has been tested on
Tegra20 (ventana), Tegra30 (beaverboard), Tegra114 (dalmore) and
Tegra124 (jetson TK1).
This driver allows userspace to read the raw efuse data. Its userspace
interface is modelled after the sunxi_sid driver which provides similar
functionality for some Allwinner SoCs. It has been tested on
Tegra20 (ventana), Tegra30 (beaverboard), Tegra114 (dalmore) and
Tegra124 (jetson TK1).
On Wed, 28 May 2014 15:54:32 +0300 Peter De Schrijver pdeschrij...@nvidia.com
wrote:
This driver allows userspace to read the raw efuse data.
The patchset uses an inexplicable mixture of fuse and efuse.
Given that the kernel already has a fuse, it would be nice if
this code could use efuse
14 matches
Mail list logo