On 10/25/2014 11:00 AM, Andrew Lunn wrote:
On Sat, Oct 25, 2014 at 10:23:27AM -0700, Florian Fainelli wrote:
On 10/25/14 07:01, Andrew Lunn wrote:
Here is another naming option:
em1dsa0-virtual-0
I prefer this over isa.
However, i think there should be some sort of separator between the
On 10/25/2014 11:00 AM, Andrew Lunn wrote:
On Sat, Oct 25, 2014 at 10:23:27AM -0700, Florian Fainelli wrote:
On 10/25/14 07:01, Andrew Lunn wrote:
Here is another naming option:
em1dsa0-virtual-0
I prefer this over isa.
However, i think there should be some sort of separator between the
On 10/25/2014 07:01 AM, Andrew Lunn wrote:
Here is another naming option:
em1dsa0-virtual-0
I prefer this over isa.
However, i think there should be some sort of separator between the
network device name and dsa.
Fine with me. Any preference ? Note that '-' is not permitted.
Guenter
--
On Sat, Oct 25, 2014 at 10:23:27AM -0700, Florian Fainelli wrote:
> On 10/25/14 07:01, Andrew Lunn wrote:
> >> Here is another naming option:
> >>
> >> em1dsa0-virtual-0
> >
> > I prefer this over isa.
> >
> > However, i think there should be some sort of separator between the
> > network device
> Here is another naming option:
>
> em1dsa0-virtual-0
I prefer this over isa.
However, i think there should be some sort of separator between the
network device name and dsa.
Andrew
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 10/25/14 07:01, Andrew Lunn wrote:
>> Here is another naming option:
>>
>> em1dsa0-virtual-0
>
> I prefer this over isa.
>
> However, i think there should be some sort of separator between the
> network device name and dsa.
Considering that network devices can be renamed, do we want it to be
On 10/25/14 07:01, Andrew Lunn wrote:
>> Here is another naming option:
>>
>> em1dsa0-virtual-0
>
> I prefer this over isa.
>
> However, i think there should be some sort of separator between the
> network device name and dsa.
Considering that network devices can be renamed, do we want it to be
On 10/25/14 07:01, Andrew Lunn wrote:
Here is another naming option:
em1dsa0-virtual-0
I prefer this over isa.
However, i think there should be some sort of separator between the
network device name and dsa.
Considering that network devices can be renamed, do we want it to be
included
On 10/25/14 07:01, Andrew Lunn wrote:
Here is another naming option:
em1dsa0-virtual-0
I prefer this over isa.
However, i think there should be some sort of separator between the
network device name and dsa.
Considering that network devices can be renamed, do we want it to be
included
Here is another naming option:
em1dsa0-virtual-0
I prefer this over isa.
However, i think there should be some sort of separator between the
network device name and dsa.
Andrew
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On Sat, Oct 25, 2014 at 10:23:27AM -0700, Florian Fainelli wrote:
On 10/25/14 07:01, Andrew Lunn wrote:
Here is another naming option:
em1dsa0-virtual-0
I prefer this over isa.
However, i think there should be some sort of separator between the
network device name and dsa.
On 10/25/2014 07:01 AM, Andrew Lunn wrote:
Here is another naming option:
em1dsa0-virtual-0
I prefer this over isa.
However, i think there should be some sort of separator between the
network device name and dsa.
Fine with me. Any preference ? Note that '-' is not permitted.
Guenter
--
On 10/23/2014 12:55 PM, Andrew Lunn wrote:
[ ... ]
Does hwmon offer a function to sanitise a string?
No, that wasn't necessary so far. The 'name' string is a constant string
provided by the driver.
The switch index definitely should be used and i would probably
combine that with a sanitised
On Thu, Oct 23, 2014 at 09:55:26PM +0200, Andrew Lunn wrote:
> On Thu, Oct 23, 2014 at 11:43:22AM -0700, Guenter Roeck wrote:
> > On Thu, Oct 23, 2014 at 08:03:57PM +0200, Andrew Lunn wrote:
> > > > No, I am not saying that. The hwmon device's parent device will tell,
> > > > which is how it works
From: Guenter Roeck
Date: Thu, 23 Oct 2014 22:40:59 -0700
> I see two options for that:
>
> - Add
> select HWMON
> to the NET_DSA Kconfig entry.
> Example is Broadcom TIGON3 driver.
>
> - Add a DSA_HWMON Kconfig entry to define the dependencies and
> to let the user select if the
On 10/24/2014 05:52 AM, Florian Fainelli wrote:
Le 23/10/2014 22:40, Guenter Roeck a écrit :
On 10/23/2014 10:03 PM, David Miller wrote:
From: Guenter Roeck
Date: Wed, 22 Oct 2014 22:06:41 -0700
On 10/22/2014 09:37 PM, Florian Fainelli wrote:
2014-10-22 21:03 GMT-07:00 Guenter Roeck :
On 10/24/2014 05:52 AM, Florian Fainelli wrote:
Le 23/10/2014 22:40, Guenter Roeck a écrit :
On 10/23/2014 10:03 PM, David Miller wrote:
From: Guenter Roeck li...@roeck-us.net
Date: Wed, 22 Oct 2014 22:06:41 -0700
On 10/22/2014 09:37 PM, Florian Fainelli wrote:
2014-10-22 21:03 GMT-07:00
From: Guenter Roeck li...@roeck-us.net
Date: Thu, 23 Oct 2014 22:40:59 -0700
I see two options for that:
- Add
select HWMON
to the NET_DSA Kconfig entry.
Example is Broadcom TIGON3 driver.
- Add a DSA_HWMON Kconfig entry to define the dependencies and
to let the user select
On Thu, Oct 23, 2014 at 09:55:26PM +0200, Andrew Lunn wrote:
On Thu, Oct 23, 2014 at 11:43:22AM -0700, Guenter Roeck wrote:
On Thu, Oct 23, 2014 at 08:03:57PM +0200, Andrew Lunn wrote:
No, I am not saying that. The hwmon device's parent device will tell,
which is how it works for all
On 10/23/2014 12:55 PM, Andrew Lunn wrote:
[ ... ]
Does hwmon offer a function to sanitise a string?
No, that wasn't necessary so far. The 'name' string is a constant string
provided by the driver.
The switch index definitely should be used and i would probably
combine that with a sanitised
Le 23/10/2014 22:40, Guenter Roeck a écrit :
On 10/23/2014 10:03 PM, David Miller wrote:
From: Guenter Roeck
Date: Wed, 22 Oct 2014 22:06:41 -0700
On 10/22/2014 09:37 PM, Florian Fainelli wrote:
2014-10-22 21:03 GMT-07:00 Guenter Roeck :
Some Marvell switches provide chip temperature data.
On 10/23/2014 10:03 PM, David Miller wrote:
From: Guenter Roeck
Date: Wed, 22 Oct 2014 22:06:41 -0700
On 10/22/2014 09:37 PM, Florian Fainelli wrote:
2014-10-22 21:03 GMT-07:00 Guenter Roeck :
Some Marvell switches provide chip temperature data.
Add support for reporting it to the dsa
From: Guenter Roeck
Date: Wed, 22 Oct 2014 22:06:41 -0700
> On 10/22/2014 09:37 PM, Florian Fainelli wrote:
>> 2014-10-22 21:03 GMT-07:00 Guenter Roeck :
>>> Some Marvell switches provide chip temperature data.
>>> Add support for reporting it to the dsa infrastructure.
>>>
>>> Signed-off-by:
On Thu, Oct 23, 2014 at 11:43:22AM -0700, Guenter Roeck wrote:
> On Thu, Oct 23, 2014 at 08:03:57PM +0200, Andrew Lunn wrote:
> > > No, I am not saying that. The hwmon device's parent device will tell,
> > > which is how it works for all other hwmon devices.
> >
> > O.K, so parent is important.
>
On Thu, Oct 23, 2014 at 08:03:57PM +0200, Andrew Lunn wrote:
> > No, I am not saying that. The hwmon device's parent device will tell,
> > which is how it works for all other hwmon devices.
>
> O.K, so parent is important.
>
> > Not really. Again, the parent device provides that information.
> No, I am not saying that. The hwmon device's parent device will tell,
> which is how it works for all other hwmon devices.
O.K, so parent is important.
> Not really. Again, the parent device provides that information. libsensors,
> which is the preferred way of accessing sensors information
On Thu, Oct 23, 2014 at 06:54:59PM +0200, Andrew Lunn wrote:
> On Thu, Oct 23, 2014 at 09:27:55AM -0700, Guenter Roeck wrote:
> > On Thu, Oct 23, 2014 at 03:47:06PM +0200, Andrew Lunn wrote:
> > > > >>+static DEVICE_ATTR_RO(temp1_input);
> > > > >
> > > > >You probably want the number of
On Thu, Oct 23, 2014 at 09:27:55AM -0700, Guenter Roeck wrote:
> On Thu, Oct 23, 2014 at 03:47:06PM +0200, Andrew Lunn wrote:
> > > >>+static DEVICE_ATTR_RO(temp1_input);
> > > >
> > > >You probably want the number of temperature sensors to come from the
> > > >switch driver, and support arbitrary
On Thu, Oct 23, 2014 at 03:47:06PM +0200, Andrew Lunn wrote:
> > >>+static DEVICE_ATTR_RO(temp1_input);
> > >
> > >You probably want the number of temperature sensors to come from the
> > >switch driver, and support arbitrary number of temperature sensors?
> >
> > In that case we would need the
> >>+static DEVICE_ATTR_RO(temp1_input);
> >
> >You probably want the number of temperature sensors to come from the
> >switch driver, and support arbitrary number of temperature sensors?
>
> In that case we would need the number of sensors, pass a sensor index,
> and create a dynamic number of
On 10/23/2014 01:24 AM, Richard Cochran wrote:
On Wed, Oct 22, 2014 at 10:06:41PM -0700, Guenter Roeck wrote:
On 10/22/2014 09:37 PM, Florian Fainelli wrote:
You probably want the number of temperature sensors to come from the
switch driver, and support arbitrary number of temperature sensors?
On Wed, Oct 22, 2014 at 10:06:41PM -0700, Guenter Roeck wrote:
> On 10/22/2014 09:37 PM, Florian Fainelli wrote:
> >You probably want the number of temperature sensors to come from the
> >switch driver, and support arbitrary number of temperature sensors?
>
> In that case we would need the number
On Wed, Oct 22, 2014 at 10:06:41PM -0700, Guenter Roeck wrote:
On 10/22/2014 09:37 PM, Florian Fainelli wrote:
You probably want the number of temperature sensors to come from the
switch driver, and support arbitrary number of temperature sensors?
In that case we would need the number of
On 10/23/2014 01:24 AM, Richard Cochran wrote:
On Wed, Oct 22, 2014 at 10:06:41PM -0700, Guenter Roeck wrote:
On 10/22/2014 09:37 PM, Florian Fainelli wrote:
You probably want the number of temperature sensors to come from the
switch driver, and support arbitrary number of temperature sensors?
+static DEVICE_ATTR_RO(temp1_input);
You probably want the number of temperature sensors to come from the
switch driver, and support arbitrary number of temperature sensors?
In that case we would need the number of sensors, pass a sensor index,
and create a dynamic number of attributes.
On Thu, Oct 23, 2014 at 03:47:06PM +0200, Andrew Lunn wrote:
+static DEVICE_ATTR_RO(temp1_input);
You probably want the number of temperature sensors to come from the
switch driver, and support arbitrary number of temperature sensors?
In that case we would need the number of sensors,
On Thu, Oct 23, 2014 at 09:27:55AM -0700, Guenter Roeck wrote:
On Thu, Oct 23, 2014 at 03:47:06PM +0200, Andrew Lunn wrote:
+static DEVICE_ATTR_RO(temp1_input);
You probably want the number of temperature sensors to come from the
switch driver, and support arbitrary number of
On Thu, Oct 23, 2014 at 06:54:59PM +0200, Andrew Lunn wrote:
On Thu, Oct 23, 2014 at 09:27:55AM -0700, Guenter Roeck wrote:
On Thu, Oct 23, 2014 at 03:47:06PM +0200, Andrew Lunn wrote:
+static DEVICE_ATTR_RO(temp1_input);
You probably want the number of temperature sensors to come
No, I am not saying that. The hwmon device's parent device will tell,
which is how it works for all other hwmon devices.
O.K, so parent is important.
Not really. Again, the parent device provides that information. libsensors,
which is the preferred way of accessing sensors information from
On Thu, Oct 23, 2014 at 08:03:57PM +0200, Andrew Lunn wrote:
No, I am not saying that. The hwmon device's parent device will tell,
which is how it works for all other hwmon devices.
O.K, so parent is important.
Not really. Again, the parent device provides that information. libsensors,
On Thu, Oct 23, 2014 at 11:43:22AM -0700, Guenter Roeck wrote:
On Thu, Oct 23, 2014 at 08:03:57PM +0200, Andrew Lunn wrote:
No, I am not saying that. The hwmon device's parent device will tell,
which is how it works for all other hwmon devices.
O.K, so parent is important.
Not
From: Guenter Roeck li...@roeck-us.net
Date: Wed, 22 Oct 2014 22:06:41 -0700
On 10/22/2014 09:37 PM, Florian Fainelli wrote:
2014-10-22 21:03 GMT-07:00 Guenter Roeck li...@roeck-us.net:
Some Marvell switches provide chip temperature data.
Add support for reporting it to the dsa
On 10/23/2014 10:03 PM, David Miller wrote:
From: Guenter Roeck li...@roeck-us.net
Date: Wed, 22 Oct 2014 22:06:41 -0700
On 10/22/2014 09:37 PM, Florian Fainelli wrote:
2014-10-22 21:03 GMT-07:00 Guenter Roeck li...@roeck-us.net:
Some Marvell switches provide chip temperature data.
Add
Le 23/10/2014 22:40, Guenter Roeck a écrit :
On 10/23/2014 10:03 PM, David Miller wrote:
From: Guenter Roeck li...@roeck-us.net
Date: Wed, 22 Oct 2014 22:06:41 -0700
On 10/22/2014 09:37 PM, Florian Fainelli wrote:
2014-10-22 21:03 GMT-07:00 Guenter Roeck li...@roeck-us.net:
Some Marvell
On 10/22/2014 09:37 PM, Florian Fainelli wrote:
2014-10-22 21:03 GMT-07:00 Guenter Roeck :
Some Marvell switches provide chip temperature data.
Add support for reporting it to the dsa infrastructure.
Signed-off-by: Guenter Roeck
---
[snip]
+/* hwmon support
2014-10-22 21:03 GMT-07:00 Guenter Roeck :
> Some Marvell switches provide chip temperature data.
> Add support for reporting it to the dsa infrastructure.
>
> Signed-off-by: Guenter Roeck
> ---
[snip]
> +/* hwmon support
> /
> +
>
Some Marvell switches provide chip temperature data.
Add support for reporting it to the dsa infrastructure.
Signed-off-by: Guenter Roeck
---
include/net/dsa.h | 6 +++
net/dsa/dsa.c | 111 ++
2 files changed, 117 insertions(+)
diff
Some Marvell switches provide chip temperature data.
Add support for reporting it to the dsa infrastructure.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
include/net/dsa.h | 6 +++
net/dsa/dsa.c | 111 ++
2 files changed, 117
2014-10-22 21:03 GMT-07:00 Guenter Roeck li...@roeck-us.net:
Some Marvell switches provide chip temperature data.
Add support for reporting it to the dsa infrastructure.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
[snip]
+/* hwmon support
On 10/22/2014 09:37 PM, Florian Fainelli wrote:
2014-10-22 21:03 GMT-07:00 Guenter Roeck li...@roeck-us.net:
Some Marvell switches provide chip temperature data.
Add support for reporting it to the dsa infrastructure.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
[snip]
+/* hwmon
50 matches
Mail list logo
