From: Rafał Miłecki
It's just an example, but lets make it look more real to don't confuse
people about possible REG_RULE usage. Channels are 20 MHz wide, so start
and end frequencies are 10 MHz away from the center one.
Signed-off-by: Rafał Miłecki
---
Documentation/networking/regulatory.txt
From: Rafał Miłecki
It's maintained by Seth Forshe for a long time now.
Signed-off-by: Rafał Miłecki
Cc: Seth Forshee
---
Documentation/networking/regulatory.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/networking/regulatory.txt
b/Documentation/networ
On 16-12-16, 16:47, Shilpasri G Bhat wrote:
> Signed-off-by: Shilpasri G Bhat
> ---
> Documentation/cpu-freq/user-guide.txt | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/cpu-freq/user-guide.txt
> b/Documentation/cpu-freq/user-guide.txt
> index 109e97b
Documentation for perf usage and Hisilicon SoC PMU uncore events.
The Hisilicon SOC has event counters for hardware modules like
L3 cache, Miscellaneous node etc. These events are all uncore.
Signed-off-by: Anurup M
Signed-off-by: Shaokun Zhang
---
Documentation/perf/hisi-pmu.txt | 75 +
On Wed, Nov 30, 2016 at 10:17 AM, Peter Rosin wrote:
> This is a generic simple i2c mux that uses the generic multiplexer
> subsystem to do the muxing.
> +static const struct of_device_id i2c_mux_of_match[] = {
> + { .compatible = "i2c-mux-simple,parent-locked",
> + .data = (void *)
Hi All,
I have very little idea how the internals of the kernel-doc processing
code work, but was wondering if it would be possible to suppress warnings
of the type:
./include/linux/iio/buffer.h:142: warning: Excess struct/union/enum/typedef
member 'ref' description in 'iio_buffer'
when the me
This is a manual conversion of the existing DocBook documentation
for IIO. The intent is not to substantially change any of the
content in this patch, but to give a base to build upon.
Signed-off-by: Jonathan Cameron
---
V2 changes:
- some small cleanups around shortening titles where the II
On 30/11/16 08:16, Peter Rosin wrote:
> Hi!
Just a quick note to encourage people to take a look at this series
if they have the time (I can't talk as it took me almost exactly a
month to take a proper look).
It actually ended up a good deal simpler than I expected so I'm falling
on the side of th
On 30/11/16 08:17, Peter Rosin wrote:
> Analog Devices ADG792A/G is a triple 4:1 mux.
>
> Signed-off-by: Peter Rosin
Looks pretty good. Some minor suggestions inline.
This convinced me of two things:
1. Need a separate subsystem directory for muxes - having them under misc
is going to lead to lo
On 30/11/16 08:17, Peter Rosin wrote:
> Analog Devices ADG792A/G is a triple 4:1 mux.
>
> Signed-off-by: Peter Rosin
Few comments inline. Worth adding anything about the gpio (output pins) to
the binding at this stage as well? Would certainly be nice to support
them.
Jonathan
> ---
> .../devi
On 30/11/16 08:17, Peter Rosin wrote:
> This is a generic simple i2c mux that uses the generic multiplexer
> subsystem to do the muxing.
>
> The user can select if the mux is to be mux-locked and parent-locked
> as described in Documentation/i2c/i2c-topology.
>
> Signed-off-by: Peter Rosin
Looks
11 matches
Mail list logo
