ed as well.
Signed-off-by: Romain Izard
---
drivers/clocksource/tcb_clksrc.c | 16 +---
1 file changed, 1 insertion(+), 15 deletions(-)
diff --git a/drivers/clocksource/tcb_clksrc.c b/drivers/clocksource/tcb_clksrc.c
index 745844ee973e..d4ca9962a759 100644
--- a/drivers/clocksource/tc
the connected device.
Implement a custom 'set_power' function for this specific hardware, that
configures the voltage in the register in all cases.
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
drivers/mmc/host/sdhci-of-at91.c | 19 +++
1 file changed, 19 inse
the connected device.
Implement a custom 'set_power' function for this specific hardware, that
configures the voltage in the register in all cases.
Signed-off-by: Romain Izard
---
drivers/mmc/host/sdhci-of-at91.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers
ithout any legacy gadget driver.
Mark the choice for legacy gadget drivers as optional.
Fixes: bc49d1d17dcf ("usb: gadget: don't couple configfs to legacy gadgets")
Cc: <sta...@vger.kernel.org> # 4.9+
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
changes in v2:
-
ithout any legacy gadget driver.
Mark the choice for legacy gadget drivers as optional.
Fixes: bc49d1d17dcf ("usb: gadget: don't couple configfs to legacy gadgets")
Cc: # 4.9+
Signed-off-by: Romain Izard
---
changes in v2:
- Reword description
drivers/usb/gadget/Kconfig | 11 +-
2017-03-06 12:28 GMT+01:00 Romain Izard <romain.izard@gmail.com>:
>
> While looking for another issue, I tried Linux 4.11-rc1 on a SAMA5D2 Xplained
> board. The boot log contains the following warning:
>
> [0.10] [ cut here ]
> [0.100
2017-03-06 12:28 GMT+01:00 Romain Izard :
>
> While looking for another issue, I tried Linux 4.11-rc1 on a SAMA5D2 Xplained
> board. The boot log contains the following warning:
>
> [0.10] [ cut here ]
> [0.10] WARNING: CPU: 0 PID: 1 a
are enabled. This warning
does not prevent the tcb clock from being used.
--
Romain Izard
are enabled. This warning
does not prevent the tcb clock from being used.
--
Romain Izard
RM: at91/dt: sama5d2: Use new compatible for ohci node")
Signed-off-by: Romain Izard <romain.izard@gmail.com>
cc: <sta...@vger.kernel.org>
---
arch/arm/boot/dts/sama5d2.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/sama5d2.d
RM: at91/dt: sama5d2: Use new compatible for ohci node")
Signed-off-by: Romain Izard
cc:
---
arch/arm/boot/dts/sama5d2.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/sama5d2.dtsi b/arch/arm/boot/dts/sama5d2.dtsi
index ceb9783ff7e1..ff7eae833a6d
When building without modules, it makes sense to configure the kernel to
only use configfs for USB Gadget drivers.
Mark the choice for legacy gadget drivers as optional.
Signed-off-by: Romain Izard <romain.izard@gmail.com>
cc: <sta...@vger.kernel.org> # 4.9
---
drivers/usb/ga
When building without modules, it makes sense to configure the kernel to
only use configfs for USB Gadget drivers.
Mark the choice for legacy gadget drivers as optional.
Signed-off-by: Romain Izard
cc: # 4.9
---
drivers/usb/gadget/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
.
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
drivers/tty/serial/atmel_serial.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/tty/serial/atmel_serial.c
b/drivers/tty/serial/atmel_serial.c
index fabbe76203bb..6684456dca9e 100644
--- a/drive
.
Signed-off-by: Romain Izard
---
drivers/tty/serial/atmel_serial.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/tty/serial/atmel_serial.c
b/drivers/tty/serial/atmel_serial.c
index fabbe76203bb..6684456dca9e 100644
--- a/drivers/tty/serial/atmel_serial.c
+++ b
2017-02-06 16:14 GMT+01:00 Romain Izard <romain.izard@gmail.com>:
>
> For verification, I checked the SAMA5D2 datasheet, and (in rev. D) the
> warning is still present in §41.7.1.2.
It looks like I got confused with between the versions. In fact, the warning
disappeared between
2017-02-06 16:14 GMT+01:00 Romain Izard :
>
> For verification, I checked the SAMA5D2 datasheet, and (in rev. D) the
> warning is still present in §41.7.1.2.
It looks like I got confused with between the versions. In fact, the warning
disappeared between versions C & D, and the la
2017-02-06 14:42 GMT+01:00 Ludovic Desroches <ludovic.desroc...@microchip.com>:
> Hello Romain,
>
> On Mon, Feb 06, 2017 at 12:56:42PM +0100, Romain Izard wrote:
>>
>> Unfortunately, I know that this will work on SAMA5D2, but this driver is
>> used for many
2017-02-06 14:42 GMT+01:00 Ludovic Desroches :
> Hello Romain,
>
> On Mon, Feb 06, 2017 at 12:56:42PM +0100, Romain Izard wrote:
>>
>> Unfortunately, I know that this will work on SAMA5D2, but this driver is
>> used for many other Atmel chips. I do not know if th
Should I just
propose this as a patch, or is it necessary to add a limitation for
supported devices only ?
Best regards,
--
Romain Izard
Should I just
propose this as a patch, or is it necessary to add a limitation for
supported devices only ?
Best regards,
--
Romain Izard
0x18/0x124)
[] (kernel_init) from [] (ret_from_fork+0x14/0x20)
---[ end trace 3d13186881cd5c91 ]---
"sched_clock_register" expects to be called with interrupts disabled, but
the tcb_clksrc initialization is called as an arch_initcall, which runs too
late in the boot sequence.
Best regards,
--
Romain Izard
race 3d13186881cd5c91 ]---
"sched_clock_register" expects to be called with interrupts disabled, but
the tcb_clksrc initialization is called as an arch_initcall, which runs too
late in the boot sequence.
Best regards,
--
Romain Izard
2016-08-29 11:07 GMT+02:00 Romain Izard <romain.izard@gmail.com>:
> Disabling USB gadget functions configured through configfs is something
> that can happen in normal use cases. Keep the existing log for this type
> of event, but only as debug, not as an error.
>
> Signed
2016-08-29 11:07 GMT+02:00 Romain Izard :
> Disabling USB gadget functions configured through configfs is something
> that can happen in normal use cases. Keep the existing log for this type
> of event, but only as debug, not as an error.
>
> Signed-off-by: Romain Izard
> ---
&
Disabling USB gadget functions configured through configfs is something
that can happen in normal use cases. Keep the existing log for this type
of event, but only as debug, not as an error.
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
v1 -> v2:
- use dev_dbg instead of
Disabling USB gadget functions configured through configfs is something
that can happen in normal use cases. Keep the existing log for this type
of event, but only as debug, not as an error.
Signed-off-by: Romain Izard
---
v1 -> v2:
- use dev_dbg instead of dev_info
drivers/usb/gad
2016-08-29 10:13 GMT+02:00 Felipe Balbi <ba...@kernel.org>:
>
> Hi,
>
> Romain Izard <romain.izard@gmail.com> writes:
>> Disabling USB gadget functions configured through configfs is something
>> that can happen in normal use cases. Keep the existing log
2016-08-29 10:13 GMT+02:00 Felipe Balbi :
>
> Hi,
>
> Romain Izard writes:
>> Disabling USB gadget functions configured through configfs is something
>> that can happen in normal use cases. Keep the existing log for this type
>> of event, but only as information, not
2016-07-26 18:21 GMT+02:00 Romain Izard <romain.izard@gmail.com>:
> Disabling USB gadget functions configured through configfs is something
> that can happen in normal use cases. Keep the existing log for this type
> of event, but only as information, not as an error.
>
>
2016-07-26 18:21 GMT+02:00 Romain Izard :
> Disabling USB gadget functions configured through configfs is something
> that can happen in normal use cases. Keep the existing log for this type
> of event, but only as information, not as an error.
>
> Signed-off-by: Romain Izard
>
Disabling USB gadget functions configured through configfs is something
that can happen in normal use cases. Keep the existing log for this type
of event, but only as information, not as an error.
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
drivers/usb/gadget/configfs
Disabling USB gadget functions configured through configfs is something
that can happen in normal use cases. Keep the existing log for this type
of event, but only as information, not as an error.
Signed-off-by: Romain Izard
---
drivers/usb/gadget/configfs.c | 5 +++--
1 file changed, 3
freeze the kernel version to be used
on my board as soon as possible.
Best regards,
--
Romain Izard
oard as soon as possible.
Best regards,
--
Romain Izard
ives the proper ready/busy bit information. The NAND flash
> driver will be updated to remove the support for this different
> implementation.
>
> Signed-off-by: Wenyou Yang <wenyou.y...@atmel.com>
> [nicolas.fe...@atmel.com: change commit message]
> Signed-off-by: Nicolas F
> driver will be updated to remove the support for this different
> implementation.
>
> Signed-off-by: Wenyou Yang
> [nicolas.fe...@atmel.com: change commit message]
> Signed-off-by: Nicolas Ferre
Acked-by: Romain Izard
> ---
> Wenyou, Romain,
>
> I plan to send
MA5D4 & SAMA5D2 have a newer
revision, which supports multiple writes to the MR register.
Are you sure about your datasheet? I have this in the latest version
found on Atmel's site.
> Atmel-11238B-ATARM-SAMA5D4-Datasheet_24-Aug-15
> Section 18.5.2
>
> Note: Write access to this register has no effect if the LOCKMR
> command is issued in WDT_CR (unlocked on hardware reset).
> Note: The WDT_MR register values must not be modified within three slow
> clock periods following a restart of the watchdog performed by
> a write access in WDT_CR. Any modification will cause the watchdog
> to trigger an end of period earlier than expected.
>
It matches the comments from Wenyou when he committed the sama5d4
watchdog driver to replace the existing at91sam9 watchdog.
Best regards,
--
Romain Izard
h supports multiple writes to the MR register.
Are you sure about your datasheet? I have this in the latest version
found on Atmel's site.
> Atmel-11238B-ATARM-SAMA5D4-Datasheet_24-Aug-15
> Section 18.5.2
>
> Note: Write access to this register has no effect if the LOCKMR
> command is issued in WDT_CR (unlocked on hardware reset).
> Note: The WDT_MR register values must not be modified within three slow
> clock periods following a restart of the watchdog performed by
> a write access in WDT_CR. Any modification will cause the watchdog
> to trigger an end of period earlier than expected.
>
It matches the comments from Wenyou when he committed the sama5d4
watchdog driver to replace the existing at91sam9 watchdog.
Best regards,
--
Romain Izard
2016-03-04 14:09 GMT+01:00 Guenter Roeck <li...@roeck-us.net>:
> On 03/04/2016 01:06 AM, Romain Izard wrote:
>> 2016-03-04 6:23 GMT+01:00 Guenter Roeck <li...@roeck-us.net>:
>>> On 03/03/2016 05:35 PM, Yang, Wenyou wrote:
>>>> On 2016/3/3 18:29, Romai
2016-03-04 14:09 GMT+01:00 Guenter Roeck :
> On 03/04/2016 01:06 AM, Romain Izard wrote:
>> 2016-03-04 6:23 GMT+01:00 Guenter Roeck :
>>> On 03/03/2016 05:35 PM, Yang, Wenyou wrote:
>>>> On 2016/3/3 18:29, Romain Izard wrote:
>>>>>
>>>>>
Hi Wenyou, Guenter,
2016-03-04 6:23 GMT+01:00 Guenter Roeck <li...@roeck-us.net>:
> On 03/03/2016 05:35 PM, Yang, Wenyou wrote:
>> On 2016/3/3 18:29, Romain Izard wrote:
>>>
>>> If the internal counter is not refreshed when the watchdog is
>>> started for
Hi Wenyou, Guenter,
2016-03-04 6:23 GMT+01:00 Guenter Roeck :
> On 03/03/2016 05:35 PM, Yang, Wenyou wrote:
>> On 2016/3/3 18:29, Romain Izard wrote:
>>>
>>> If the internal counter is not refreshed when the watchdog is
>>> started for the first time, th
Hi Guenter,
2016-03-03 13:10 GMT+01:00 Guenter Roeck <li...@roeck-us.net>:
> On 03/03/2016 02:29 AM, Romain Izard wrote:
>>
>> If the internal counter is not refreshed when the watchdog is started
>> for the first time, the watchdog will trigger very rapidly. For
>&g
Hi Guenter,
2016-03-03 13:10 GMT+01:00 Guenter Roeck :
> On 03/03/2016 02:29 AM, Romain Izard wrote:
>>
>> If the internal counter is not refreshed when the watchdog is started
>> for the first time, the watchdog will trigger very rapidly. For
>> example, opening /d
the timer on opening the watchdog device.
Command: "while sleep 5; do echo 1; done > /dev/watchdog"
Before: system reset
After: the watchdog runs correctly
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
drivers/watchdog/sama5d4_wdt.c | 3 +++
1 file changed, 3
the timer on opening the watchdog device.
Command: "while sleep 5; do echo 1; done > /dev/watchdog"
Before: system reset
After: the watchdog runs correctly
Signed-off-by: Romain Izard
---
drivers/watchdog/sama5d4_wdt.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/dri
t;clk" field on removal, triggering an oops when
a device was bound again after being unbound.
Acked-by: Nicolas Ferre <nicolas.fe...@atmel.com>
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
Changelog:
v2: Add the rationale for keeping the "remove" function
t;clk" field on removal, triggering an oops when
a device was bound again after being unbound.
Acked-by: Nicolas Ferre
Signed-off-by: Romain Izard
---
Changelog:
v2: Add the rationale for keeping the "remove" function as a comment.
v3: Do not cleanup the spaces in the driver initi
2016-02-25 17:09 GMT+01:00 Greg Kroah-Hartman
<gre...@linuxfoundation.org>:
> On Thu, Feb 25, 2016 at 11:01:07AM +0100, Nicolas Ferre wrote:
>> Le 25/02/2016 10:23, Romain Izard a écrit :
>> > In commit c39dfebc7798956fd2140ae6321786ff35da30c3, the modular
>> &
2016-02-25 17:09 GMT+01:00 Greg Kroah-Hartman
:
> On Thu, Feb 25, 2016 at 11:01:07AM +0100, Nicolas Ferre wrote:
>> Le 25/02/2016 10:23, Romain Izard a écrit :
>> > In commit c39dfebc7798956fd2140ae6321786ff35da30c3, the modular
>> > support code for atmel_serial was re
t;clk" field on removal, triggering an oops when
a device was bound again after being unbound.
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
Changelog:
v2: Add the rationale for keeping the "remove" function as a comment.
drivers/tty/
t;clk" field on removal, triggering an oops when
a device was bound again after being unbound.
Signed-off-by: Romain Izard
---
Changelog:
v2: Add the rationale for keeping the "remove" function as a comment.
drivers/tty/serial/atmel_serial.c | 39 +++
2016-02-24 17:20 GMT+01:00 Sylvain Rochet <sylvain.roc...@finsecur.com>:
> Hi,
>
> On Wed, Feb 24, 2016 at 05:04:42PM +0100, Romain Izard wrote:
>> Register the counter of the Periodic Interval Timer as a possible
>> source for sched_clock. Keep the timer running even i
2016-02-24 17:20 GMT+01:00 Sylvain Rochet :
> Hi,
>
> On Wed, Feb 24, 2016 at 05:04:42PM +0100, Romain Izard wrote:
>> Register the counter of the Periodic Interval Timer as a possible
>> source for sched_clock. Keep the timer running even if the related
>
in the
initialization sequence.
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
Changelog:
v2:
- Keep the tick counter updated when the clocksource is disabled
- Ensure that sched_clock is a 64 bit counter
drivers/clocksource/timer-atmel-pit.c | 31 ---
in the
initialization sequence.
Signed-off-by: Romain Izard
---
Changelog:
v2:
- Keep the tick counter updated when the clocksource is disabled
- Ensure that sched_clock is a 64 bit counter
drivers/clocksource/timer-atmel-pit.c | 31 ---
1 file changed, 16 insertions(+), 15
2016-02-24 15:53 GMT+01:00 Nicolas Ferre <nicolas.fe...@atmel.com>:
> Le 23/02/2016 17:59, Romain Izard a écrit :
>> In commit c39dfebc7798956fd2140ae6321786ff35da30c3, the modular support
>> code for atmel_serial was removed, as the driver cannot be built as a
>>
2016-02-24 15:53 GMT+01:00 Nicolas Ferre :
> Le 23/02/2016 17:59, Romain Izard a écrit :
>> In commit c39dfebc7798956fd2140ae6321786ff35da30c3, the modular support
>> code for atmel_serial was removed, as the driver cannot be built as a
>> module. Because no use case was
2016-02-23 20:18 GMT+01:00 Paul Gortmaker <paul.gortma...@windriver.com>:
> [[PATCH] tty/serial: at91: restore dynamic driver binding] On 23/02/2016 (Tue
> 17:59) Romain Izard wrote:
>
>> In commit c39dfebc7798956fd2140ae6321786ff35da30c3, the modular support
>> code f
2016-02-23 20:18 GMT+01:00 Paul Gortmaker :
> [[PATCH] tty/serial: at91: restore dynamic driver binding] On 23/02/2016 (Tue
> 17:59) Romain Izard wrote:
>
>> In commit c39dfebc7798956fd2140ae6321786ff35da30c3, the modular support
>> code for atmel_serial was removed, as the d
t;clk" field on removal, triggering an oops when
a device was bound again after being unbound.
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
drivers/tty/serial/atmel_serial.c | 30 +++---
1 file changed, 27 insertions(+), 3 deletions(-)
diff --git a/dr
t;clk" field on removal, triggering an oops when
a device was bound again after being unbound.
Signed-off-by: Romain Izard
---
drivers/tty/serial/atmel_serial.c | 30 +++---
1 file changed, 27 insertions(+), 3 deletions(-)
diff --git a/drivers/tty/serial/atmel_serial.c
2016-02-23 16:21 GMT+01:00 Fabio Estevam <feste...@gmail.com>:
> On Tue, Feb 23, 2016 at 11:54 AM, Romain Izard
> <romain.izard@gmail.com> wrote:
>> As the mctrl_gpio driver can be built as a module, it needs to have its
>> license specified with MODULE_LICENS
2016-02-23 16:21 GMT+01:00 Fabio Estevam :
> On Tue, Feb 23, 2016 at 11:54 AM, Romain Izard
> wrote:
>> As the mctrl_gpio driver can be built as a module, it needs to have its
>> license specified with MODULE_LICENSE. Otherwise, it cannot access
>> required
As the mctrl_gpio driver can be built as a module, it needs to have its
license specified with MODULE_LICENSE. Otherwise, it cannot access
required symbols exported through EXPORT_SYMBOL_GPL.
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
drivers/tty/serial/serial_mctrl_gpio
As the mctrl_gpio driver can be built as a module, it needs to have its
license specified with MODULE_LICENSE. Otherwise, it cannot access
required symbols exported through EXPORT_SYMBOL_GPL.
Signed-off-by: Romain Izard
---
drivers/tty/serial/serial_mctrl_gpio.c | 3 +++
1 file changed, 3
2016-02-18 21:07 GMT+01:00 Linus Walleij <linus.wall...@linaro.org>:
> On Thu, Feb 18, 2016 at 11:37 AM, Romain Izard
> <romain.izard@gmail.com> wrote:
>
>> The current code for device probing tries to map the default pinctrl
>> state (in pinctrl_bind_pin
2016-02-18 21:07 GMT+01:00 Linus Walleij :
> On Thu, Feb 18, 2016 at 11:37 AM, Romain Izard
> wrote:
>
>> The current code for device probing tries to map the default pinctrl
>> state (in pinctrl_bind_pins), but is returning 0 or -EDEFER. If there
>> is an othe
probed successfully
as conflicting pin sets are not recognized as an issue, which means
that my use case does not work.
Is the direction I'm taking something correct ?
Best regards,
--
Romain Izard
probed successfully
as conflicting pin sets are not recognized as an issue, which means
that my use case does not work.
Is the direction I'm taking something correct ?
Best regards,
--
Romain Izard
to require valid mappings. Additionally, the pin is not protected from
being remapped later by an other driver.
There is an external 1kΩ pull-up to 3.3V, so no bias is required on
the Ethernet PHY's interrupt line.
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
arch/arm/boot/dt
to require valid mappings. Additionally, the pin is not protected from
being remapped later by an other driver.
There is an external 1kΩ pull-up to 3.3V, so no bias is required on
the Ethernet PHY's interrupt line.
Signed-off-by: Romain Izard
---
arch/arm/boot/dts/at91-sama5d2_xplained.dts | 1 +
1 file
Register the counter of the Periodic Interval Timer as a possible source
for sched_clock. This provides a better precision than the jiffies-based
default.
Signed-off-by: Romain Izard
---
To reduce overhead and cache consumption, sched_clock_register does not
take a void* argument
Register the counter of the Periodic Interval Timer as a possible source
for sched_clock. This provides a better precision than the jiffies-based
default.
Signed-off-by: Romain Izard <romain.izard@gmail.com>
---
To reduce overhead and cache consumption, sched_clock_register does no
2014-03-06 18:34 GMT+01:00 Steven Rostedt :
> Ingo,
>
> You want to push this to Linus?
>
> Reviewed-by: Steven Rostedt
>
> -- Steve
>
>
> On Tue, 4 Mar 2014 10:09:39 +0100
> Romain Izard wrote:
>
>> The replacement of the 'count' variable by two vari
2014-03-06 18:34 GMT+01:00 Steven Rostedt rost...@goodmis.org:
Ingo,
You want to push this to Linus?
Reviewed-by: Steven Rostedt rost...@goodmis.org
-- Steve
On Tue, 4 Mar 2014 10:09:39 +0100
Romain Izard romain.izard@gmail.com wrote:
The replacement of the 'count' variable
code, and the refcount in the traces was not usable as a result.
Use 'count = incs - decs' to compute the user count.
Signed-off-by: Romain Izard
---
include/trace/events/module.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/trace/events/module.h b/include/trace
code, and the refcount in the traces was not usable as a result.
Use 'count = incs - decs' to compute the user count.
Signed-off-by: Romain Izard romain.izard@gmail.com
---
include/trace/events/module.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/trace/events
code, and the refcount in the traces was not usable as a result.
Use 'count = incs - decs' to compute the user count.
Signed-off-by: Romain Izard
---
include/trace/events/module.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/trace/events/module.h b/include/trace
code, and the refcount in the traces was not usable as a result.
Use 'count = incs - decs' to compute the user count.
Signed-off-by: Romain Izard romain.izard@gmail.com
---
include/trace/events/module.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/trace
v);
> - if (IS_ERR(pinctrl))
> - dev_warn(>dev, "no pins associated\n");
> -
> /*
> * Some non-DT platforms do not pass a clock, and the clock
>* frequency is passed through platform_data. On DT platforms,
Best regards,
--
Romai
-dev);
- if (IS_ERR(pinctrl))
- dev_warn(pdev-dev, no pins associated\n);
-
/*
* Some non-DT platforms do not pass a clock, and the clock
* frequency is passed through platform_data. On DT platforms,
Best regards,
--
Romain Izard
--
To unsubscribe from
201 - 283 of 283 matches
Mail list logo
