This patch adds support for ASEM opto-isolated dual channels
CAN raw device (http://www.asem.it)
Signed-off-by: Flavio Suligoi
---
v2: - renamed ASEM_... constants to reduce space size;
- remove "else" in "plx_pci_reset_asem_dual_can_raw" function to avoid
string
Fix the following typo:
"recommeded" --> "recommended"
"firmare" --> "firmware"
Signed-off-by: Flavio Suligoi
---
drivers/watchdog/wdat_wdt.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/watchdog/wdat_wdt.c b/
[ 3] local 192.168.200.159 port 32778 connected with 192.168.200.1 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec
[ 3] Sent 893 datagrams
ht-700 ~ # uname -a
Linux ht-700 5.12.0-rc2-watchdog+ #12 SMP Thu Apr 8 11:08:49 CEST 2021 x86_64
x8
Sometimes, in some embedded systems boards (i.e. ARM boards),
the NVM eeprom is not mounted, to save cost and space.
In this case it is necessary to bypass the NVM management
and directly force the MAC address using a kernel command-line
parameter (macaddr).
Signed-off-by: Flavio Suligoi
Sometimes, in some embedded systems boards (i.e. ARM boards),
the NVM eeprom is not mounted, to save cost and space.
In this case it is necessary to bypass the NVM management
and directly force the MAC address using a kernel command-line
parameter (macaddr).
Signed-off-by: Flavio Suligoi
v2
Sometimes, in some embedded systems boards (i.e. ARM boards),
the NVM eeprom is not mounted, to save cost and space.
In this case it is necessary to bypass the NVM management
and directly force the MAC address using a kernel command-line
parameter (macaddr).
Signed-off-by: Flavio Suligoi
> -Original Message-
> From: Andrew Lunn
> Sent: giovedì 28 febbraio 2019 16:33
> To: Flavio Suligoi
> Cc: Jeff Kirsher ; David S . Miller
> ; intel-wired-...@lists.osuosl.org;
> net...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v3] net:
> > Hi Andrew,
> >
> > we produce a lot of boards and we have to change the MAC address,
> > from u-boot, for every board. So I must save in the u-boot
> > environment (SPI NOR flash) the MAC address for every board.
>
> Hi Flavio
>
> u-boot should be able to write the MAC address in the correct
> >> > Hi Flavio
> >> >
> >> > u-boot should be able to write the MAC address in the correct part of
> >> > device tree. Boards have been doing this a long time.
> >> >
> >> > Module parameters are considered bad. You should only do it if you
> >> > have no other option. Here you do have another op
The file:
Documentation/acpi/aml-debugger.txt
reports an obsolete path for the acpidbg tool.
Signed-off-by: Flavio Suligoi
---
Documentation/acpi/aml-debugger.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/acpi/aml-debugger.txt
b/Documentation/acpi
alarm" enable the RTC to generate the
hw signaling in case of battery-low event.
Signed-off-by: Flavio Suligoi
---
Documentation/devicetree/bindings/rtc/rtc.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/rtc/rtc.txt
b/Documentation/devicetree/bi
reg = <0x51>;
battery-low-hw-alarm;
status = "okay";
};
};
Signed-off-by: Flavio Suligoi
---
drivers/rtc/rtc-pcf2127.c | 33 +
1 file changed, 33 insertions(+)
diff --git a/drivers/rtc/rtc-pcf21
Hi Alexandre,
> Hi,
>
> On 03/04/2019 16:52:44+0200, Flavio Suligoi wrote:
> > Some RTC devices have a battery-low automatic detection circuit.
> > The battery-low event is usually reported with:
> >
> > - a bit change in a RTC status register
> > - a hw
Hi Alexandre,
> On 03/04/2019 16:52:45+0200, Flavio Suligoi wrote:
> > The pcf2127 has an automatic battery-low detection function.
> >
> > In case of battery-low event, an interrupt generation through
> > the pin INTn (active low) can be enabled, setting the fl
Hi,
> On 03/04/2019 15:06:17+0000, Flavio Suligoi wrote:
> > Hi Alexandre,
> >
> > > Hi,
> > >
> > > On 03/04/2019 16:52:44+0200, Flavio Suligoi wrote:
> > > > Some RTC devices have a battery-low automatic detection circuit.
> > > On 03/04/2019 16:52:45+0200, Flavio Suligoi wrote:
> > > > The pcf2127 has an automatic battery-low detection function.
> > > >
> > > > In case of battery-low event, an interrupt generation through
> > > > the pin INTn (active
Hi,
> On 03/04/2019 15:49:03+0000, Flavio Suligoi wrote:
> > > Then, you should probably not enable BLIE because this will cause
> issues
> > > with the alarm functionnality.. It is certainly enough to use
> > > RTC_VL_READ periodically.
> >
> > We us
> On 03/04/2019 16:09:14+0000, Flavio Suligoi wrote:
> > Hi,
> >
> > > On 03/04/2019 15:49:03+, Flavio Suligoi wrote:
> > > > > Then, you should probably not enable BLIE because this will cause
> > > issues
> > > > >
HI,
> On 06/04/2019 01:07:13-0500, Rob Herring wrote:
> > On Wed, Apr 03, 2019 at 04:52:44PM +0200, Flavio Suligoi wrote:
> > > Some RTC devices have a battery-low automatic detection circuit.
> > > The battery-low event is usually reported with:
> > >
Add an info message for the PXA2xx device driver start-up,
with the indication of the transfer mode used (DMA or GPIO).
This info is useful to individuate the timing when
the module starts.
Signed-off-by: Flavio Suligoi
---
drivers/spi/spi-pxa2xx.c | 3 +++
1 file changed, 3 insertions
Hi Jarkko,
> Hi
>
> On 4/8/19 6:22 PM, Flavio Suligoi wrote:
> > Add an info message for the PXA2xx device driver start-up,
> > with the indication of the transfer mode used (DMA or GPIO).
> >
> > This info is useful to individuate the timing when
> > t
Hi Rob,
> On Mon, Apr 8, 2019 at 2:22 AM Flavio Suligoi wrote:
> >
> > HI,
> >
> > > On 06/04/2019 01:07:13-0500, Rob Herring wrote:
> > > > On Wed, Apr 03, 2019 at 04:52:44PM +0200, Flavio Suligoi wrote:
> > > > > Some RTC devices have
Hi Jarkko,
> >
> >> Hi
> >>
> >> On 4/8/19 6:22 PM, Flavio Suligoi wrote:
> >>> Add an info message for the PXA2xx device driver start-up,
> >>> with the indication of the transfer mode used (DMA or GPIO).
> >>>
> >&g
> On 4/10/19 11:13 AM, Flavio Suligoi wrote:
> >> [9.506895] pxa2xx-spi pxa2xx-spi.13: no DMA channels available,
> >> using PIO
> >> [9.516770] pxa2xx-spi pxa2xx-spi.13: registered master spi2
> >> [9.518527] pxa2xx-spi pxa2xx-spi.13: PXA2
Add an info message for the PXA2xx device driver start-up,
with the indication of:
- mode (slave device or master controller)
- transfer mode (DMA or GPIO)
Signed-off-by: Flavio Suligoi
---
v1: - first version
v2: - remove warning message "no DMA channels available, usin
> On 4/10/19 12:47 PM, Flavio Suligoi wrote:
> > Add an info message for the PXA2xx device driver start-up,
> > with the indication of:
> >
> > - mode (slave device or master controller)
> > - transfer mode (DMA or GPIO)
> >
> > Signed-off-by: Flavio
Hi Mark,
> On Mon, Apr 08, 2019 at 05:22:44PM +0200, Flavio Suligoi wrote:
> > Add an info message for the PXA2xx device driver start-up,
> > with the indication of the transfer mode used (DMA or GPIO).
> >
> > This info is useful to individuate the timing when
> &g
> On Wed, Apr 10, 2019 at 11:47:43AM +0000, Flavio Suligoi wrote:
>
> > You have right about to avoid too many boot messages,
> > but in this case, using an x86 machine and with
> > the spi-pxa2xx in DMA mode, so without the message:
>
> > "no DMA channels
clock of 12.5MHz,
so the max rate of the SPI device clock is respected.
Signed-off-by: Flavio Suligoi
---
drivers/spi/spi-pxa2xx.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
index f7068cc..c9560a1 100644
--- a
With dw_dmac, sometimes the request of a DMA channel fails because
the DMA driver is not ready, so an explicit dependency request
is necessary.
Signed-off-by: Flavio Suligoi
---
drivers/spi/spi-pxa2xx.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi
Hi Mark,
> On Wed, Apr 10, 2019 at 02:51:36PM +0200, Flavio Suligoi wrote:
> > With dw_dmac, sometimes the request of a DMA channel fails because
> > the DMA driver is not ready, so an explicit dependency request
> > is necessary.
>
> While this isn't going to
> > I think that the problem could be related to how the DMA channel is
> requested.
> > At the moment the function used are:
>
> > pxa2xx_spi_dma_setup --> dma_request_slave_channel_compat -->
> > --> __dma_request_slave_channel_compat --> dma_request_slave_channel -->
> > --> dma_request_chan
>
> > > Right, yes - that analysis seems correct. The interfaces seem a bit
> > > weird here but fixing them looks like the most complete and robust
> fix.
>
> > Ok Mark, I'll fix this problem as soon as I can, using EPROBE_DEFER.
> > For now, in my application, I use the patch that I already sent,
Hi Jarkko,
> > diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
> > index f7068cc..c9560a1 100644
> > --- a/drivers/spi/spi-pxa2xx.c
> > +++ b/drivers/spi/spi-pxa2xx.c
> > @@ -884,10 +884,15 @@ static unsigned int ssp_get_clk_div(struct
> driver_data *drv_data, int rate)
> >
> >
ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
Package () {
Package () {"compatible", "mr25h40"},
}
})
e (_DSD, Package () {
ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
Package () {
Package () {"compatible", "mr25h40"},
}
The file linux/pcwd.h is not more present in the kernel
sources. Its information is now moved into the file:
include/uapi/linux/watchdog.h
Signed-off-by: Flavio Suligoi
---
Documentation/watchdog/pcwd-watchdog.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
setting of the
BIOS setup). In other cases, when this BIOS feature is not
present, the possibility to start the watchdog immediately
after the module loading can be very useful.
Signed-off-by: Flavio Suligoi
---
drivers/watchdog/wdat_wdt.c | 8
1 file changed, 8 insertions(+)
diff --git
Hi Mika,
> > const struct wdat_instruction *instr, u32 *value)
> > {
> > @@ -437,6 +443,8 @@ static int wdat_wdt_probe(struct platform_device
> *pdev)
> > }
> >
> > wdat_wdt_boot_status(wdat);
> > + if (start_enabled)
> > + wdat_wdt_start(&wdat->wdd);
>
> No objections t
The website:
http://wiki.minnowboard.org
doesn't exist anymore. The same pages are moved to:
https://www.elinux.org/Minnowboard
Other improvements concern the introduction of some rst
semantic markup in the document.
Signed-off-by: Flavio Suligoi
---
v1: remove added backq
When an EFI variable is reading from:
/sys/firmware/efi/efivars
(for example using "hexdump"), the first 4 bytes of the
output are not the real EFI variable data, but the variable
attributes (in little-endian format).
Signed-off-by: Flavio Suligoi
---
v1: remove added backq
The gpio-line-names lists must respect some rules.
This patch adds a new rule in documentation, to avoid
the use of duplicate names in the same gpiochip.
Signed-off-by: Flavio Suligoi
---
Documentation/firmware-guide/acpi/gpio-properties.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a
ave a possibility for
> > backporting. Patches 3 and 4 fix a minor warnings from Sparse while
> > moving to a new APIs. Patch 5 is MODULE_VERSION() clean up.
> >
> > Tested on Intel Minnowboard (v1).
>
> Anything should I do here?
it's ok for me
> --
>
Hi Guenter,
...
> On 4/9/21 2:34 AM, Flavio Suligoi wrote:
> > The new parameter "start_enabled" starts the watchdog at the same time
> > of the module insertion.
> > This feature is very useful in embedded systems, to avoid cases where
> > the s
> >>> in this way it is common for all the watchdog hardware implementations.
> >>>
> >>> Note: to use only for watchdog drivers which doesn't support this
> >>> parameter by itself.
> >>>
> >>> Signed-off-by:
d when the watchdog driver is build as "built-in".
This parameter involves the "core" section of the watchdog driver;
in this way it is common for all the watchdog hardware implementations.
Signed-off-by: Flavio Suligoi
---
v2: - check WDOG_HW_RUNNING before starting watchdog;
d when the watchdog driver is build as built-in.
This parameter involves the "core" section of the watchdog driver;
in this way it is common for all the watchdog hardware implementations.
Note: to use only for watchdog drivers which doesn't support this
parameter by itself.
Sign
Hi Guenter
> >>>const struct wdat_instruction *instr, u32 *value) { @@ -437,6
> >>> +443,8 @@ static int wdat_wdt_probe(struct platform_device
> >> *pdev)
> >>> }
> >>>
> >>> wdat_wdt_boot_status(wdat);
> >>> + if (start_enabled)
> >>> + wdat_wdt_start(&wdat->wdd);
> >>
> >> No ob
ded to the pins of a GPIO expander on the PCI bus.
In order to find the ACPI name of a PCI device , it's necessary
to disassemble the BIOS ACPI tables (in particular the DSDT)
and also to analyze the PCI bus topology of the board.
This patch, with a practical example, show how to do this.
Sign
For inline web links, no special markup are needed.
Signed-off-by: Flavio Suligoi
---
Documentation/firmware-guide/acpi/dsd/leds.rst | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/firmware-guide/acpi/dsd/leds.rst
b/Documentation/firmware-guide/acpi
Hi Andy!
> On Thu, Nov 19, 2020 at 11:12:33AM +0100, Flavio Suligoi wrote:
>
> Thank you very much for nice piece of documentation!
> My comments below.
Thanks for your suggestions! I'll use them in the next version
of the patch!
> > +particular the DSDT (see also [2
ded to the pins of a GPIO expander on the PCI bus.
In order to find the ACPI name of a PCI device, it's necessary
to disassemble the BIOS ACPI tables (in particular the DSDT)
and also to analyze the PCI bus topology of the board.
This patch, with a practical example, show how to do this.
Sign
Actions:
- fix spelling mistake
- reduce some double spaces to a single one
- substitute spaces with tab
Signed-off-by: Flavio Suligoi
---
Documentation/vm/hwpoison.rst | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/vm/hwpoison.rst b
Hi Jon,
[PATCH v1] docs/vm: hwpoison: fix spelling mistakes
>
> On Wed, 25 Nov 2020 17:52:22 +0100
> Flavio Suligoi wrote:
>
> > Actions:
> >
> > - fix spelling mistake
> > - reduce some double spaces to a single one
>
> Please don't make chang
de_enabled()
* watchdog_global_param_start_enabled()
* watchdog_global_param_nowayout_enabled()
Flavio Suligoi (2):
watchdog: add global watchdog kernel module parameters structure
watchdog: wdat: add start_enable global parameter
Documentation/watchdog/index.rst | 1 +
ged by the watchdog_core
itself.
Signed-off-by: Flavio Suligoi
---
drivers/watchdog/wdat_wdt.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/watchdog/wdat_wdt.c b/drivers/watchdog/wdat_wdt.c
index cec7917790e5..7304a335227f 100644
--- a/drivers/watchdog/wdat_wdt.c
+++ b/drivers/watchdog/
the base structure to add the global parameters, starting
with some common integer data (timeout, ioport, irq) and a bitwise
"features" flag, where we can store some boolean features (verbose,
test_mode, start_enabled, nowayout, etc.)
Signed-off-by: Flavio Suligoi
---
Documentat
global_parameters_init()*, in the same file.
> >
> > Global parameters use
> > =
> >
> > Each watchdog driver, to check if one of the global parameters is
> > enabled, can use the corresponding in-line function declared in
>
> Hi,
>
Hi Randy,
> On 3/8/21 3:21 AM, Flavio Suligoi wrote:
> > Different watchdog modules frequently require the same type of
> > parameters (for example: timeout, nowayout feature, start wdog on
> > module insertion, etc.).
...
> > +In this way, e
the spi_nor_of_table structure.
With this change, all the SPI NOR devices (JEDEC and
non-JEDEC) can be detected by the kernel (and the above
example of ACPI table finally works).
Signed-off-by: Flavio Suligoi
---
drivers/mtd/spi-nor/core.c | 13 +
1 file changed, 13 insertions(+)
diff --gi
The old file:
drivers/mtd/spi-nor/spi-nor.c
is not more present and now some of its code is
contained in:
drivers/mtd/spi-nor/core.c
This patch fix/remove the references to the old
spi-nor.c file.
Signed-off-by: Flavio Suligoi
---
Documentation/driver-api/mtd/spi-nor.rst | 2 +-
drivers/mtd
Hi Greg,
> >
> > switch (chip) {
> > case CHIP_ID_F81865:
> > + chip_name = "F81865";
> > + break;
> > case CHIP_ID_F81866:
> > + chip_name = "F81866";
> > + break;
> > case CHIP_ID_F81966:
> > + chip_name = "F81966";
> > +
Hi Greg,
> > > > + chip_name = "F81216H";
> > > > + break;
> > > > case CHIP_ID_F81216:
> > > > + chip_name = "F81216";
> > > > break;
> > > > default:
> > > > return -ENODEV;
> > > > }
> > > >
> > >
Hi Greg,
> > > Fintek F81216AD
> > > > 00:02: ttyS3 at I/O 0x2e8 (irq = 11, base_baud = 115200) is a 16550A
> -
> > > Fintek F81216AD
> > > >
> > > > where the "extra_name", if not empty, is printed
> > > > at the end of the line.
> > > > For practical space reasons, the "extra_name" length
> > >
Hi Peter,
> >>>
> >>> dmesg| grep ttyS
> >>
> >> But as they work the same, why does it matter?
> >
> > Yes you are right, by the user point of view, they are the same.
> >
> >>
> >> Userspace should not care here. Isn't there some other id you can
> >> read/query for a hardware database tool to
ff-by: Flavio Suligoi
---
drivers/tty/serial/8250/8250_fintek.c | 25 +++--
1 file changed, 23 insertions(+), 2 deletions(-)
diff --git a/drivers/tty/serial/8250/8250_fintek.c
b/drivers/tty/serial/8250/8250_fintek.c
index 31c9e83ea3cb..ef2303cb5176 100644
--- a/drivers/tty/serial
Hi Andy,
> > This patch, with a practical example, show how to do this.
>
> Good enough, we can amend style and formatting later on.
> Reviewed-by: Andy Shevchenko
>
Thanks!
> > Signed-off-by: Flavio Suligoi
> > ---
>
> (Here you usually put a chang
Signed-off-by: Flavio Suligoi
---
Documentation/x86/x86_64/uefi.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/x86/x86_64/uefi.rst
b/Documentation/x86/x86_64/uefi.rst
index 88c3ba3..3b89410 100644
--- a/Documentation/x86/x86_64/uefi.rst
+++ b/Documentation
In case of SPI error during the reading of the nor Id,
the probe fails without any error message related to
the JEDEC Id reading procedure.
Signed-off-by: Flavio Suligoi
---
drivers/mtd/spi-nor/spi-nor.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/spi-nor/spi
t messages
written during the initialization.
Signed-off-by: Flavio Suligoi
---
drivers/spi/spi-pxa2xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
index 6160fe0..f7068cc 100644
--- a/drivers/spi/spi-pxa2xx.c
+++ b/drive
The knowledge of the cache controller version
is very useful during the comparison of the performances
of similar boards, with similar CPU but different versions
of the L310 controller.
Signed-off-by: Flavio Suligoi
---
arch/arm/mm/cache-l2x0.c | 28
1 file changed
> -Original Message-
> From: David Woodhouse
> Sent: giovedì 7 marzo 2019 18:40
> To: Flavio Suligoi ; Brian Norris
> ; Boris Brezillon ;
> Marek Vasut ; Richard Weinberger ;
> Mark Brown ; Frieder Schrempf
> ; Yogesh Gaur ;
> linux-...@lists.infradead.org; l
Hi Joe,
> On Tue, 2020-06-09 at 18:02 +0200, Flavio Suligoi wrote:
> > Fix typo: "tigger" --> "trigger"
>
> Thanks.
>
> fyi:
>
> $ git grep -w -i tigger
Thanks for your suggestion!
> drivers/iio/common/cros_ec_sensors/cros_ec_sensors_core
Hi Jiri,
> Subject: Re: [PATCH 1/1] tty: fix spelling mistake
>
> On 09. 06. 20, 19:37, Joe Perches wrote:
> > On Tue, 2020-06-09 at 18:02 +0200, Flavio Suligoi wrote:
> >> Fix typo: "tigger" --> "trigger"
> >
> > Thanks.
> >
Fix typo: "triger" --> "trigger"
Signed-off-by: Flavio Suligoi
---
arch/arm/include/asm/cti.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/include/asm/cti.h b/arch/arm/include/asm/cti.h
index f8500e5d6ea8..ddd7b73a5870 100644
--- a/arc
Fix typo: "Tigger" --> "Trigger"
Signed-off-by: Flavio Suligoi
Reviewed-by: Alexander Dahl
---
drivers/leds/led-triggers.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/leds/led-triggers.c b/drivers/leds/led-triggers.c
index 79e30d2cb7a5..08
Fix typo: "triger" --> "trigger"
Signed-off-by: Flavio Suligoi
---
Documentation/devicetree/bindings/gpio/mediatek,mt7621-gpio.txt | 2 +-
.../devicetree/bindings/interrupt-controller/csky,mpintc.txt| 2 +-
Documentation/devicetree/bindings/timer/csky,mptimer.txt
.h file.
Signed-off-by: Flavio Suligoi
---
drivers/gpu/drm/i915/i915_reg.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
index 9d6536afc94b..c2153364724a 100644
--- a/drivers/gpu/drm/i915/i915_reg.h
+++
Fix typo: "trigered" --> "triggered"
Signed-off-by: Flavio Suligoi
---
drivers/net/ethernet/neterion/vxge/vxge-config.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/neterion/vxge/vxge-config.h
b/drivers/net/ethernet/neterion/v
Fix typo: "Triger" --> "Trigger"
Signed-off-by: Flavio Suligoi
---
drivers/net/ethernet/oki-semi/pch_gbe/pch_gbe.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/oki-semi/pch_gbe/pch_gbe.h
b/drivers/net/ethernet/oki-semi/
Fix typo: "EZUSB_REQUEST_TRIGER" --> "EZUSB_REQUEST_TRIGGER"
Signed-off-by: Flavio Suligoi
---
drivers/net/wireless/intersil/orinoco/orinoco_usb.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/net/wireless/intersil/orinoco/orino
All native pci drivers are in drivers/pci/controller,
but this comment still refers to the old pathname,
when all pci drivers were located directly under the
drivers/pci directory.
Signed-off-by: Flavio Suligoi
---
drivers/pci/controller/cadence/pcie-cadence-ep.c | 2 +-
1 file changed, 1
Hi Kalle,
>
> Flavio Suligoi writes:
>
> > Fix typo: "EZUSB_REQUEST_TRIGER" --> "EZUSB_REQUEST_TRIGGER"
> >
> > Signed-off-by: Flavio Suligoi
> > ---
> > drivers/net/wireless/intersil/orinoco/orinoco_usb.c | 6 +++---
> > 1
This comment still refers to the old driver pathname,
when all PCI drivers were located directly under the
drivers/pci directory.
Anyway the function name itself is enough, so we can
remove the overabundant path reference.
Signed-off-by: Flavio Suligoi
---
v1: - after the suggestion of Bjorn
Fix typo: "triger" --> "trigger"
Signed-off-by: Flavio Suligoi
Acked-by: Guo Ren
---
v1: add Acked-by: Guo Ren
Documentation/devicetree/bindings/gpio/mediatek,mt7621-gpio.txt | 2 +-
.../devicetree/bindings/interrupt-controller/csky,mpintc.txt| 2 +-
Documentat
Fix typo: "triger" --> "trigger"
Signed-off-by: Flavio Suligoi
---
arch/sh/include/asm/smc37c93x.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/sh/include/asm/smc37c93x.h b/arch/sh/include/asm/smc37c93x.h
index f054c30a171a..891f2f8f2f
Hi Andy,
> > > > > I was wondering if there is a generic GPIO driver that I can use
> Maybe I was not so clear, but as Bart mentioned the least you can do
> is simply define line name via "gpio-line-names" property. The problem
> here is when and how you would like to have them incorporated.
I al
Hi Andy,
> I guess you simply didn't get. The "gpio-line-names" property of GPIO
> *controller* (provider!) and you are trying to do something with the
> *consumer*
> if I got it right.
>
> And of course GPIO line, which has name, has no difference in use from
> another
> w/o name assigned. You w
Hi Andy,
sorry for the delay!
> > > My SSDT table is:
> >
> > See the difference? I can't help here.
This is the DSDT table related to the GPIO controller of my board:
Device (GPO1)
{
Name (_ADR, Zero) // _ADR: Address
Name (_HID, "INT3452") // _HID: Hardw
Hi Andy,
with my custom SSDT table:
DefinitionBlock ("gpio_button.aml", "SSDT", 5, "ASEMsp", "GPIO_BTN", 1)
{
External (_SB_.GPO1, DeviceObj)
Scope (\_SB.GPO1)
{
Device (BTNS)
{
Name (_HID, "ASEM0005") // _HID
HI Andy,
> > So, what about adding the following
> >
> >
> > (Replace '...' with meaningful line names or drop for now, but in any
> > case you need to provide as much names as lines of such GPIO
> > controller)
>
> I have checked the code, so it allows you to define from 0 up to all
> lines, but
Hi all,
I need to expose to the userspace a GPIO, physically connected to a board
push-button. This GPIO must expose a pre-defined name, such as
"user-push-button", so that the userspace applications can use it without
know any physical GPIO details.
I can customize the board BIOS and so my goal
Hi Bartosz,
> > I need to expose to the userspace a GPIO, physically connected to a
> board
> > push-button. This GPIO must expose a pre-defined name, such as
> > "user-push-button", so that the userspace applications can use it
> without
> > know any physical GPIO details.
> >
> > I can customize
Hi Andy and Bartosz,
> > >
> > > I need to expose to the userspace a GPIO, physically connected to a
> board
> > > push-button. This GPIO must expose a pre-defined name, such as
> > > "user-push-button", so that the userspace applications can use it
> without
> > > know any physical GPIO details.
The documentation reports the wrong macro names
related to the pca9532 instead of the pca955x
Signed-off-by: Flavio Suligoi
---
Documentation/devicetree/bindings/leds/leds-pca955x.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings
The documentation reports the wrong macro names
related to the pca9532 instead of the pca955x
Signed-off-by: Flavio Suligoi
---
Documentation/devicetree/bindings/leds/leds-pca955x.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings
> Subject: Re: [PATCH] dt-bindings: leds: fix macro names for pca955x
>
> On Tue 2020-05-26 11:20:52, Flavio Suligoi wrote:
> > The documentation reports the wrong macro names
> > related to the pca9532 instead of the pca955x
> >
> > Signed-off-by: Flavio Suli
> Subject: Re: [PATCH] dt-bindings: leds: fix macro names for pca955x
>
> On Tue 2020-05-26 09:25:58, Flavio Suligoi wrote:
> > > Subject: Re: [PATCH] dt-bindings: leds: fix macro names for pca955x
> > >
> > > On Tue 2020-05-26 11:20:52, Flavio Suligoi wrote:
&
When an EFI variable is reading from:
/sys/firmware/efi/efivars
(for example using "hexdump"), the first 4 bytes of the
output are not the real EFI variable data, but the variable
attributes (in little-endian format).
Signed-off-by: Flavio Suligoi
---
Documentation/filesystems/ef
The website:
http://wiki.minnowboard.org
doesn't exist anymore. The same pages are moved to:
https://www.elinux.org/Minnowboard
Other improvements concern the introduction of some rst
semantic markup in the document.
Signed-off-by: Flavio Suligoi
---
Documentation/admin-guide
1 - 100 of 136 matches
Mail list logo
