On Fri, Oct 19, 2012 at 12:36:12PM +0530, AnilKumar Ch wrote:
> Remove const from pointer to array of gpios in matrix_keypad_platform_data
> struct. This is required if we update row_gpios and col_gpios based on
> device tree data.
Then don't. Set them up via non-const aliases instead.
Thanks.
-
* Haojian Zhuang [121018 02:09]:
> Add comments with pinconf & gpio range in the document of
> pinctrl-single.
>
> Signed-off-by: Haojian Zhuang
> ---
> .../devicetree/bindings/pinctrl/pinctrl-single.txt | 43
>
> 1 files changed, 43 insertions(+), 0 deletions(-)
>
> di
Hi,
Few minor comments below.
* Haojian Zhuang [121018 02:08]:
> Marvell's PXA/MMP silicon also match the behavior of pinctrl-single.
> Each pin binds to one register. A lot of pins could be configured
> as gpio.
>
> Now add three properties in below.
> pinctrl-single,gpio-mask: mask of enable/
On Fri, 2012-10-19 at 23:38 +1300, Tony Prisk wrote:
> This patch adds pwm support to arch-vt8500 board files, and adds
> the use-case of pwm-backlight.
>
> Signed-off-by: Tony Prisk
> ---
> arch/arm/boot/dts/vt8500-bv07.dts |8
> arch/arm/boot/dts/vt8500.dtsi | 29 +++
Hi Stephen,
On Fri, 28 Sep 2012 09:22:48 -0600, Stephen Warren
wrote:
> On 09/27/2012 07:41 PM, Simon Glass wrote:
> > Rather than leave the fdt down next to the code/data, we really should
> > relocate it along with everything else. For CONFIG_OF_EMBED this happens
> > automatically, but for CO
* Haojian Zhuang [121018 02:08]:
> Add pinconf generic support with POWER SOURCE, BIAS PULL.
...
> + case PIN_CONFIG_POWER_SOURCE:
> + if (pcs->psmask == PCS_OFF_DISABLED
> + || pcs->psshift == PCS_OFF_DISABLED)
> + return -ENOTSUPP;
> +
* Haojian Zhuang [121018 19:25]:
>
> I wonder whether gpio function in OMAP is also configured in the pinmux
> register. For example, the function is 3bit field in pinmux register
> of Marvell's
> PXA/MMP silicon. GPIO function is the one of function.
For omaps, the mux registers in padconf area
* Tony Lindgren [121018 19:41]:
> * Haojian Zhuang [121018 19:25]:
> >
> > I wonder whether gpio function in OMAP is also configured in the pinmux
> > register. For example, the function is 3bit field in pinmux register
> > of Marvell's
> > PXA/MMP silicon. GPIO function is the one of function.
* Haojian Zhuang [121018 19:54]:
> On Fri, Oct 19, 2012 at 10:38 AM, Tony Lindgren wrote:
> > * Haojian Zhuang [121018 19:17]:
> >> On Fri, Oct 19, 2012 at 6:28 AM, Tony Lindgren wrote:
> >> >
> >> > Specifically could you decribe the cases where this issue happens?
> >> > Also check if one of
On Fri, Oct 19, 2012 at 12:02:42PM +, Bedia, Vaibhav wrote:
> On Fri, Oct 19, 2012 at 16:45:58, Porter, Matt wrote:
> > On Fri, Oct 19, 2012 at 10:26:20AM +, Bedia, Vaibhav wrote:
> [...]
> > >
> > > I didn't see all the patches that you posted on edma-dmaengine-v3
> > > but I do seem them
Tony,
On 18 October 2012 18:52, Tony Lindgren wrote:
> Thanks, the related patches are now posted in thread
> "[PATCH v3 0/6] omap iommu changes to remove plat includes".
Ok.
> Also, can you please take a look at the "Updated status of the removal
> of plat headers" thread?
>
> I've tagged you
On 10/19/2012 03:20 AM, Tony Prisk wrote:
> On Fri, 2012-10-19 at 18:06 +0900, Alexandre Courbot wrote:
>> Make use of the power sequences specified in the device tree or platform
>> data to control how the backlight is powered on and off.
Tony, please do cut down the amount of the patch that you
For OMAP devices, the 32kHz counter is the default clock-source for the kernel.
However, this is not the only possible clock-source the kernel can use for OMAP
devices.
When booting with device-tree, if the 32kHz counter is the desired clock-source
for the kernel, then parse the device-tree blob t
Adds the counter-32k timers nodes present in OMAP2/3/4 devices and
device-tree binding documentation for OMAP counter-32k.
Signed-off-by: Jon Hunter
---
.../devicetree/bindings/arm/omap/counter.txt | 15 +++
arch/arm/boot/dts/omap2420.dtsi|6 ++
ar
This series adds device-tree support for the 32kHz counter on OMAP2+ devices,
which is used as the default kernel clock-source for OMAP devices.
Boot tested on OMAP2420 H4, OMAP3430 Beagle Board and OMAP4430 Panda Board
with and without device-tree present.
Based and dependent upon OMAP2+ series
On 10/19/2012 09:59 AM, Jon Hunter wrote:
> Add the 12 GP timers nodes present in OMAP2.
> Add the 12 GP timers nodes present in OMAP3.
> Add the 11 GP timers nodes present in OMAP4.
> Add the 7 GP timers nodes present in AM33xx.
>
> Add documentation for timer properties specific to OMAP.
>
> Th
In order to add device-tree support to the timer driver the following changes
were made ...
1. Allocate system timers (used for clock-events and clock-source) based upon
timer properties rather than using an hard-coded timer instance ID. To allow
this a new helper function called omap_dmtime
OMAP3 devices may or may not have security features enabled. Security enabled
devices are known as high-secure (HS) and devices without security are known as
general purpose (GP).
Some OMAP3 boards, such as the OMAP3 beagle board, only use GP devices and for
GP devices there is a 12th timer availa
Add the 12 GP timers nodes present in OMAP2.
Add the 12 GP timers nodes present in OMAP3.
Add the 11 GP timers nodes present in OMAP4.
Add the 7 GP timers nodes present in AM33xx.
Add documentation for timer properties specific to OMAP.
Thanks to Vaibhav Hiremath for creating the AM33xx timer nod
Currently OMAP timers can be requested by requesting any available or by a
numerical device ID. If a specific timer is required because it has a particular
capability, such as can interrupt the on-chip DSP in addition to the ARM CPU,
then the user needs to know the device ID of the timer with this
OMAP3 devices may or may not have security features enabled. Security enabled
devices are known as high-secure (HS) and devices without security are known as
general purpose (GP).
For OMAP3 devices there are 12 general purpose timers available. On secure
devices the 12th timer is reserved for secu
This series adds device-tree support for the timers on OMAP2+ devices
including AM33xx. Based upon v3.7-rc1.
Testing:
1. I have booted tested this series on OMAP2420 H4, OMAP3430 Beagle, OMAP4430
Panda and AM335x Beagle Bone with/without ...
a). device-tree present
b). CONFIG_OMAP_32K_TIM
On 10/19/2012 02:06 AM, AnilKumar Ch wrote:
> Add device tree support to matrix keypad driver and usage details
> are added to device tree documentation. Driver was tested on AM335x
> EVM.
>
> Signed-off-by: AnilKumar Ch
> ---
> .../devicetree/bindings/input/matrix-keypad.txt| 52 +
On Fri, Oct 19, 2012 at 10:26:20AM +, Bedia, Vaibhav wrote:
> Hi Matt,
>
> On Thu, Oct 18, 2012 at 18:56:39, Porter, Matt wrote:
> > Changes since v2:
> > - Rebased on 3.7-rc1
> > - Fixed bug in DT/pdata parsing first found by Gururaja
> > that turned out to be masked by some too
This patch adds pwm support to arch-vt8500 board files, and adds
the use-case of pwm-backlight.
Signed-off-by: Tony Prisk
---
arch/arm/boot/dts/vt8500-bv07.dts |8
arch/arm/boot/dts/vt8500.dtsi | 29 +
arch/arm/boot/dts/wm8505-ref.dts |8 ++
Add a binding document describing the PWM controller found
on arch-vt8500 supported SoCs.
Signed-off-by: Tony Prisk
---
.../devicetree/bindings/pwm/vt8500-pwm.txt | 17 +
1 file changed, 17 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pwm/vt8500-p
This patch updates pwm-vt8500.c to support devicetree probing and
make use of the common clock subsystem.
Signed-off-by: Tony Prisk
---
drivers/pwm/pwm-vt8500.c | 79 ++
1 file changed, 51 insertions(+), 28 deletions(-)
diff --git a/drivers/pwm/pwm-
On Friday 19 October 2012 17:20:36 Tony Prisk wrote:
> On Fri, 2012-10-19 at 18:06 +0900, Alexandre Courbot wrote:
> > +static void pwm_backlight_on(struct backlight_device *bl)
> > +{
> > + struct pwm_bl_data *pb = dev_get_drvdata(&bl->dev);
> > + int ret;
> > +
> > + if (pb->enabled)
On Fri, 2012-10-19 at 18:06 +0900, Alexandre Courbot wrote:
> Make use of the power sequences specified in the device tree or platform
> data to control how the backlight is powered on and off.
>
> Signed-off-by: Alexandre Courbot
> ---
> .../bindings/video/backlight/pwm-backlight.txt | 72
Signed-off-by: Alexandre Courbot
---
arch/arm/boot/dts/tegra20-ventana.dts | 59 ++-
1 file changed, 58 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/tegra20-ventana.dts
b/arch/arm/boot/dts/tegra20-ventana.dts
index bec8bb2..877a1bb 100644
--- a/arc
Some device drivers (e.g. panel backlights ) need to follow precise
sequences for powering on and off, involving GPIOs, regulators, PWMs
with a precise powering order and delays to respect between each steps.
These sequences are device-specific, and do not belong to a particular
driver - therefore
Make use of the power sequences specified in the device tree or platform
data to control how the backlight is powered on and off.
Signed-off-by: Alexandre Courbot
---
.../bindings/video/backlight/pwm-backlight.txt | 72 -
drivers/video/backlight/Kconfig| 1 +
d
Quite a big redesign of the feature - both structures and code have been
simplified and should be easier to read and understand, data duplication is
avoided, and much less memory allocations take place at runtime. Usage
interface is also simpler and IMHO more logical.
What happened is that platfor
Hi,
the following patch adds generic openfirmware/devicetree support to
enc28j60 driver.
It also adds support for custom hardware based (FPGA) "interrupt line
deasserter" for processors with level triggered interrupts
(for example Altera Nios2), as the enc28j60 works only with
processors with edg
Add device tree support to matrix keypad driver and usage details
are added to device tree documentation. Driver was tested on AM335x
EVM.
Signed-off-by: AnilKumar Ch
---
.../devicetree/bindings/input/matrix-keypad.txt| 52 ++
drivers/input/keyboard/matrix_keypad.c | 1
Add device tree support to matrix keypad driver by adding all necessary
DT parameters. Also added device tree bindings.
These patches were tested on AM335x-EVM with DT patches, DT patches
will be submitted once these are accepted.
AnilKumar Ch (2):
Input: matrix-keypad - remove const from point
Remove const from pointer to array of gpios in matrix_keypad_platform_data
struct. This is required if we update row_gpios and col_gpios based on
device tree data.
Signed-off-by: AnilKumar Ch
---
include/linux/input/matrix_keypad.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
di
37 matches
Mail list logo
