Enable pinctrl for pwm-tiehrpwm
Signed-off-by: Philip, Avinash avinashphi...@ti.com
---
:100644 100644 fba7f9b... 07911e6... M drivers/pwm/pwm-tiehrpwm.c
drivers/pwm/pwm-tiehrpwm.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/drivers/pwm/pwm-tiehrpwm.c
Some platforms (like AM33XX) requires clock gating from control module
explicitly for TBCLK. Enabling of this clock required for the
functioning of the time base sub module in EHRPWM module. So adding
optional TBCLK handling if DT node populated with tbclkgating. This
helps the driver can coexist
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor Grinberg wrote:
CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
Make OMAP2+ timer code independant from the CONFIG_OMAP_32K_TIMER
setting.
To remove the dependancy, several conversions/additions
PWM output from ecap0 uses as backlight source. Also adds low threshold
value to have a uniform divisions in brightness-levels scales.
Signed-off-by: Philip, Avinash avinashphi...@ti.com
---
:100644 100644 185d632... 9857050... M arch/arm/boot/dts/am335x-evm.dts
arch/arm/boot/dts/am335x-evm.dts
Add PWMSS device tree nodes in relation with ECAP EHRPWM DT nodes to
AM33XX SoC family. Also populates device tree nodes for ECAP EHRPWM by
adding necessary properties like pwm-cells, base reg set disabled as
status.
Signed-off-by: Philip, Avinash avinashphi...@ti.com
---
:100644 100644
On Wed, Nov 7, 2012 at 6:54 PM, Balaji T K balaj...@ti.com wrote:
On Tuesday 06 November 2012 10:22 PM, Venkatraman S wrote:
Define the most frequently used bitmasks of the Interrupt Enable /
Interrupt Status register with consistent naming ( with _EN suffix).
Use meaningful concatenation of
+ Peter
Hi Stephen,
On 11/7/2012 6:25 PM, Stephen Warren wrote:
On 11/07/2012 03:19 AM, Benoit Cousson wrote:
Hi Panto,
On 11/07/2012 09:13 AM, Pantelis Antoniou wrote:
Hi Grant
On Nov 6, 2012, at 9:45 PM, Grant Likely wrote:
On Tue, Nov 6, 2012 at 7:34 PM, Pantelis Antoniou
On Thu, Nov 8, 2012 at 9:14 AM, Péter Ujfalusi peter.ujfal...@ti.com wrote:
On 11/07/2012 06:50 PM, Grazvydas Ignotas wrote:
+ if (pwm-hwpwm) {
+ /* PWM 1 */
+ mask = TWL4030_GPIO7_VIBRASYNC_PWM1_MASK;
+ bits = TWL4030_GPIO7_VIBRASYNC_PWM1_PWM1;
On Thu, Nov 8, 2012 at 9:34 AM, Péter Ujfalusi peter.ujfal...@ti.com wrote:
On 11/07/2012 07:12 PM, Grazvydas Ignotas wrote:
+static int twl4030_pwmled_config(struct pwm_chip *chip, struct pwm_device
*pwm,
+ int duty_ns, int period_ns)
+{
+ int duty_cycle =
Hi Tony,
On Thu, Nov 08, 2012 at 03:10:14, Tony Lindgren wrote:
* Mohammed, Afzal af...@ti.com [121107 01:00]:
And Daniel has started working on gpmc dt. Let us take Tony's
opinion on how to deal with this, Tony ?
Up to you to figure out the ordering.
Maybe send pull requests for the
On 11/08/2012 01:29 PM, Grazvydas Ignotas wrote:
But I want to note that I'm currently trying to clean up the mess around
twl-core. In my view we have quite a bit of redundancy in there. The PWM A/B
is for driving the LED A/B outputs. We should have only these modules for
PWM/LED in twl-core:
On 10/31/2012 8:47 PM, Benoit Cousson wrote:
diff --git a/arch/arm/boot/dts/am335x-bone.dts
b/arch/arm/boot/dts/am335x-bone.dts
index c634f87..e233cfa 100644
--- a/arch/arm/boot/dts/am335x-bone.dts
+++ b/arch/arm/boot/dts/am335x-bone.dts
@@ -78,3 +78,11 @@
};
};
};
+
On Wed, Nov 07, 2012 at 22:45:20, Kevin Hilman wrote:
[...]
We could perhaps add a couple of APIs to check the SYSC values when coming
out of suspend and take appropriate action if the sysc cache does not match?
Yes, for IPs with only SW support and no drivers, we may need something
Hi Santosh,
On Tue, Nov 06, 2012 at 20:05:40, Bedia, Vaibhav wrote:
Hi Santosh,
On Tue, Nov 06, 2012 at 03:29:22, Shilimkar, Santosh wrote:
[...]
IMO, assuming that idle will not be useful from the begining is leading
down the path to poor design choices that will be much more
Op 7 nov. 2012, om 23:35 heeft Ryan Mallon rmal...@gmail.com het volgende
geschreven:
On 06/11/12 08:40, Tabi Timur-B04825 wrote:
On Mon, Nov 5, 2012 at 2:40 PM, Grant Likely grant.lik...@secretlab.ca
wrote:
Jane is building custom BeagleBone expansion boards called 'capes'. She
can
Hello,
Changes cince v1:
- The turn on/off sequence has been corrected for twl4030 PWMs as suggested by
Grazvydas Ignotas
- Comment section added to the new drivers to describe what they are controlling
The series has been tested (with additional, pending patches):
Zoom2 for twl4030 PWM0
This driver only supported the Charging indicator LED.
New set of drivers going to provide support for both PWMs and LEDs for twl4030
and twl6030 series of PMICs.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/pwm/Kconfig | 9 ---
drivers/pwm/Makefile | 1 -
The driver supports the following LED outputs as generic PWM driver:
TWL4030 LEDA and LEDB (PWMA and PWMB)
TWL6030 Charging indicator LED (PWM LED)
On TWL6030 when the PWM requested LED is configured to be controlled by SW.
In this case the user can enable/disable and set the duty period freely.
The driver supports the following PWM outputs:
TWL4030 PWM0 and PWM1
TWL6030 PWM1 and PWM2
On TWL4030 the PWM signals are muxed. Upon requesting the PWM the driver
will select the correct mux so the PWM can be used. When the PWM has been
freed the original configuration going to be restored.
Koen Kooi wrote:
And as Pantelis mentioned before, I really don't want my users to change the
bootloader whenever they add a new LED.
Well, U-Boot does allow you to manipulate the device tree from the
command-line, but I understand that this feature doesn't work that well.
--
Timur Tabi
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor Grinberg wrote:
CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
Make OMAP2+ timer code independant from the CONFIG_OMAP_32K_TIMER
setting.
To remove
* Igor Grinberg grinb...@compulab.co.il [121107 23:15]:
On 11/07/12 19:33, Tony Lindgren wrote:
I think this should be the default for the timers as that counter
does not stop during deeper idle states.
Well, it is the default as you can see from the patch.
The problem is that for
* Marek Szyprowski m.szyprow...@samsung.com [121107 23:48]:
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
CC: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap1/io.c |1 -
arch/arm/mach-omap2/io.c | 12
arch/arm/plat-omap/common.c
On 11/07/2012 04:04 PM, Santosh Shilimkar wrote:
On Wednesday 07 November 2012 01:01 PM, Jon Hunter wrote:
For OMAP2+ devices, when using DMTIMERs for system timers
(clock-events and
clock-source) the posted mode configuration of the timers is used. To
allow
the compiler to optimise the
On 11/07/2012 05:43 PM, Santosh Shilimkar wrote:
On Wednesday 07 November 2012 05:28 PM, Jon Hunter wrote:
On 11/07/2012 04:14 PM, Santosh Shilimkar wrote:
Looks sensible considering alternative WAs.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Thanks. With further thought I
On 11/8/2012 3:28 AM, Koen Kooi wrote:
Op 7 nov. 2012, om 23:35 heeft Ryan Mallon rmal...@gmail.com het volgende
geschreven:
On 06/11/12 08:40, Tabi Timur-B04825 wrote:
On Mon, Nov 5, 2012 at 2:40 PM, Grant Likely grant.lik...@secretlab.ca
wrote:
Jane is building custom BeagleBone
On Thu, Nov 08, 2012 at 21:46:53, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor Grinberg wrote:
CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
Make OMAP2+ timer code
On Thu, Nov 08, 2012 at 21:50:05, Tony Lindgren wrote:
* Igor Grinberg grinb...@compulab.co.il [121107 23:15]:
On 11/07/12 19:33, Tony Lindgren wrote:
I think this should be the default for the timers as that counter
does not stop during deeper idle states.
Well, it is the
On 11/07/2012 05:44 PM, Tony Lindgren wrote:
Hi Jon,
* Tony Lindgren t...@atomide.com [121106 16:48]:
* Jon Hunter jon-hun...@ti.com [121102 12:01]:
g...@github.com:jonhunter/linux.git dev-dt-timer
Thanks pulling into omap-for-v3.8/dt branch.
Looks like omap-for-v3.8/dt boots OK on
* Jon Hunter jon-hun...@ti.com [121108 09:21]:
On 11/07/2012 05:44 PM, Tony Lindgren wrote:
That's a bugger. I completely missed your patch last week sorry (I will blame
the Danish
beer) and had clearly not folded in to my testing!
:)
I guess we should apply the following fix
On 11/08/2012 11:08 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 21:46:53, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor Grinberg wrote:
CONFIG_OMAP_32K_TIMER is kind of standing on the
The offset parameter is in fact the pin index. The printed
value is then most of the time wrong.
Multiply that value by the width to get the proper offset.
Signed-off-by: Benoit Cousson b-cous...@ti.com
---
Hi Tony,
I guess that should probably go for 3.7-rc.
Regards,
Benoit
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
On 11/08/2012 11:08 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 21:46:53, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
On 11/07/12 23:36, Jon Hunter wrote:
Hi Igor,
On 11/07/2012 08:42 AM, Igor
On Thu, 8 Nov 2012, Jon Hunter wrote:
Igor was mentioning a h/w scenario where the 32kHz source is not
present. However, I am not sure which devices support this and is
applicable too.
Pretty sure Igor is referring to the AM3517/3505. This is very poorly
documented, but can be observed in
* Benoit Cousson b-cous...@ti.com [121108 09:46]:
The offset parameter is in fact the pin index. The printed
value is then most of the time wrong.
Multiply that value by the width to get the proper offset.
Signed-off-by: Benoit Cousson b-cous...@ti.com
---
Hi Tony,
I guess that should
On Wed, 7 Nov 2012, Paul Walmsley wrote:
On Wed, 7 Nov 2012, Paul Walmsley wrote:
On Tue, 6 Nov 2012, Tony Lindgren wrote:
I'm getting errors with the allnoconfig ones, there are total four
omap defconfigs there not counting the randconfigs.
That might indeed explain the
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are missing the point here. For OMAP devices we have two
main external clock sources which are the 32kHz clock
On Wed, 7 Nov 2012, Mike Turquette wrote:
From: Rajendra Nayak rna...@ti.com
The patch is the output from a python script which converts
from the old OMAP clk format to COMMON clk format using a
JSON parser in between which was developed by Paul Walmsley.
Signed-off-by: Rajendra Nayak
On 11/08/2012 11:58 AM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
Igor was mentioning a h/w scenario where the 32kHz source is not
present. However, I am not sure which devices support this and is
applicable too.
Pretty sure Igor is referring to the AM3517/3505. This is
On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are missing the point here. For OMAP devices we have two
main
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are missing the point here. For OMAP devices we have two
main external clock sources which are the 32kHz clock and the sys_clk
(can be a range of frequencies from
On Thu, 8 Nov 2012, Jon Hunter wrote:
On 11/08/2012 11:58 AM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
Igor was mentioning a h/w scenario where the 32kHz source is not
present. However, I am not sure which devices support this and is
applicable too.
Pretty sure
Hi,
On Tue, Nov 06, 2012 at 08:44:59PM +0530, Afzal Mohammed wrote:
Hi Balbi,
This is a resend of remaining changes to get am335x usb working. These
were sent on 31 Oct with subject, usb: musb: dsps: fixes for -rc.
there is no more time for this to reach -rc. Do we need it for v3.8
merge
On Thu, Nov 08, 2012 at 23:43:31, Hunter, Jon wrote:
On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are
On 11/08/2012 12:17 PM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
On 11/08/2012 11:58 AM, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Jon Hunter wrote:
Igor was mentioning a h/w scenario where the 32kHz source is not
present. However, I am not sure which devices support this
On 11/08/2012 12:28 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:43:31, Hunter, Jon wrote:
On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57,
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which source should be used in runtime
for boards that do not have the 32k oscillator wired.
So thinking about this some more and given that we are moving away from
board files, if a board does not
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which source should be used in runtime
for boards that do not have the 32k oscillator wired.
So thinking about this some more and given that
On 11/8/2012 6:42 AM, Mike Turquette wrote:
From: Mike Turquette mturque...@linaro.org
Hi all,
This series is based on top of Paul's PRM/CM clean-up work. It is a
refresh of the patches Rajendra sent out a while back[1], with the
addition of several fixes for PM regressions[2] across
From: Kevin Hilman khil...@ti.com
On OMAP4 boards using the TWL6030 PMIC, the sys_drm_msecure is
connected to the MSECURE input of the TWL6030 PMIC. This signal
controls the secure-mode operation of the PMIC. If its not mux'd
correctly, some functionality of the PMIC will not be accessible
On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wrote:
On 11/08/2012 01:59 AM, Igor Grinberg wrote:
[snip]
There is no reliable way to determine which source should be used in runtime
for boards that do not have the 32k oscillator wired.
So
Mike Turquette mturque...@ti.com writes:
Quoting Rajendra Nayak (2012-11-07 21:02:59)
On Thursday 08 November 2012 06:42 AM, Mike Turquette wrote:
I also tested on OMAP4460 Panda-ES. Boot is fine and PRCM programming
appears sane. However Panda-ES never comes back from suspend/resume.
On Mon, 15 Oct 2012, Paul Walmsley wrote:
The OMAP watchdog timer driver directly calls a function exported by
code in arch/arm/mach-omap2. This is not good; it tightly couples
this driver to the mach-omap2 integration code. Instead, add a
temporary platform_data function pointer to
Hi,
On Thu, Nov 08, 2012 at 11:08:50AM -0800, Kevin Hilman wrote:
From: Kevin Hilman khil...@ti.com
On OMAP4 boards using the TWL6030 PMIC, the sys_drm_msecure is
connected to the MSECURE input of the TWL6030 PMIC. This signal
controls the secure-mode operation of the PMIC. If its not
On 11/08/2012 11:38 AM, Tony Lindgren wrote:
* Jon Hunter jon-hun...@ti.com [121108 09:21]:
On 11/07/2012 05:44 PM, Tony Lindgren wrote:
That's a bugger. I completely missed your patch last week sorry (I will
blame the Danish
beer) and had clearly not folded in to my testing!
:)
I
On 21:28-20121108, Felipe Balbi wrote:
Hi,
On Thu, Nov 08, 2012 at 11:08:50AM -0800, Kevin Hilman wrote:
From: Kevin Hilman khil...@ti.com
On OMAP4 boards using the TWL6030 PMIC, the sys_drm_msecure is
connected to the MSECURE input of the TWL6030 PMIC. This signal
controls
Just use BUG_ON() instead of constructions such as:
if (...)
BUG()
A simplified version of the semantic patch that makes this transformation
is as follows: (http://coccinelle.lip6.fr/)
// smpl
@@
expression e;
@@
- if (e) BUG();
+ BUG_ON(e);
// /smpl
Signed-off-by:
On 11/02/2012 07:32 AM, Vaibhav Bedia wrote:
AM33XX has only one usable timer in the WKUP domain.
Currently the timer instance in WKUP domain is used
as the clockevent and the timer in non-WKUP domain
as the clocksource. The timer in WKUP domain can keep
running in suspend from a 32K clock
Quoting Paul Walmsley (2012-11-08 10:08:16)
On Wed, 7 Nov 2012, Mike Turquette wrote:
From: Rajendra Nayak rna...@ti.com
The patch is the output from a python script which converts
from the old OMAP clk format to COMMON clk format using a
JSON parser in between which was developed by
On Thu, 8 Nov 2012, Paul Walmsley wrote:
Am seeing warnings during the disable-unused-clocks phase of the boot on
the OMAP3 test boards here.
Similar problems during system suspend on 3530ES3 Beagle. Not sure
what's causing these yet. At this point the clockdomain usecounts
should be
On Thu, 25 Oct 2012, Paul Walmsley wrote:
Convert the OMAP clock code's _omap2_module_wait_ready() to use
SoC-independent CM functions that are provided by the CM code, rather
than using a deprecated function from mach-omap2/prcm.c.
This facilitates the future conversion of the CM code to a
The OMAP port to the common clk framework[1] resulted in spurious WARNs
while disable unused clocks. This is due to _clkdm_clk_hwmod_disable
catching clkdm-usecount's with a value of zero. Even less desirable it
would not allow the clkdm_clk_disable function pointer to get called due
to an early
On Thu, 8 Nov 2012, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Paul Walmsley wrote:
Am seeing warnings during the disable-unused-clocks phase of the boot on
the OMAP3 test boards here.
Similar problems during system suspend on 3530ES3 Beagle. Not sure
what's causing these yet. At this
When booting with device-tree the kernel is panicing in the probe of the
DMTIMER driver. The panic is caused because the pointer to platform_data
structure is NULL when booting with device-tree and the driver is
attempting to access the structure without checking if the pointer is
valid.
Fix this
On 11/08/2012 01:47 PM, Jon Hunter wrote:
Do you want to generate the patch or me?
Patch posted here ...
http://marc.info/?l=linux-omapm=135242025202171w=2
Cheers
Jon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
On Fri, 9 Nov 2012, Paul Walmsley wrote:
One observation is that dpll4_m5x2_ck and dpll4_m6x2_ck are never enabled.
The tracebacks occur when something in the suspend path tries to disable
those clocks.
Sorry, this part is inaccurate - I misread the trace. The suspend path
errors are
On Fri, 9 Nov 2012, Paul Walmsley wrote:
The enables and disables of dpll4_m2x2_ck from the entire log appear to be
balanced:
Looks like this is an artifact of the disable-unused-clocks problem. The
disable of dpll4_m6x2_ck during that phase removes the usecount that was
previously added
On 11/08/2012 12:06 PM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:28:53, Hunter, Jon wrote:
On 11/08/2012 11:47 AM, Hiremath, Vaibhav wrote:
On Thu, Nov 08, 2012 at 23:09:57, Hunter, Jon wrote:
[snip]
I think you are missing the point here. For OMAP devices we have two
main
Quoting Paul Walmsley (2012-11-08 16:11:12)
On Thu, 8 Nov 2012, Paul Walmsley wrote:
On Thu, 8 Nov 2012, Paul Walmsley wrote:
Am seeing warnings during the disable-unused-clocks phase of the boot on
the OMAP3 test boards here.
Similar problems during system suspend on 3530ES3
On Thu, 8 Nov 2012, Mike Turquette wrote:
The OMAP port to the common clk framework[1] resulted in spurious WARNs
while disable unused clocks. This is due to _clkdm_clk_hwmod_disable
catching clkdm-usecount's with a value of zero. Even less desirable it
would not allow the clkdm_clk_disable
On 11/08/2012 06:17 PM, Jon Hunter wrote:
When booting with device-tree the kernel is panicing in the probe of the
DMTIMER driver. The panic is caused because the pointer to platform_data
structure is NULL when booting with device-tree and the driver is
attempting to access the structure
Quoting Paul Walmsley (2012-11-08 16:58:21)
On Thu, 8 Nov 2012, Mike Turquette wrote:
The OMAP port to the common clk framework[1] resulted in spurious WARNs
while disable unused clocks. This is due to _clkdm_clk_hwmod_disable
catching clkdm-usecount's with a value of zero. Even less
On Mon, Nov 05, 2012 at 08:40:30PM +, Grant Likely wrote:
Hey folks,
As promised, here is my early draft to try and capture what device
tree overlays need to do and how to get there. Comments and
suggestions greatly appreciated.
Device Tree Overlay Feature
Hrm. So, you may yet
Hi Pantelis,
I hope I'm not too late to reply as I'm traveling.
On Nov 6, 2012, at 5:30 AM, Pantelis Antoniou
pa...@antoniou-consulting.com wrote:
Joanne has purchased one of Jane's capes and packaged it into a rugged
case for data logging. As far as Joanne is concerned, the BeagleBone and
On Thu, Nov 08, 2012 at 01:23:08PM +0530, Philip, Avinash wrote:
diff --git a/Documentation/devicetree/bindings/pwm/tipwmss.txt
b/Documentation/devicetree/bindings/pwm/tipwmss.txt
new file mode 100644
index 000..b6c2814
--- /dev/null
+++
75 matches
Mail list logo
