Hello Tomi,
On Tue, Dec 29, 2015 at 7:23 AM, Tomi Valkeinen <tomi.valkei...@ti.com> wrote:
> Hi Javier, Tony,
>
> On 22/12/15 23:18, Javier Martinez Canillas wrote:
>
>>> But if the userspace is using any omapfb specific apps, then yes, update
>>> is neces
drivers/staging/media/omap4iss/iss.c
>> @@ -1412,6 +1412,9 @@ static int iss_probe(struct platform_device *pdev)
>> unsigned int i;
>> int ret;
>>
>> +
>> +printk("%s: pdata=%p\n", __func__, pdata);
>> +
>> if (!pdata)
Hello Uri,
On Thu, Dec 24, 2015 at 12:35 PM, Uri Mashiach
wrote:
> Add DT support for the wl1271 SPI WiFi.
>
> Add documentation file for the wl1271 SPI WiFi.
>
> Signed-off-by: Uri Mashiach
> Acked-by: Igor Grinberg
Hello Uri,
On Thu, Dec 24, 2015 at 12:35 PM, Uri Mashiach
wrote:
> Device tree modifications:
> - Pinmux for SPI0 and WiFi GPIOs.
> - SPI0 node with wlcore as a child node.
>
> Cc: Tony Lindgren
> Signed-off-by: Uri Mashiach
Hello Paul,
[snip]
> +
> +_pmx_core {
> + pinctrl-names = "default";
> +
> + uart3_pins: pinmux_uart3_pins {
> + pinctrl-single,pins = <
> + 0x16e (PIN_INPUT | MUX_MODE0) /*
> uart3_rx_irrx */
> + 0x170 (PIN_OUTPUT
Hello Tomi,
On Fri, Dec 18, 2015 at 1:14 PM, Tomi Valkeinen wrote:
> On 18/12/15 18:05, Tony Lindgren wrote:
>
>>> Are you referring to Kconfig options? Or userspace?
>>
>> Well sounds like both need updating :)
>
> Depends... For simple fb apps, omapdrm works fine, and X
Hello Tomi,
On 12/22/2015 04:50 AM, Tomi Valkeinen wrote:
> Hi Javier,
>
> On 21/12/15 20:26, Javier Martinez Canillas wrote:
>> The omapfb is failing to build in -next due missing declarations for
>> dss_feat_get_supported_displays() and dss_feat_get_supported_outputs():
&
outside the driver.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
Hello Tomi,
This seems to be caused by a wrong order in which some commits from
the omapdss tree [0] were merged, or rather a wrong base used for
the dss-drm-merge (4.4.0-rc4) and the for-next (4.4
ly it shall be optional! I wonder how I could let that patch
>> slip through, my bad!
>
I also wonder how I missed that in my patch, sorry for the mess :(
> OK good to hear :)
>
>> Thanks for fixing this!
>
+1
> No problem, thanks,
>
> Tony
>
Bes
Hello Tony,
On 12/03/2015 03:16 PM, Tony Lindgren wrote:
> * Javier Martinez Canillas <jav...@osg.samsung.com> [151203 10:03]:
>> Hello,
>>
>> This series converts the IGEPv2 (IGEP0020) and IGEP COM Module (IGEP0030)
>> Device Tree to use the MMC power sequenc
.
But now the simple MMC power sequence provider can be used for this and
the workaround removed.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
arch/arm/boot/dts/omap3-igep0030.dts | 24
1 file changed, 8 insertions(+), 16 deletions(-)
diff
preferred to leave those untouched.
Best regards,
Javier
Javier Martinez Canillas (2):
ARM: dts: omap3-igep0020: Use MMC pwrseq to init SDIO WiFi
ARM: dts: omap3-igep0030: Use MMC pwrseq to init SDIO WiFi
arch/arm/boot/dts/omap3-igep0020.dts | 24
arch/arm/boot/dts/omap3
.
But now the simple MMC power sequence provider can be used for this and
the workaround removed.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
arch/arm/boot/dts/omap3-igep0020.dts | 24
1 file changed, 8 insertions(+), 16 deletions(-)
diff
Hello Linus,
On 11/17/2015 10:47 AM, Linus Walleij wrote:
> On Fri, Nov 13, 2015 at 5:53 AM, Javier Martinez Canillas
> <jav...@osg.samsung.com> wrote:
>
>> The header file defines a set of macros
>> for different SoCs families that falls under the OMAP sub-ar
Use the pinmux IOPAD macros to define the register as an offset from
the padconf physical address instead of the offset from padconf base.
This makes the DTS easier to read since matches the addresses listed
in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <
Use the pinmux IOPAD macros to define the register as an offset from
the padconf physical address instead of the offset from padconf base.
This makes the DTS easier to read since matches the addresses listed
in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <
Use the pinmux IOPAD macros to define the register as an offset from
the padconf physical address instead of the offset from padconf base.
This makes the DTS easier to read since matches the addresses listed
in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <
Use the pinmux IOPAD macros to define the register as an offset from
the padconf physical address instead of the offset from padconf base.
This makes the DTS easier to read since matches the addresses listed
in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macros to define the register as an offset from
the padconf physical address instead of the offset from padconf base.
This makes the DTS easier to read since matches the addresses listed
in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <
Use the pinmux IOPAD macros to define the register as an offset from
the padconf physical address instead of the offset from padconf base.
This makes the DTS easier to read since matches the addresses listed
in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <
Use the pinmux IOPAD macros to define the register as an offset from
the padconf physical address instead of the offset from padconf base.
This makes the DTS easier to read since matches the addresses listed
in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <
Use the pinmux IOPAD macros to define the register as an offset from
the padconf physical address instead of the offset from padconf base.
This makes the DTS easier to read since matches the addresses listed
in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <
Use the pinmux IOPAD macros to define the register as an offset from
the padconf physical address instead of the offset from padconf base.
This makes the DTS easier to read since matches the addresses listed
in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
]: https://lkml.org/lkml/2015/10/24/114
Best regards,
Javier
Javier Martinez Canillas (39):
pinctrl: Move am4372 and dra7 macros to the the SoC header files
ARM: dts: am335x-baltos-ir5221: Remove leftover pinctrl lines
ARM: dts: am335x-baltos-ir5221: Use AM33XX_IOPAD pinmux macro
ARM: dts
for the padconf
values when defining the pinctrl lines to make it more readable.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
arch/arm/boot/dts/am335x-baltos-ir5221.dts | 182 ++---
1 file changed, 91 insertions(+), 91 deletions(-)
diff --git a/arch/ar
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
When the Device Tree source file got merged, some commented pinctrl lines
were left in the file. These are already defined so seems to be a cleanup
that was missed. Delete the unneeded lines from the file.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
arch/arm/bo
the DTS using these SoCs aren't able to use the AM4372_IOPAD()
and DRA7XX_CORE_IOPAD() macros since is
not included.
Move the macros to the correct header files so can be used by the DTS.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
include/dt-bindings/pinctrl/am
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macros to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macros to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macros to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macros to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
Use the pinmux IOPAD macro to define the register absolute physical
address instead of the offset from the padconf base address. This
makes the DTS easier to read since matches the addresses listed in
the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.
for the padconf
values when defining the pinctrl lines to make it more readable.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
arch/arm/boot/dts/am335x-evm.dts | 220 +++
1 file changed, 110 insertions(+), 110 deletions(-)
diff --git a/arch/ar
for the padconf
values when defining the pinctrl lines to make it more readable.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
arch/arm/boot/dts/am335x-evmsk.dts | 278 ++---
1 file changed, 139 insertions(+), 139 deletions(-)
diff --git a/arch/ar
Hello Andrew,
On Sat, Oct 24, 2015 at 2:05 PM, Andrew F. Davis wrote:
> Using constants for pinctrl allows better readability and removes
> redundancy with comments. AM33XX_IOPAD allows us to use part of the
> pinctrl physical address as in the TRM instead of an offset.
>
>
set.
>
> Signed-off-by: Andrew F. Davis <a...@ti.com>
> ---
I haven't verified the values against the TRM, but assuming there are correct:
Reviewed-by: Javier Martinez Canillas <jav...@osg.samsung.com>
Best regards,
Javier
--
To unsubscribe from this list: send the line
Hello Andrew,
On Fri, Oct 23, 2015 at 3:08 PM, Andrew F. Davis wrote:
> On 10/22/2015 04:23 PM, Tony Lindgren wrote:
>>
>> * Andrew F. Davis [151022 09:21]:
>>>
>>> Using constants for pinctrl allows better readability and removes
>>> redundancy with comments.
>>
>>
>>
Hello Andrew,
On Fri, Oct 23, 2015 at 4:36 PM, Andrew F. Davis <a...@ti.com> wrote:
> On 10/23/2015 09:29 AM, Javier Martinez Canillas wrote:
>>
>> Hello Andrew,
>>
>> On Fri, Oct 23, 2015 at 3:08 PM, Andrew F. Davis <a...@ti.com> wrote:
>>>
Hello Tony,
On 10/20/2015 06:26 PM, Tony Lindgren wrote:
> * Javier Martinez Canillas <jav...@osg.samsung.com> [151019 08:39]:
>> Hello,
>>
>> This series use the IOPAD pinmux macros for the remaining IGEP boards that
>> still used the register offset inst
Use the OMAP3 pinmux IOPAD macro to define the physical address instead
of the offset from the padconf address. It makes the DTS easier to read
since matches the addresses listed in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
ar
Use the AM33xx pinmux IOPAD macro to define the physical address instead
of the offset from the padconf address. It makes the DTS easier to read
since matches the addresses listed in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
ar
-igep0020-rev-f.dtb
After
d7a56205bdc54365d49d9a90dfe3fafb am335x-base0033.dtb
fa272fcdee65d7bf4c03bd5a6c5ec4fd omap3-igep0020.dtb
ba65bf74d8c6ea8e7bd8face17179e6e omap3-igep0020-rev-f.dtb
Best regards,
Javier
Javier Martinez Canillas (3):
ARM: dts: omap3-igep0020: Use IOPAD pinmux macro
Use the AM33XX pinmux IOPAD macro to define the physical address instead
of the offset from the padconf address. It makes the DTS easier to read
since matches the addresses listed in the Technical Reference Manual.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
ar
I see that people are still sending emails to my old address (that no
longer exists) since is the one mentioned in the IGEP DTS. Replace it
with my current email address to avoid this.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
arch/arm/boot/dts/omap3-ige
.
>
> Signed-off-by: Laurent Pinchart <laurent.pinch...@ideasonboard.com>
> ---
Agreed with the patch and in fact I had the same change in my TODO list.
I didn't double check the values against the TRM but I trust you ;-)
Acked-by: Javier Martinez Canillas <jav...@osg.sams
nd = 0;
>> active_high = 0;
>> open_drain = 0;
>> flags = 0;
>> }
>> '
>> --
>>
>> All patches except for the ones touching omap3-beagle-xm and omap3-overo-base
&
Hello Laurent,
Thanks for the patch.
On Mon, Oct 12, 2015 at 10:46 PM, Laurent Pinchart
<laurent.pinch...@ideasonboard.com> wrote:
> Use tabs instead of spaces for indentation.
>
> Signed-off-by: Laurent Pinchart <laurent.pinch...@ideasonboard.com>
Acked-by: Javier M
h...@ideasonboard.com>
> ---
Indeed, this is something that was overlooked when the common dtsi
file was introduced in commit ebc13bf2e0d2 ("ARM: dts:
omap3-igep0020-common: Introduce igep0020 common dtsi file").
Acked-by: Javier Martinez Canillas <jav...@osg.samsung.com>
Many OMAP2+ DTS are not using the defined constants to express
the GPIO polarity. Replace these so the DTS are easier to read.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
arch/arm/boot/dts/omap2420-n8x0-common.dtsi| 6 +++---
arch/arm/boot/dts/omap3-
The card detect GPIO is using IRQ_TYPE_LEVEL_LOW in the GPIO flag cells
but this defined constant is meant to be used for a IRQ and not a GPIO.
So instead use GPIO_ACTIVE_LOW that seems to be the original intention.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
ar
[adding Ulf and Tomeu to cc list]
On Fri, Sep 18, 2015 at 10:27 PM, Tony Lindgren <t...@atomide.com> wrote:
> * Tony Lindgren <t...@atomide.com> [150918 10:54]:
>> * Javier Martinez Canillas <jav...@dowhile0.org> [150918 10:39]:
>&
Hello Tony,
[snip]
>
> + vmmcsdio_fixed: fixedregulator-mmcsdio {
> + compatible = "regulator-fixed";
> + regulator-name = "vmmcsdio_fixed";
> + regulator-min-microvolt = <180>;
> + regulator-max-microvolt = <180>;
> +
The PRM_POLCTRL_TWL_MASK and PRM_POLCTRL_TWL_MASK
macros are not used so they can be deleted.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
arch/arm/mach-omap2/vc.c | 4
1 file changed, 4 deletions(-)
diff --git a/arch/arm/mach-omap2/vc.c b/arch/arm/mach-omap
complains with the following message:
omap_hwmod_54xx_data.c:1846:37-58: duplicated argument to & or |
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a
Remove the unneded semicolons since they are clearly a typo error.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
arch/arm/mach-omap2/pm44xx.c| 2 +-
arch/arm/mach-omap2/powerdomains3xxx_data.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Drivers needs to export the OF id table and this be built into
the module or udev won't have the necessary information to autoload
the driver module when the device is registered via OF.
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
drivers/video/fbdev/omap2/displa
for the padconf reg.
Suggested-by: Ladislav Michl <la...@linux-mips.org>
Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
---
arch/arm/boot/dts/omap3-igep.dtsi| 6 --
arch/arm/boot/dts/omap3-igep0020-common.dtsi | 6 ++
2 files changed, 6 insertions(+),
better to also export the OF table even when
is unused now to prevent breaking module loading when the core changes.
Signed-off-by: Javier Martinez Canillas jav...@osg.samsung.com
---
drivers/video/fbdev/omap2/displays-new/panel-sony-acx565akm.c | 1 +
1 file changed, 1 insertion(+)
diff --git
patches in this series, will break
module autoloading for the drivers of devices registered using OF but
that lacks an of_match_table. I'll repost patch #18 once all the patches
in this series have landed.
[0]: https://lkml.org/lkml/2015/7/30/519
Best regards,
Javier
Javier Martinez Canillas (18
Hello Brian,
On 08/20/2015 11:11 PM, Brian Norris wrote:
On Thu, Aug 20, 2015 at 09:07:13AM +0200, Javier Martinez Canillas wrote:
Patches #1 and #2 solves a), patches #3 to #8 solves b) and patches
^^^ I'm dying to know how this sentence ends :)
Sigh, I did some last minute restructuring
so after these changes feel free to
also add my:
Reviewed-by: Javier Martinez Canillas jav...@osg.samsung.com
Best regards,
Javier
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
Hello Dmitry,
Thanks a lot for your feedback.
On 07/30/2015 06:37 PM, Dmitry Torokhov wrote:
On Thu, Jul 30, 2015 at 09:35:17AM -0700, Dmitry Torokhov wrote:
Hi Javier,
On Thu, Jul 30, 2015 at 06:18:25PM +0200, Javier Martinez Canillas wrote:
Hello,
Short version:
This series add
instead so the module can be auto-loaded and also
report the correct alias using sysfs:
$ cat /sys/class/i2c-adapter/i2c-8/8-004b/modalias
of:NtrackpadTNULLCatmel,maxtouch
Signed-off-by: Javier Martinez Canillas jav...@osg.samsung.com
---
drivers/i2c/i2c-core.c | 8
1 file changed, 8
if that happens.
Signed-off-by: Javier Martinez Canillas jav...@osg.samsung.com
---
drivers/mfd/rt5033.c | 1 +
drivers/mfd/tps65217.c | 1 +
drivers/mfd/tps65218.c | 1 +
3 files changed, 3 insertions(+)
diff --git a/drivers/mfd/rt5033.c b/drivers/mfd/rt5033.c
index db395a6c52bc..d60f91619c4a
with OF but that don't have a of_match_table.
Although arguably, those drivers were relying on the assumption that a
MODALIAS=i2c:foo would always be reported even for the OF case which
is not the true on other subsystems.
[0]: https://lkml.org/lkml/2014/8/28/283
Best regards,
Javier
Javier Martinez
...@linutronix.de
---
Should be safe to do it.
Acked-by: Santosh Shilimkar ssant...@kernel.org
Answered on the wrong thread, sorry for the noise.
Acked-by: Javier Martinez Canillas jav...@dowhile0.org
Best regards,
Javier
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the first time you posted this [0] but you didn't
carry the tag so here goes again:
Acked-by: Javier Martinez Canillas jav...@dowhile0.org
Best regards,
Javier
[0]: https://patchwork.ozlabs.org/patch/439249/
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
:
Acked-by: Javier Martinez Canillas jav...@dowhile0.org
Best regards,
Javier
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
+-
drivers/gpio/gpio-msm-v2.c |2 +-
drivers/gpio/gpio-mvebu.c |2 +-
drivers/gpio/gpio-mxc.c|4 ++--
drivers/gpio/gpio-mxs.c|2 +-
drivers/gpio/gpio-omap.c |2 +-
For gpio-omap:
Acked-by: Javier Martinez Canillas jav...@dowhile0.org
Best
-off-by: Grygorii Strashko grygorii.stras...@linaro.org
Can I get an ACK or comment from one of the three (!) maintainers
on atleast these non-RFC patches?
Sorry for the delay, the patch looks good to me.
Acked-by: Javier Martinez Canillas jav...@dowhile0.org
Yours,
Linus Walleij
Best
, handle_edge_irq);
+ return 0;
+
+error:
+ if (!BANK_USED(bank))
+ pm_runtime_put(bank-dev);
return retval;
}
--
But you are correct about the runtime PM bug so after addressing the
above comment, feel free to add:
Acked-by: Javier Martinez Canillas jav
Hello Pali,
On Thu, Apr 9, 2015 at 2:59 PM, Pali Rohár pali.ro...@gmail.com wrote:
On Thursday 09 April 2015 14:43:59 Javier Martinez Canillas wrote:
Please re-spin your previous patch and submit it properly.
Best regards,
Javier
Hi all! What about stopping this meaningless discussion
Hello Pavel,
On Thu, Apr 9, 2015 at 2:31 PM, Pavel Machek pa...@ucw.cz wrote:
Fix includes according to Sebastian.
Signed-off-by: Pavel Machek pa...@ucw.cz
---
On Thu 2015-04-09 14:19:14, Sebastian Reichel wrote:
On Thu, Apr 09, 2015 at 01:29:43PM +0200, Pavel Machek wrote:
On Thu
Hello Pavel,
On Fri, Apr 3, 2015 at 10:21 AM, Pavel Machek pa...@ucw.cz wrote:
Hi!
Fixed feedback by Sakari.
Please apply,
There is no need to ask for patches to be applied IMHO. It is expected
that people post patches wanting them to be applied unless there is an
RFC prefix in the
Hello Pavel,
I haven't reviewed the patch since I'm not familiar with the hardware
but just wanted to point out a couple of things that I spot:
On Thu, Apr 2, 2015 at 10:34 PM, Pavel Machek pa...@ucw.cz wrote:
We are moving to device tree support on OMAP3, but that currently
breaks ADP1653
Hello Grygorii,
On Fri, Mar 20, 2015 at 9:39 PM, grygorii.stras...@linaro.org
grygorii.stras...@linaro.org wrote:
On 03/20/2015 08:56 PM, Javier Martinez Canillas wrote:
Hello Grygorii,
On Thu, Mar 19, 2015 at 6:25 PM, grygorii.stras...@linaro.org wrote:
From: Grygorii Strashko
GPIO offset
as 'gpio' input parameter, so rename it to 'offset' and
drop usage of GPIO_BIT() macro.
Signed-off-by: Grygorii Strashko grygorii.stras...@linaro.org
---
Acked-by: Santosh Shilimkar ssant...@kernel.org
Acked-by: Javier Martinez Canillas jav...@dowhile0.org
--
To unsubscribe from
access to OMAP1 boards to test but Tony did it o an
osk5912 and Aaro can confirm that it doesn't cause regressions on
other OMAP1 boards.
Thanks a lot for the cleanup.
Acked-by: Javier Martinez Canillas jav...@dowhile0.org
Best regards,
Javier
--
To unsubscribe from this list: send the line
On Thu, Mar 19, 2015 at 6:25 PM, grygorii.stras...@linaro.org wrote:
From: Grygorii Strashko grygorii.stras...@linaro.org
Now OMAP GPIO driver prepared for GPIO_INDEX() macro removing.
Do It ;)
Signed-off-by: Grygorii Strashko grygorii.stras...@linaro.org
Acked-by: Javier Martinez Canillas
()
Signed-off-by: Grygorii Strashko grygorii.stras...@linaro.org
---
Acked-by: Javier Martinez Canillas jav...@dowhile0.org
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
1 - 100 of 610 matches
Mail list logo