of 4.14-rc7 and tested it on an at91sam9g20 based
platform.
Tested-by: Alexander Dahl
Greets
Alex
Hello Alexandre,
Am Freitag, 23. Februar 2018, 18:15:52 CEST schrieb Alexandre Belloni:
> - using the PIT doesn't work well with preempt-rt because its interrupt is
>shared (in particular with the UART and their interrupt flags are
>incompatible)
This is actually quite annoying when usin
This seems to have slipped in by accident when sorting the entries.
Fixes: ffbdd9172ee2f53020f763574b4cdad8d9760a4f
Signed-off-by: Alexander Dahl
---
drivers/net/can/usb/Kconfig | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/net/can/usb/Kconfig b/drivers/net/can/usb/Kconfig
Hei hei,
Am Freitag, 2. November 2018, 14:35:26 CET schrieb Jean-Michel Hautbois:
> Then, after looking into deeper details in the datasheet I understand
> it is connected through EBI and it sounds not so easy :D.
Did you read docs on that? You'll find the binding docs here:
Documentation/device
Hello Daniel,
Am Dienstag, 27. März 2018, 13:30:22 CEST schrieb Daniel Lezcano:
> Can you can give a rough amount for the irq rate on the timer ?
I used itop [1] now to get a rough estimate. First with kernel v4.14.29-rt25
(fully preempt RT):
INTNAME RATE MA
Hei hei,
Am Mittwoch, 28. März 2018, 17:50:33 CEST schrieb Alexandre Belloni:
> On 28/03/2018 at 17:31:35 +0200, Alexandre Belloni wrote:
> > > Do you have an explanation of why the rate is much higher ?
> >
> > The core is giving deltas of 31 clocks instead of much more than that, I
> > guess I
Hello Alexandre,
Am Donnerstag, 29. März 2018, 12:45:42 CEST schrieb Alexandre Belloni:
> > This is the result:
> >
> > INTNAME RATE MAX
> >
> > 17 [vel timer@fffa] 1837 Ints/s (max: 1912)
> > 26 [ vel eth0] 3 Ints/s (max:11)
Hei hei,
Am Donnerstag, 29. März 2018, 10:01:26 CEST schrieb Alexander Dahl:
> This is the result:
>
> INTNAME RATE MAX
> 17 [vel timer@fffa] 1837 Ints/s (max: 1912)
> 26 [ vel eth0] 3 Ints/s (max:11)
Above was
Hello Jeff,
On Thu, Jan 14, 2021 at 09:50:50PM -0600, Jeff LaBundy wrote:
> On Thu, Jan 14, 2021 at 10:03:12AM +, Lee Jones wrote:
> > On Mon, 28 Dec 2020, Alexander Dahl wrote:
> >
> > > The node names for devices using the pwm-leds driver follow a certain
> >
/build/linux/arch/arm/boot/dts/berlin2cd-google-chromecast.dt.yaml:
leds: 'red', 'white' do not match any of the regexes: '^led(-[0-9a-f]+)?$',
'pinctrl-[0-9]+'
From schema:
/home/alex/src/linux/leds/Documentation/devicetree/bindings/leds/leds
The node names for devices using the pwm-leds driver follow a certain
naming scheme (now). Parent node name is not enforced, but recommended
by DT project.
Signed-off-by: Alexander Dahl
Reviewed-by: Neil Armstrong
---
Notes:
v8 -> v9:
* rebased on v5.11-rc1
v7 -&
/arm/boot/dts/stm32mp157c-lxa-mc1.dt.yaml: led-rgb:
'led-blue', 'led-green', 'led-red' do not match any of the regexes:
'^led(-[0-9a-f]+)?$', 'pinctrl-[0-9]+'
From schema:
/home/alex/src/linux/leds/Documentation/devicetree/bindings/leds/l
s/leds-pwm.yaml
Signed-off-by: Alexander Dahl
Acked-by: Jeff LaBundy
Acked-by: Rob Herring
---
Notes:
v8 -> v9:
* added forgotten Acked-by (Jeff LaBundy)
* rebased on v5.11-rc1
v7 -> v8:
* rebased on recent pavel/for-next (post v5.10-rc1)
* added Acke
)
v1:
- based on v5.9-rc2
- backport on v5.4.59 tested and working
Cc: linux-l...@vger.kernel.org
Cc: devicet...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-st...@st-md-mailman.stormreply.com
Cc: linux-amlo...@lists.infradead.org
Alexander
Hei hei,
I could not get ethernet to work on SAMA5D27-SOM1-EK1 with kernels v5.10 and
v5.11 built by a recent ptxdist based DistroKit BSP, while it used to work with
an older v4.19 kernel. Just applying this patch to the tree made ethernet
working again, thus:
Tested-by: Alexander Dahl
Not
Hello Hermes,
> Hermes Zhang hat am 24.03.2021 03:48 geschrieben:
>
>
> From: Hermes Zhang
>
> Document the device tree bindings of the multiple GPIOs LED driver
> Documentation/devicetree/bindings/leds/leds-multi-gpio.yaml.
>
> Signed-off-by: Hermes Zhang
> ---
>
> Notes:
> Add maxIt
Hello,
> Hermes Zhang hat am 24.03.2021 07:04 geschrieben:
>
>
> > >
> > > Notes:
> > > Add maxItems
> >
> > What about the other part of the series? I think you should send both
> > patches together with an introduction message on both. If you only change
> > one patch for a new version
Hello Andy,
Am Wed, Mar 31, 2021 at 03:27:05PM +0300 schrieb Andy Shevchenko:
> On Mon, Mar 29, 2021 at 2:18 PM Alexander Dahl wrote:
> >
> > Module probing with the parameter documented yielded this in kernel log:
> >
> > gpio_mockup: unknown parameter
s") long before introducing the documentation.
Fixes: commit 2fd1abe99e5f ("Documentation: gpio: add documentation for
gpio-mockup")
Signed-off-by: Alexander Dahl
---
Documentation/admin-guide/gpio/gpio-mockup.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/
Hei hei,
while experimenting with the gpio-mockup driver, I found minor flaws in
the documentation, addressed in the three patches of this series.
Greets
Alex
Alexander Dahl (3):
docs: gpio: mockup: Fix parameter name
docs: kernel-parameters: Move gpio-mockup for alphabetic order
docs
Missing since introduced in the driver.
Fixes: commit 8a68ea00a62e ("gpio: mockup: implement naming the lines")
Signed-off-by: Alexander Dahl
---
Documentation/admin-guide/kernel-parameters.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/admin-guide/kernel-para
Fixes: commit 0f98dd1b27d2 ("gpio/mockup: add virtual gpio device")
Signed-off-by: Alexander Dahl
---
Documentation/admin-guide/kernel-parameters.txt | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/admin-guide/kernel-parameters.txt
b/Documenta
Hello Hermes,
great to see your improved series. See below for my remarks.
On Fri, Mar 26, 2021 at 01:28:01PM +0800, Hermes Zhang wrote:
> From: Hermes Zhang
>
> Introduce a new multiple GPIOs LED driver. This LED will made of
> multiple GPIOs (up to 8) and will map different brightness to diff
Hei hei,
> Enrico Weigelt, metux IT consult hat am 18.03.2021 11:27
> geschrieben:
>
>
> On 15.03.21 11:48, Andy Shevchenko wrote:
>
> Hi,
>
> > I have a question, why we can't provide a GPIO driver which is already
> > in the kernel and, with use of the patch series I sent, to convert
> >
Hallo Hermes,
thanks for your effort.
Am Donnerstag, 11. März 2021, 14:04:08 CET schrieb Hermes Zhang:
> From: Hermes Zhang
>
> Introduce a new Dual GPIO LED driver. These two GPIOs LED will act as
> one LED as normal GPIO LED but give the possibility to change the
> intensity in four levels: O
Hello,
On Wed, Feb 17, 2021 at 12:02:47PM +0100, Enrico Weigelt, metux IT consult
wrote:
> On 16.02.21 14:30, Andreas Eberlein wrote:
> > The DMI_PRODUCT_NAME entry on current firmware of PC Engines APU1 changed
> > from "APU" to "apu1"
> >
> > This modification adds the missing DMI data and the
_LED;
> - leds[1].led_cdev.name = "amber:status",
> + leds[1].led_cdev.name = "amber:status";
>
> leds[2].ec_index = EC_GREEN_LED;
> - leds[2].led_cdev.name = "green:status",
> + leds[2].led_cdev.name = "green:status";
> leds[2].led_cdev.default_trigger = "default-on";
>
> for (i = 0; i < NLEDS; i++) {
Reviewed-by: Alexander Dahl
Greets
Alex
s/leds-pwm.yaml
Signed-off-by: Alexander Dahl
Acked-by: Rob Herring
---
Notes:
v7 -> v8:
* rebased on v5.10-rc1
* added Acked-by (Rob Herring)
v6 -> v7:
* added warning message to commit message (Krzysztof Kozlowski)
v6:
* added this patch to series
/build/linux/arch/arm/boot/dts/berlin2cd-google-chromecast.dt.yaml:
leds: 'red', 'white' do not match any of the regexes: '^led(-[0-9a-f]+)?$',
'pinctrl-[0-9]+'
From schema:
/home/alex/src/linux/leds/Documentation/devicetree/bindings/leds/leds
...@st-md-mailman.stormreply.com
Cc: linux-amlo...@lists.infradead.org
Cc: linux-m...@vger.kernel.org
Alexander Dahl (5):
dt-bindings: mfd: Fix schema warnings for pwm-leds
ARM: dts: berlin: Fix schema warnings for pwm-leds
ARM: dts: stm32: Fix schema warnings for pwm-leds
arm64: dts: meson
/arm/boot/dts/stm32mp157c-lxa-mc1.dt.yaml: led-rgb:
'led-blue', 'led-green', 'led-red' do not match any of the regexes:
'^led(-[0-9a-f]+)?$', 'pinctrl-[0-9]+'
From schema:
/home/alex/src/linux/leds/Documentation/devicetree/bindings
The node names for devices using the pwm-leds driver follow a certain
naming scheme (now). Parent node name is not enforced, but recommended
by DT project.
Signed-off-by: Alexander Dahl
Reviewed-by: Neil Armstrong
---
Notes:
v7 -> v8:
* rebased on v5.10-rc1
v6 -&
The node names for devices using the pwm-leds driver follow a certain
naming scheme (now). Parent node name is not enforced, but recommended
by DT project.
Signed-off-by: Alexander Dahl
---
Notes:
v7 -> v8:
* rebased on v5.10-rc1
v6 -> v7:
* added another expl
Hello Sebastian,
Am Dienstag, 27. August 2019, 12:55:42 CEST schrieb Sebastian Andrzej Siewior:
> I'm pleased to announce the v5.2.10-rt5 patch set.
>
> Changes since v5.2.10-rt4:
>
> - Take care of compile issue within the timer-atmel-tcb driver on
> AT91. Rep
We have a MFD driver compiled as module instantiating this driver. When
unloading that module, those LED devices are not removed, which produces
conflicts, when that module is inserted again.
Signed-off-by: Alexander Dahl
---
drivers/leds/leds-syscon.c | 2 +-
1 file changed, 1 insertion(+), 1
Hello Sebastian,
Am Dienstag, 27. August 2019, 15:22:01 CEST schrieb Sebastian Andrzej Siewior:
> of course, !SMP. What about this:
>
> diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c
> --- a/kernel/time/hrtimer.c
> +++ b/kernel/time/hrtimer.c
> @@ -934,7 +934,11 @@ void hrtimer_grab_e
Hello,
out of curiosity: The SAMA5D27-SOM1-EK board has a 24 MHz crystal, that is
also what /sys/kernel/debug/clk/clk_summary says and the board runs without
obvious problems. What is this change improving in real practice then?
Greets
Alex
Am Mittwoch, 11. September 2019, 06:39:20 CEST schri
Hello Gene,
Am Montag, 7. Oktober 2019, 15:16:04 CEST schrieb Gene Heskett:
> On Monday 07 October 2019 15:10:05 Gene Heskett wrote:
> > Unfortunately, this does not work for the pi3-4 family. When its all
> > pulled in and patched, there is no arch/arm/configs bcm2709_defconfig
> > or bcm2711_def
Hei hei,
just tried to compile this v5.2.9-rt3 for SAMA5D27-SOM1-EK1 based on
arch/arm/configs/sama5_defconfig and with running oldconfig and selecting
defaults, but that fails if CONFIG_ATMEL_TCB_CLKSRC_USE_SLOW_CLOCK is not set.
I think this is due to changes for Atmel TCLIB in v5.2 and the
exandre Belloni
Acked-by: Alexander Dahl
> ---
> arch/arm/configs/at91_dt_defconfig | 1 +
> arch/arm/configs/sama5_defconfig | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/arch/arm/configs/at91_dt_defconfig
> b/arch/arm/configs/at91_dt_defconfig index 63d09e6
This seems to have slipped in by accident when sorting the entries.
Fixes: ffbdd9172ee2f53020f763574b4cdad8d9760a4f
Signed-off-by: Alexander Dahl
---
Notes:
v1 -> v2:
* rebase onto v5.0-rc3 (was v4.20-rc6)
drivers/net/can/usb/Kconfig | 6 --
1 file changed, 6 deletions(-)
d
Hei hei,
tl;dr: is there a way to prevent an ethernet PHY to ever power down, preferred
with some dt configuration, not with a hack e.g. patching out suspend
functions?
With the bugfix 0da70f808029476001109b6cb076737bc04cea2e ("net: macb: do not
disable MDIO bus at open/close time", came with
eeded firmware files to package.
Cc: Christoph Schulz
Signed-off-by: Alexander Dahl
---
drivers/staging/rtl8188eu/os_dep/os_intfs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/rtl8188eu/os_dep/os_intfs.c
b/drivers/staging/rtl8188eu/os_dep/os_intfs.c
index 2c088af44c8b.
Converted with tmplcvt. Only some tiny things needed manual fixing.
Signed-off-by: Alexander Dahl
Cc: Hans-Jürgen Koch
Cc: Greg Kroah-Hartman
---
based on v4.10-rc4
---
Documentation/DocBook/uio-howto.tmpl | 1112
Documentation/driver-api/index.rst
Hei hei,
On Sat, Jan 28, 2017 at 11:13:20AM +0800, kbuild test robot wrote:
> All errors (new ones prefixed by >>):
>
> >> make[2]: *** No rule to make target 'Documentation/DocBook/uio-howto.xml',
> >> needed by 'Documentation/DocBook/uio-howto.aux.xml'.
>make[2]: Target 'htmldocs' not rema
Converted with tmplcvt. Only some tiny things needed manual fixing.
Signed-off-by: Alexander Dahl
Cc: Hans-Jürgen Koch
Cc: Greg Kroah-Hartman
---
v1 -> v2:
* removed uio-howto.xml from docbook makefile
* rebased on v4.10-rc5
Signed-off-by: Alexander Dahl
---
Documentation/DocB
Hei hei,
With
#define ATMEL_SMC_MODE_TDF(x) (((x) - 1) << 16)
from include/linux/mfd/syscon/atmel-smc.h you added this:
> + ret = of_property_read_u32(np, "atmel,smc-tdf-ns", &val);
> + if (!ret) {
> + required = true;
> + ncycles = DIV_ROUND_UP(val, c
Hei hei,
there's a typo in the subject you may want to fix in a v2:
watchodg → watchdog
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaro
That one made me laugh. :-)
Reviewed-by: Alexander Dahl
Am Dienstag, 9. Juni 2020, 17:49:29 CEST schrieb Flavio Suligoi:
> Fix typo: "Tigger" --> "Trigger"
>
> Signed-off-by: Flavio Suligoi
> ---
> drivers/leds/led-triggers.c | 2 +-
> 1 file changed
Hei hei,
On Mon, Oct 05, 2020 at 05:35:38PM +0200, ultracool...@tutanota.com wrote:
> Well, the major benefit I see is that it makes the driver slightly
> more readable. However I'm fine with whatever you guys decide.
>
> I'll attach the patch with the struct renaming removed just in case.
Note:
e license set now is
recommended by DT project.
Suggested-by: Jacek Anaszewski
Signed-off-by: Alexander Dahl
Reviewed-by: Krzysztof Kozlowski
Reviewed-by: Rob Herring
Cc: Peter Ujfalusi
Cc: Russell King
---
Notes:
NOTE: Due to license set/change this needs Acked-by or Signed-off-by from:
7;^led(-[0-9a-f]+)?$', 'pinctrl-[0-9]+'
From schema:
/home/alex/src/linux/leds/Documentation/devicetree/bindings/leds/leds-pwm.yaml
Signed-off-by: Alexander Dahl
---
Notes:
v6 -> v7:
* split up patch (one per sub arch)
* added actual warnings to commit
/build/linux/arch/arm/boot/dts/berlin2cd-google-chromecast.dt.yaml:
leds: 'red', 'white' do not match any of the regexes: '^led(-[0-9a-f]+)?$',
'pinctrl-[0-9]+'
From schema:
/home/alex/src/linux/leds/Documentation/devicetree/bindings/leds/leds
ch/arm/boot/dts/omap4-sdp.dt.yaml: pwmleds:
'charging', 'kpad' do not match any of the regexes: '^led(-[0-9a-f]+)?$',
'pinctrl-[0-9]+'
From schema:
/home/alex/src/linux/leds/Documentation/devicetree/bindings/leds/leds-pwm.yaml
DTC arch/arm/boot/
ux-o...@vger.kernel.org
Cc: linux-st...@st-md-mailman.stormreply.com
Cc: linux-amlo...@lists.infradead.org
Cc: linux-m...@vger.kernel.org
Alexander Dahl (12):
leds: pwm: Remove platform_data support
dt-bindings: leds: Convert pwm to yaml
dt-bindings: mfd: Fix schema warnings for pwm-leds
ARM: dts: at91
The node names for devices using the pwm-leds driver follow a certain
naming scheme (now). Parent node name is not enforced, but recommended
by DT project.
Signed-off-by: Alexander Dahl
---
Notes:
v6 -> v7:
* added another explaining sentence to commit message
ot match any of the regexes: '^led(-[0-9a-f]+)?$',
'pinctrl-[0-9]+'
From schema:
/home/alex/src/linux/leds/Documentation/devicetree/bindings/leds/leds-pwm.yaml
Signed-off-by: Alexander Dahl
---
Notes:
v6 -> v7:
* split up patch (one per sub arch)
The node names for devices using the pwm-leds driver follow a certain
naming scheme (now). Parent node name is not enforced, but recommended
by DT project.
Signed-off-by: Alexander Dahl
Reviewed-by: Neil Armstrong
---
Notes:
v6 -> v7:
* added Reviewed-by
* added anot
)?$', 'pinctrl-[0-9]+'
From schema:
/home/alex/src/linux/leds/Documentation/devicetree/bindings/leds/leds-pwm.yaml
(Warnings above are for armv7 only, armv5 would produce similar warnings.)
Signed-off-by: Alexander Dahl
---
Notes:
v6 -> v7:
* split up patch (one p
driver to switch over from 'devm_led_classdev_register()' to
'devm_led_classdev_register_ext()'.
Signed-off-by: Alexander Dahl
Cc: Denis Osterland-Heim
Reviewed-by: Marek Behún
---
Notes:
v6 -> v7:
* (no changes on this patch)
v5 -> v6:
* added Re
s/leds-pwm.yaml
Signed-off-by: Alexander Dahl
---
Notes:
v6 -> v7:
* added warning message to commit message (Krzysztof Kozlowski)
v6:
* added this patch to series
Documentation/devicetree/bindings/mfd/iqs62x.yaml | 5 +++--
1 file changed, 3 insertions(+), 2 deletio
Do it the simple way like for the other kizbox boards. This will allow
renaming the led controller node name later without breaking things.
Signed-off-by: Alexander Dahl
---
Notes:
v6 -> v7:
* (no changes on this patch)
v6:
* added this patch to series
arch/arm/b
/arm/boot/dts/stm32mp157c-lxa-mc1.dt.yaml: led-rgb:
'led-blue', 'led-green', 'led-red' do not match any of the regexes:
'^led(-[0-9a-f]+)?$', 'pinctrl-[0-9]+'
From schema:
/home/alex/src/linux/leds/Documentation/devicetree/bindings
Hello Jeff,
Am Dienstag, 6. Oktober 2020, 04:17:29 CEST schrieb Jeff LaBundy:
> Hi Alexander,
>
> On Mon, Oct 05, 2020 at 10:34:42PM +0200, Alexander Dahl wrote:
> > The node names for devices using the pwm-leds driver follow a certain
> > naming scheme (now). Parent node
Hello Pavel,
On Wed, Sep 30, 2020 at 07:24:41PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > +__attribute__((nonnull))
> > > >
> > > > static int led_pwm_add(struct device *dev, struct led_pwm_priv *priv,
> > > >
> > > >struct led_pwm *led, struct fwnode_handle
> > > >
Do it the simple way like for the other kizbox boards. This will allow
renaming the led controller node name later without breaking things.
Signed-off-by: Alexander Dahl
---
Notes:
v6:
* added this patch to series
arch/arm/boot/dts/at91-smartkiz.dts | 6 ++
1 file changed, 2
The node names for devices using the pwm-leds driver follow a certain
naming scheme (now).
Signed-off-by: Alexander Dahl
---
Notes:
v6:
* added this patch to series
Documentation/devicetree/bindings/mfd/iqs62x.yaml | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff
e to recommended one (patch 2/2)
- added Acked-by to both patches
v2:
- series rebased on v5.9-rc3
- added the dt-bindings update patch (2/2)
v1:
- based on v5.9-rc2
- backport on v5.4.59 tested and working
Alexander Dahl (7):
leds: pwm: Remove platform_data support
dt-bindings: leds: Convert pw
The node names for devices using the pwm-leds driver follow a certain
naming scheme (now).
Signed-off-by: Alexander Dahl
---
Notes:
v6:
* added this patch to series
arch/arm/boot/dts/at91-kizbox.dts | 10 +++
arch/arm/boot/dts/at91-kizbox2-common.dtsi| 8
Suggested-by: Jacek Anaszewski
Signed-off-by: Alexander Dahl
Cc: Peter Ujfalusi
---
Notes:
v5 -> v6:
* removed pwm nodes from example (Rob)
* renamed led-controller node in example (Rob)
v4 -> v5:
* updated based on feedback by Rob Herring
* removed
The node names for devices using the pwm-leds driver follow a certain
naming scheme (now).
Signed-off-by: Alexander Dahl
---
Notes:
v6:
* added this patch to series
arch/mips/boot/dts/img/pistachio_marduk.dts | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a
driver to switch over from 'devm_led_classdev_register()' to
'devm_led_classdev_register_ext()'.
Signed-off-by: Alexander Dahl
Cc: Denis Osterland-Heim
Reviewed-by: Marek Behún
---
Notes:
v5 -> v6:
* added Reviewed-by from Marek
* minimal commit message rew
The node names for devices using the pwm-leds driver follow a certain
naming scheme (now).
Signed-off-by: Alexander Dahl
---
Notes:
v6:
* added this patch to series
.../arm64/boot/dts/amlogic/meson-gxl-s905x-khadas-vim.dts | 4 ++--
arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2
Hello Krzysztof,
Am Freitag, 2. Oktober 2020, 11:12:50 CEST schrieb Krzysztof Kozlowski:
> On Thu, 1 Oct 2020 at 01:53, Alexander Dahl wrote:
> > The node names for devices using the pwm-leds driver follow a certain
> > naming scheme (now).
> >
> > Si
Hello Krzysztof,
Am Freitag, 2. Oktober 2020, 11:21:10 CEST schrieb Krzysztof Kozlowski:
> On Thu, 1 Oct 2020 at 01:51, Alexander Dahl wrote:
> > The node names for devices using the pwm-leds driver follow a certain
> > naming scheme (now).
>
> What warning? Please post t
Hei hei,
Am Freitag, 2. Oktober 2020, 11:31:09 CEST schrieb Krzysztof Kozlowski:
> On Thu, 1 Oct 2020 at 01:52, Alexander Dahl wrote:
> > The example was adapted in the following ways:
> >
> > - make use of the now supported 'function' and 'color' pro
From: Alexander Dahl
If LEDs are configured through device tree and the property 'label' is
omitted, the label is supposed to be generated from the properties
'function' and 'color' if present. While this works fine for e.g. the
'leds-gpio' driver, it did
atch any of the regexes:
> > '^led(-[0-9a-f]+)?$', 'pinctrl-[0-9]+'>
> > From schema:
> > /home/alex/src/linux/leds/Documentation/devicetree/bindings/leds/
> > leds-pwm.yaml>
> > Signed-off-by: Alexander Dahl
>
&g
Hello Pavel,
Am Samstag, 19. September 2020, 11:44:18 CEST schrieb Pavel Machek:
> > Since commit 141f15c66d94 ("leds: pwm: remove header") that platform
> > interface is not usable from outside and there seems to be no in tree
> > user anymore. All in-tree users of the leds-pwm driver seem to us
Hello Rob,
Am Dienstag, 22. September 2020, 17:42:58 CEST schrieb Rob Herring:
> On Sat, 19 Sep 2020 07:31:45 +0200, Alexander Dahl wrote:
> > The example was adapted slightly to make use of the 'function' and
> > 'color' properties. License discussed with the
Hei hei,
Am Dienstag, 22. September 2020, 17:57:47 CEST schrieb Rob Herring:
> Use generic node names:
>
> led-controller {
>
> > +compatible = "pwm-leds";
> > +
> > +led-1 {
> > +label = "omap4::keypad";
> > +pwms = <&twl_pwm 0 7812500>;
> > +
Enable emulation on 32bit too")
Fixes: https://web.nettworks.org/bugs/browse/FFL-2560
Fixes: https://unix.stackexchange.com/q/520065/50007
Reported-by: Alan Jenkins
Suggested-by: Robin Murphy
Signed-off-by: Alexander Dahl
Cc: sta...@vger.kernel.org
---
Notes:
v3:
- rewritten commi
Hei hei,
I would like to kindly ask about the status of this patch.
On Wed, Apr 15, 2020 at 04:35:21PM +0200, Alexander Dahl wrote:
> now after v5.7-rc1 is out, I would kindly ask, if anyone had time to
> review this one line patch? Is anything wrong with that fix?
Did it maybe not rea
Hello Jacek,
Am Donnerstag, 27. August 2020, 23:28:45 CEST schrieb Jacek Anaszewski:
> On 8/26/20 11:37 AM, Alexander Dahl wrote:
> > From: Alexander Dahl
> >
> > If LEDs are configured through device tree and the property 'label' is
> > omitted, the label
Hi Jacek,
Am Dienstag, 1. September 2020, 23:08:09 CEST schrieb Jacek Anaszewski:
> Hi Alexander,
>
> Thanks for the v2.
>
> On 8/31/20 11:02 PM, Alexander Dahl wrote:
> > Hei hei,
> >
> > for leds-gpio you can use the properties 'function' and
;
pwms = <&pwm0 2 1000 0>;
max-brightness = <127>;
linux,default-trigger = "heartbeat";
panic-indicator;
};
};
Signed-off-by: Alexander Dahl
Acked-by: Jacek Anas
5.9-rc2
- backport on v5.4.59 tested and working
Greets
Alex
Alexander Dahl (2):
leds: pwm: Allow automatic labels for DT based devices
dt-bindings: leds: Convert pwm to yaml
.../devicetree/bindings/leds/leds-pwm.txt | 50 ---
.../devicetree/bindings/leds/leds-pwm.yaml| 85
The example was adapted slightly to make use of the 'function' and
'color' properties.
Suggested-by: Jacek Anaszewski
Signed-off-by: Alexander Dahl
Acked-by: Jacek Anaszewski
---
Notes:
v2 -> v3:
* change license identifier to recommended one
* added Ac
Hello Jacek,
Am Freitag, 28. August 2020, 22:43:02 CEST schrieb Jacek Anaszewski:
> On 8/28/20 9:00 AM, Alexander Dahl wrote:
> > Am Donnerstag, 27. August 2020, 23:28:45 CEST schrieb Jacek Anaszewski:
> >> This part looks good, but corresponding update of
> >> Docume
The example was adapted slightly to make use of the 'function' and
'color' properties.
Suggested-by: Jacek Anaszewski
Signed-off-by: Alexander Dahl
---
.../devicetree/bindings/leds/leds-pwm.txt | 50 ---
.../devicetree/bindings/leds/leds-pwm.yaml| 85 ++
leds-pwm' driver.
This series fixes the driver and takes the opportunity to update the
dt-bindings accordingly.
v1: based on v5.9-rc2, backport on v5.4.59 tested and working
v2: based on v5.9-rc3, added the dt-bindings update patch
Greets
Alex
Alexander Dahl (2):
leds: pwm: Allow au
;
pwms = <&pwm0 2 1000 0>;
max-brightness = <127>;
linux,default-trigger = "heartbeat";
panic-indicator;
};
};
Signed-off-by: Alexander Dahl
---
drivers/leds/leds
that line from leds-gpio.yaml, can be changed in a
v3 of course.
Greets
Alex
On Mon, Aug 31, 2020 at 11:02:31PM +0200, Alexander Dahl wrote:
> The example was adapted slightly to make use of the 'function' and
> 'color' properties.
>
> Suggested-by: Jacek Anasze
Hello Ahmad,
thanks for your feedback, comments below.
On Tue, Oct 27, 2020 at 08:03:40AM +0100, Ahmad Fatoum wrote:
> Hello Alexander,
>
> On 10/5/20 10:34 PM, Alexander Dahl wrote:
> > The node names for devices using the pwm-leds driver follow a certain
> > naming schem
Hello Ahmad,
Am Dienstag, 27. Oktober 2020, 11:58:10 CET schrieb Ahmad Fatoum:
> Hello,
>
> On 10/27/20 11:05 AM, Alexander Dahl wrote:
> > Hello Ahmad,
> >
> > thanks for your feedback, comments below.
> >
> >>> - led-rgb {
> >>> + l
05, 2020 at 10:34:41PM +0200, Alexander Dahl wrote:
> The example was adapted in the following ways:
>
> - make use of the now supported 'function' and 'color' properties
> - remove pwm nodes, those are documented elsewhere
> - align node names to new dt
Hei hei,
On Tue, Oct 27, 2020 at 11:58:10AM +0100, Ahmad Fatoum wrote:
> Hello,
>
> On 10/27/20 11:05 AM, Alexander Dahl wrote:
> > Hello Ahmad,
> >
> > thanks for your feedback, comments below.
> >
>
> >>> - led-rgb {
> >>>
+ * @section: pointer where the section id will be stored
> * @oobregion: OOB region information
> *
> * Works like mtd_ooblayout_find_region() except it searches for a specific
> ECC
Reviewed-by: Alexander Dahl
Greets
Alex
Hello Alex,
On Mon, Nov 09, 2020 at 12:02:18PM +0100, Alexandre Torgue wrote:
> Hi Alex
>
> On 10/31/20 2:54 PM, Alexander Dahl wrote:
> > Hei hei,
> >
> > On Tue, Oct 27, 2020 at 11:58:10AM +0100, Ahmad Fatoum wrote:
> > > Hello,
> > >
>
te the
> > > > dt-bindings accordingly.
> > > >
> > > > v1: based on v5.9-rc2, backport on v5.4.59 tested and working
> > > >
> > > > v2: based on v5.9-rc3, added the dt-bindings update patch
> > > >
> > > > Greets
1 - 100 of 124 matches
Mail list logo
