On 11/30/15 16:33, Dmitry Lifshitz wrote:
> On-board EEPROM chip is used for storing a board production
> info.
>
> Add module EEPROM support (over I2C4 bus).
>
> Signed-off-by: Dmitry Lifshitz
Acked-by: Igor Grinberg
> ---
>
> v2:
>
>* Fix EEPROM c
Hi Dima,
On 11/25/15 08:39, Dmitry Lifshitz wrote:
> On-board EEPROM chip is used for storing a board production
> info.
>
> Add module EEPROM support (over I2C4 bus).
>
> Signed-off-by: Dmitry Lifshitz
> ---
> arch/arm/boot/dts/am57xx-cl-som-am57x.dts | 6 ++
> 1 file changed, 6 insertion
Hi Uri,
On 10/27/15 14:14, Uri Mashiach wrote:
> From: Ilya Ledvich
>
> Add basic support for CompuLab cm-t335 module based on AM335X SoC.
>
> CM-T335 is a tiny computer-on-module (CoM) / system-on-module (SoM)
> The module is built around the Texas Instruments Sitara AM3352/4
> system-on-chip.
Hi Matt,
On 07/27/15 17:34, Matt Porter wrote:
> On Thu, Jul 16, 2015 at 10:30:48AM +0200, Teresa Remmet wrote:
>> phyCORE-AM335x is a SoM (System on Module) containing
>> a AM335x SOC. The module can be connected to different
>> carrier boards.
>>
>> Some hardware parts are configurable on the ph
Hi,
On 04/07/15 06:29, Keerthy wrote:
> Hi Andrew,
>
> Apologies for replying late.
>
> On Wednesday 25 March 2015 04:29 AM, Andrew Morton wrote:
>> On Tue, 3 Mar 2015 15:12:02 +0530 Keerthy wrote:
>>
>>> Add external 32k clock feature. The internal clock will be gated during
>>> suspend.
>>>
be
> allocated and accessed separately without those needed only in the case of
> platform data. The platform data related structs can be later removed once
> the support for platform data can be removed.
>
> Signed-off-by: Sakari Ailus
> Acked-by: Laurent Pinchart
> Cc: I
x devices as it works
> now in non DT boot (in this case the timings are updated by U-Boot).
>
> Update GPMC ranges in boards DT files to include all connected devices.
>
> Signed-off-by: Dmitry Lifshitz
Acked-by: Igor Grinberg
--
Regards,
Igor.
--
To unsubscribe from this li
Hi Dima,
On 12/28/14 15:15, Dmitry Lifshitz wrote:
> Add NAND support
>
> Signed-off-by: Dmitry Lifshitz
> ---
> arch/arm/boot/dts/omap3-cm-t3x.dtsi | 58
> +
> arch/arm/boot/dts/omap3-sbc-t3517.dts |4 ++
> arch/arm/boot/dts/omap3-sbc-t3530.dts | 10 +
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/26/14 17:09, Felipe Balbi wrote:
> Hi,
>
> On Fri, Dec 26, 2014 at 01:56:26PM +0200, Igor Grinberg wrote:
>>>>>> Tony, your call.
>>>>>
>>>>> I think we should move omap2plus_defconfig to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/26/14 06:37, Felipe Balbi wrote:
> Hi,
>
> On Wed, Dec 24, 2014 at 11:04:01AM -0800, Tony Lindgren wrote:
>> * Felipe Balbi [141224 07:52]:
>>> Hi,
>>>
>>> On Wed, Dec 24, 2014 at 01:53:46PM +0200
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/26/14 06:42, Felipe Balbi wrote:
> Hi,
>
> On Thu, Dec 25, 2014 at 12:13:07PM +0200, Igor Grinberg wrote:
>> Hi Tony,
>>
>> On 12/24/14 21:04, Tony Lindgren wrote:
>>> * Felipe Balbi [141224 07:52]:
>&g
Hi Tony,
On 12/24/14 21:04, Tony Lindgren wrote:
> * Felipe Balbi [141224 07:52]:
>> Hi,
>>
>> On Wed, Dec 24, 2014 at 01:53:46PM +0200, Igor Grinberg wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On 12/23/14 18:1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/23/14 18:19, Felipe Balbi wrote:
> On Tue, Dec 23, 2014 at 09:30:45AM +0200, Igor Grinberg wrote:
>> Hi Felipe,
>>
>> On 12/22/14 20:05, Felipe Balbi wrote:
>>
>> [...]
>>
>>
Hi Felipe,
On 12/22/14 20:05, Felipe Balbi wrote:
[...]
> CONFIG_SCSI_SCAN_ASYNC=y
> -CONFIG_ATA=y
> -CONFIG_SATA_AHCI_PLATFORM=y
> -CONFIG_MD=y
> +CONFIG_ATA=m
> +CONFIG_SATA_AHCI_PLATFORM=m
Isn't this needed for the rootfs on SATA devices?
> CONFIG_NETDEVICES=y
> # CONFIG_NET_VENDOR_ARC i
Hi Paul,
On 12/02/14 20:39, Paul Walmsley wrote:
>
> Here are some basic OMAP test results for Linux v3.18-rc7.
> Logs and other details at:
>
> http://www.pwsan.com/omap/testlogs/test_v3.18-rc7/20141201203859/
>
>
> Test summary
>
>
[...]
> Build: uImage+dtb:
> Pass (1
On 11/11/14 16:49, Tony Lindgren wrote:
> * Igor Grinberg [14 04:04]:
>> Hi Tony,
>>
>> On 11/10/14 19:48, Tony Lindgren wrote:
>>> * Igor Grinberg [141102 04:08]:
>>>> On 11/02/14 13:19, Dmitry Lifshitz wrote:
>>>>> Add DSS related pi
Hi Tony,
On 11/10/14 19:48, Tony Lindgren wrote:
> * Igor Grinberg [141102 04:08]:
>> On 11/02/14 13:19, Dmitry Lifshitz wrote:
>>> Add DSS related pinmux and display data nodes required to support
>>> DVI video out on SBC-T3530, SBC-T3730 and SBC-T3517.
>>>
On 11/04/14 17:42, Tony Lindgren wrote:
> * Igor Grinberg [141104 05:22]:
>> Hi Tony,
>>
>> On 11/02/14 20:07, Tony Lindgren wrote:
>>> Commit e7cd1d1eb16f ("mfd: twl4030-power: Add generic reset
>>> configuration") enabled configuring the PM f
Hi Tony,
On 11/02/14 20:07, Tony Lindgren wrote:
> Commit e7cd1d1eb16f ("mfd: twl4030-power: Add generic reset
> configuration") enabled configuring the PM features for twl4030.
>
> This caused poweroff command to fail on devices that have the
> BCI charger on twl4030 wired, or have power wired f
On 11/02/14 13:19, Dmitry Lifshitz wrote:
> Add DSS related pinmux and display data nodes required to support
> DVI video out on SBC-T3530, SBC-T3730 and SBC-T3517.
>
> Signed-off-by: Dmitry Lifshitz
Acked-by: Igor Grinberg
--
Regards,
Igor.
--
To unsubscribe from this list: s
Hi Dmitry,
On 10/15/14 12:09, Dmitry Lifshitz wrote:
> Add DSS related pinmux and display data nodes required to support
> DVI video out on SBC-T3530, SBC-T3730 and SBC-T3517.
>
> Signed-off-by: Dmitry Lifshitz
> ---
> arch/arm/boot/dts/omap3-cm-t3517.dts | 22 +++
> arch/arm/boo
m
[...]
> A Compulab SBC-T54 (OMAP5432) has been added to the testbed, graciously
> donated by Compulab and Igor Grinberg. It currently isn't booting to
> userspace in the current mainline kernel, but if the 'ldo8' regulator is
> modified to be always-on in the oma
On 03/12/14 19:44, Tony Lindgren wrote:
> * Stefan Roese [140312 03:52]:
>> Add support for the MMC2/SDIO WiFi Libertas (Marvell) module available
>> on the CM-T3530 SOM.
>>
>> Signed-off-by: Stefan Roese
>> Cc: Dmitry Lifshitz
>> Cc: Igor Grinberg
o toggle it
before the EHCI controller resumes.
There is also a USB phy on the way from EHCI controller to the hub.
You might also want to check if the phy resumes correctly.
Which phy do you use and how is it reset?
> Regards
> Marc
> ____
&
On 03/03/14 13:06, Roger Quadros wrote:
> Hi Marc,
>
> On 03/03/2014 12:04 PM, Marc Murphy wrote:
>> Hi,
>> I am using the latest stable 3.4.80 kernel with some changes to get the EMAC
>> Phy to initialise correctly after a suspend/resume. The platform is AM3517
>> with most of the system worki
On 03/01/14 00:12, Tony Lindgren wrote:
> * Igor Grinberg [140223 04:33]:
>> ping x2!
>
> Thanks applying into omap-for-v3.15/dt finally.
Thanks!
>
> Is it OK to remove the board-cm-*.c files for v3.15?
Hmmm
I thought we will have a transition release with
know exactly how this
> should be done. Perhaps somebody else might jump in here...
>
> Signed-off-by: Stefan Roese
> Cc: Igor Grinberg
> Cc: Dmitry Lifshitz
> Cc: Tony Lindgren
> ---
> arch/arm/boot/dts/Makefile| 1 +
> arch/arm/boot/dts/omap3-cm-t3530
ping x2!
On 02/12/14 14:38, Igor Grinberg wrote:
> ping!
>
> On 01/12/14 15:22, Dmitry Lifshitz wrote:
>> Add support for CompuLab SBC-T3530 and SBC-T3517 boards:
>>
>> https://compulab.co.il/products/sbcs/sbc-t3530/
>> https://compulab.co.il/products/sbcs/sbc-t
> activity recently I believe the risk of conflict is pretty low.
Indeed, as we work on DT stuff of cm-t35/3730 and pretty much stopped
updating the board-cm-t35.c file.
> Tony, would
> that be fine with you ?
>
>> Signed-off-by: Laurent Pinchart
Acked-by: Igor G
Hi Paul,
On 02/16/14 19:26, Paul Bolle wrote:
> The Kconfig symbol MACH_CM_T3730 was added in v3.1. It has never been
> used. Setting it has no effect. There are no calls for
> machine_is_cm_t3730(). This symbol can safely be removed.
Indeed...
Is it such a burden to keep it just until we switch
ping!
On 01/12/14 15:22, Dmitry Lifshitz wrote:
> Add support for CompuLab SBC-T3530 and SBC-T3517 boards:
>
> https://compulab.co.il/products/sbcs/sbc-t3530/
> https://compulab.co.il/products/sbcs/sbc-t3517/
>
> along with respective CoMs - CM-T3530 and CM-T3517:
>
> https://compulab.co.il/pro
On 12/18/13 23:16, Tony Lindgren wrote:
[...]
>
> I've kept your Ack as the changes were minor. If no other
> comments, I will apply this into omap-for-v3.14/dt probably
> on Thursday.
Looks great! Thanks!
--
Regards,
Igor.
--
To unsubscribe from this list: send the line "unsubscribe linux-o
On 12/17/13 21:31, Tony Lindgren wrote:
> * Igor Grinberg [131216 23:16]:
>> On 12/16/13 21:17, Tony Lindgren wrote:
>>> * Igor Grinberg [131216 05:57]:
>>>> On 12/13/13 21:22, Tony Lindgren wrote:
[...]
>
>> I think we can drop the different memory
On 12/16/13 21:17, Tony Lindgren wrote:
> * Igor Grinberg [131216 05:57]:
>> On 12/13/13 21:22, Tony Lindgren wrote:
>>
>> SB-T35 has only one SMSC Ethernet on-board (smsc2),
>> while the first one is on the cm-t3530 and cm-t3730 modules.
>> SBC-T3517 has only one
t; may need some changes for the EMAC Ethernet if that's used
> instead of the smsc911x.
>
> Cc: devicet...@vger.kernel.org
> Cc: Igor Grinberg
> Cc: Mike Rapoport
> Signed-off-by: Tony Lindgren
Great job!
I'm sorry I couldn't make it in time with the conversio
ei Yongjun
Acked-by: Igor Grinberg
> ---
> arch/arm/mach-omap2/gpmc-smsc911x.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-omap2/gpmc-smsc911x.c
> b/arch/arm/mach-omap2/gpmc-smsc911x.c
> index ef99011..2757504 100644
> --- a/arc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/17/13 10:08, Tomi Valkeinen wrote:
> On 16/06/13 15:28, Igor Grinberg wrote:
>
>>>> Although one thing is missing from the tfp410 driver is
>>>> the PD GPIO polarity. I had to adjust it locally to get the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/13/13 19:01, Tomi Valkeinen wrote:
> On 13/06/13 18:51, Igor Grinberg wrote:
>> Hi Tomi,
>>
>> On 06/04/13 10:40, Tomi Valkeinen wrote:
>>> Hi guys,
>>
>>> I've made some big changes on the o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tomi,
On 06/04/13 10:40, Tomi Valkeinen wrote:
> Hi guys,
>
> I've made some big changes on the omapdss device model, which involves
> converting all the panel drivers. I've got only a bunch of boards, so I
> hope some of you can perhaps do some m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tomi,
On 06/04/13 10:40, Tomi Valkeinen wrote:
> Hi guys,
>
> I've made some big changes on the omapdss device model, which involves
> converting all the panel drivers. I've got only a bunch of boards, so I
> hope some of you can perhaps do some m
On 04/17/13 11:38, Roger Quadros wrote:
> On 04/17/2013 10:56 AM, Igor Grinberg wrote:
>> On 04/17/13 04:30, Robert Nelson wrote:
>>> On Tue, Apr 16, 2013 at 7:52 PM, Tony Lindgren wrote:
>>>> * Roger Quadros [130415 05:44]:
>>>>> On 04/15/2013 03:35
On 04/17/13 04:30, Robert Nelson wrote:
> On Tue, Apr 16, 2013 at 7:52 PM, Tony Lindgren wrote:
>> * Roger Quadros [130415 05:44]:
>>> On 04/15/2013 03:35 PM, Roger Quadros wrote:
Provide RESET and Power regulators for the USB PHY,
the USB Host port mode and the PHY device.
Al
is handled in the board file at init time, as there's a 50 ms delay
> required when using the GPIO, and the panel driver doesn't know about
> that.
>
> Cc: Tony Lindgren
> Cc: Igor Grinberg
> Signed-off-by: Tomi Valkeinen
Looks good, thanks!
Acked-by: I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/02/13 11:07, Tomi Valkeinen wrote:
> On 2013-03-31 12:17, Igor Grinberg wrote:
>>
>>
>> On 03/28/13 19:02, Tomi Valkeinen wrote:
>>> On 2013-03-28 18:09, Igor Grinberg wrote:
>>>> On 03/28/13 14:4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/02/13 11:01, Tomi Valkeinen wrote:
> On 2013-03-31 11:39, Igor Grinberg wrote:
>> On 03/28/13 18:48, Tomi Valkeinen wrote:
>>> On 2013-03-28 17:31, Igor Grinberg wrote:
>>>> On 03/28/13 14:48, Tomi Valkeinen wr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/28/13 19:02, Tomi Valkeinen wrote:
> On 2013-03-28 18:09, Igor Grinberg wrote:
>> On 03/28/13 14:49, Tomi Valkeinen wrote:
>>> Boards with multiple display options for the same video bus have all the
>>> possible li
On 03/28/13 18:57, Tony Lindgren wrote:
> * Tomi Valkeinen [130328 09:53]:
>> On 2013-03-28 17:31, Igor Grinberg wrote:
>>> On 03/28/13 14:48, Tomi Valkeinen wrote:
>>>
>>> I've missed this discussion, can you please point to it?
>>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/28/13 18:48, Tomi Valkeinen wrote:
> On 2013-03-28 17:31, Igor Grinberg wrote:
>> On 03/28/13 14:48, Tomi Valkeinen wrote:
>>> So here are the DSS related board file changes for 3.10.
>>>
>>> First there are a
On 03/28/13 14:49, Tomi Valkeinen wrote:
> Boards with multiple display options for the same video bus have all the
> possible linux display devices present at the same time. Only one of
> those devices should be used at a time, as the video bus cannot be
> shared.
Yes, only one can be used at a t
On 03/28/13 14:48, Tomi Valkeinen wrote:
> So here are the DSS related board file changes for 3.10.
>
> First there are a bunch of patches adding the Kconfig options so that only one
> display device is created for a single video bus. Only Overo had more than two
> displays on the same bus, but un
rom boards which have a VENC device.
>
> Signed-off-by: Archit Taneja
> Signed-off-by: Tomi Valkeinen
This should have been done long long time ago...
Thanks!
Acked-by: Igor Grinberg
--
Regards,
Igor.
--
To unsubscribe from this list: send the line "unsubscribe linu
On 03/12/13 18:40, Paul Walmsley wrote:
>
> Here are some basic OMAP test results for Linux v3.9-rc1.
> Logs and other details at:
>
> http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/
[...]
> Failing tests: needing investigation
>
[...]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/13 14:52, Tomi Valkeinen wrote:
> On 2013-02-14 14:37, Igor Grinberg wrote:
>> On 02/14/13 12:59, Tomi Valkeinen wrote:
>>> On 2013-02-14 11:43, Igor Grinberg wrote:
>>
>>>>> True, it's generic, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/13 12:59, Tomi Valkeinen wrote:
> On 2013-02-14 11:43, Igor Grinberg wrote:
>
>>> True, it's generic, but does it work reliably? The panel hardware is now
>>> partly handled in the backlight driver, and partly i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/13 11:09, Tomi Valkeinen wrote:
> On 2013-02-14 10:37, Igor Grinberg wrote:
>> On 02/14/13 09:09, Tomi Valkeinen wrote:
>>> On 2013-02-14 08:56, Igor Grinberg wrote:
>>>> On 02/13/13 17:59, Tomi Valkeinen w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/14/13 09:09, Tomi Valkeinen wrote:
> On 2013-02-14 08:56, Igor Grinberg wrote:
>> On 02/13/13 17:59, Tomi Valkeinen wrote:
>
>>> Okay, so I just realized there's an spi backlight driver used here, and
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/13 17:59, Tomi Valkeinen wrote:
> On 2013-02-13 17:28, Tomi Valkeinen wrote:
>> On 2013-02-13 17:16, Igor Grinberg wrote:
>>> Hi Archit,
>>>
>>> On 02/13/13 16:21, Archit Taneja wrote:
>>>>
Hi Archit,
On 02/13/13 16:21, Archit Taneja wrote:
> The cm-t35 board file currently requests gpios required to configure the
> tdo35s
> panel, and provides platform_enable/disable callbacks to configure them.
>
> These tasks have been moved to the generic dpi panel driver itself and
> shouldn'
On 02/05/13 18:49, Jon Hunter wrote:
>
> On 02/05/2013 02:39 AM, Igor Grinberg wrote:
[...]
>>
>> Hmmm...
>> Do I miss something or you have forgot to update the commit message?
>
> Ugh you are right :-(
>
> Some how yesterday when rebasing the series a
On 02/04/13 21:46, Jon Hunter wrote:
> When booting with device-tree for OMAP3 and AM335x devices and a gptimer
> is used as the clocksource (which is always the case for AM335x), a
> gptimer located in a power domain that is not always-on is selected.
> Ideally we should use a gptimer located in a
/435
>
> Special thanks to John Stulz, Arnd Bergmann and Russell King for their
> valuable suggestions.
>
> Cc: Arnd Bergmann
> Cc: Russell King
> Cc: John Stultz
> Cc: Tony Lindgren
If it still not too late:
Acked-by: Igor Grinberg
>
> Signed-off-by: San
gt; function omap2_sync32k_timer_init() can be re-used for OMAP4/5 devices.
> Therefore, consolidate the definitions to simplify the code.
>
> Signed-off-by: Jon Hunter
Acked-by: Igor Grinberg
--
Regards,
Igor.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
y stated in the commit message.
For instance:
... it is better to use a gptimer in a power domain that is
always-on for clocksource. Therefore we switch to use the first gptimer
for clocksource and the second for clockevents.
>
> Signed-off-by: Jon Hunter
Apart from above,
Acked-by: Igor Gr
ping!
It has been 1.5 month and we are at rc4 already...
On 01/02/13 09:16, Igor Grinberg wrote:
> ping
>
> Hi Tony,
>
> This is a really small addition to improve Paul's tests coverage.
> Can this go into 3.9?
>
> Thanks
>
> On 12/07/12 11:05, Igor Grinb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It looks like Kevin has a new address:
Kevin Hilman
On 01/21/13 23:38, NeilBrown wrote:
> On Mon, 21 Jan 2013 13:38:59 +0200 Igor Grinberg
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>
>> Hi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Neil,
On 01/21/13 11:28, NeilBrown wrote:
>
>
> The standard suspend sequence involves runtime_resuming
> devices before suspending the system.
> So just saving context in runtime_suspend and restoring it
> in runtime resume isn't enough. We mu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/16/13 12:19, NeilBrown wrote:
> On Wed, 16 Jan 2013 11:28:02 +0200 Igor Grinberg
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>
>> On 01/16/13 09:26, NeilBrown wrote:
>>> On Wed, 0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/16/13 09:26, NeilBrown wrote:
> On Wed, 09 Jan 2013 14:54:00 +0200 Igor Grinberg
> wrote:
>
>> On 01/09/13 14:08, Michael Trimarchi wrote:
>>> Hi Neil
>>>
>>> I forget to answer to your questions
>&
/09/2013 11:19 AM, NeilBrown wrote:
>>>> On Wed, 09 Jan 2013 12:00:05 +0200 Igor Grinberg
>>>> wrote:
>>>>
>>>>> -BEGIN PGP SIGNED MESSAGE-
>>>>> Hash: SHA1
>>>>
>>>>> Hi Neil,
>>>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Neil,
On 01/09/13 00:29, NeilBrown wrote:
>
> Hi,
> I'm trying to get off_mode working reliably on my gta04 mobile phone.
>
> My current stumbling block is USB. The "Option" GSM module is attached via
> USB (there is a separate transceiver chip
On 01/03/13 10:38, Santosh Shilimkar wrote:
> On Thursday 03 January 2013 12:58 PM, R Sricharan wrote:
>> Hi,
>>
>> On Sunday 30 December 2012 02:13 AM, ahema...@gmail.com wrote:
>>> From: ahemaily
>>>
>>> The variable dma_lch_count used for comparison
>>> (omap_dma_reserve_channels <= dma_lch_c
ping
Hi Tony,
This is a really small addition to improve Paul's tests coverage.
Can this go into 3.9?
Thanks
On 12/07/12 11:05, Igor Grinberg wrote:
> cm-t3517 uses two MMC interfaces. Add support for both.
>
> Signed-off-by: Igor Grinberg
> ---
> v2: Use CONFIG_MMC_OMAP
Hi Stephen,
I've only now bumped into the patchset (working the back log on linux-arm).
Sorry for late reply, but I guess you should have Cc'd the relevant
mailing lists with such changes.
Cc'd now.
On 11/19/12 20:31, Stephen Warren wrote:
> From: Stephen Warren
>
> Now that the only field in s
cm-t3517 uses two MMC interfaces. Add support for both.
Signed-off-by: Igor Grinberg
---
v2: Use CONFIG_MMC_OMAP_HS instead of plain CONFIG_MMC, so it will be stubbed
out with the same defines as omap_hsmmc_init() function.
Fix the !CONFIG_MMC_OMAP_HS case.
arch/arm/mach-omap2/board-cm
cm-t3517 uses two MMC interfaces. Add support for both.
Signed-off-by: Igor Grinberg
---
arch/arm/mach-omap2/board-cm-t3517.c | 25 +
1 files changed, 25 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-cm-t3517.c
b/arch/arm/mach-omap2/board-cm
_sync32k_clocksource_init() function to indicate that this function
> may be used for certain configurations.
>
> Cc: Igor Grinberg
>
> Signed-off-by: Jon Hunter
Acked-by: Igor Grinberg
--
Regards,
Igor.
--
To unsubscribe from this list: send the line "unsubscrib
tialisation function for the AM335x
>> device as it has no 32k-sync timer.
>>
>> Fix this by only including the omap2_sync32k_clocksource_init() function
>> if either OMAP2, OMAP3, OMAP4 or OMAP5 devices are enabled.
>>
>> Cc: Igor Grinberg
>>
>> Signed-off-by: Jon Hunter
>&
MER) where the "k" is missing from the "sync32k" in
> the function name "omap4_sync32_timer_init". Therefore, correct this
> typo to resolve the above error and warning.
Yeah ;-( sorry for this...
>
> Cc: Igor Grinberg
>
> Reported-by: Tony Lin
On 11/26/12 15:15, Alessio Igor Bogani wrote:
> Hi Igor,
>
> On 26/11/2012 13:02, Igor Grinberg wrote:
>> On 11/26/12 11:28, Alessio Igor Bogani wrote:
> [...]
>>> # Common support
>>> -obj-y := sram.o dma.o fb.o counter_32k.o
>>> +obj-y :=
On 11/26/12 11:28, Alessio Igor Bogani wrote:
> The 32K timer isn't available on all OMAP devices.
>
> Signed-off-by: Alessio Igor Bogani
> ---
> arch/arm/plat-omap/Makefile |4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/plat-omap/Makefile b/arch/arm/pla
omap2_sync32k_clocksource_init() function.
Signed-off-by: Igor Grinberg
Cc: Jon Hunter
Cc: Santosh Shilimkar
Cc: Vaibhav Hiremath
Acked-by: Santosh Shilimkar
Reviewed-by: Jon Hunter
---
Compile tested on omap2plus_defconfig + crane board enabled.
This patch conflicts slightly with the:
ARM: OMAP2
Some platforms need the pendown GPIO debounce time setting programmed.
Since the pendown GPIO is handled by the driver, the debounce time
should also be handled along with the pendown GPIO request.
Signed-off-by: Igor Grinberg
---
v2: fix the comment style
drivers/input/touchscreen/ads7846.c
off-by: Igor Grinberg
Cc: Kevin Hilman
Cc: Zumeng Chen
---
arch/arm/mach-omap2/common-board-devices.c | 34 ---
1 files changed, 20 insertions(+), 14 deletions(-)
diff --git a/arch/arm/mach-omap2/common-board-devices.c
b/arch/arm/mach-omap2/common-board-devices.c
index a
Some platforms need the pendown GPIO debounce time setting programmed.
Since the pendown GPIO is handled by the driver, the debounce time
should also be handled along with the pendown GPIO request.
Signed-off-by: Igor Grinberg
---
drivers/input/touchscreen/ads7846.c |6 +-
include/linux
e OMAP platform code to pass the debounce time value
to the driver instead of handling it by itself.
Igor Grinberg (2):
ads7846: enable pendown GPIO debounce time setting
ARM: OMAP: ads7846: fix pendown debounce setting
arch/arm/mach-omap2/common-board-devices.c
__omap2_sync32k_clocksource_init() function.
Signed-off-by: Igor Grinberg
Cc: Jon Hunter
Cc: Santosh Shilimkar
Cc: Vaibhav Hiremath
---
Compile tested on omap2plus_defconfig + crane board enabled.
This patch conflicts slightly with the:
ARM: OMAP2+: Fix compiler warning for 32k timer (From Jon)
(or
cm-t3517 starting from revision 1.2 does not have the 32K oscilator
wired to the AM3517 SoC.
Therefore switch to use the GPTIMER for system clock.
Signed-off-by: Igor Grinberg
---
arch/arm/mach-omap2/board-cm-t3517.c |2 +-
arch/arm/mach-omap2/common.h |1 +
arch/arm/mach-omap2
On 11/13/12 18:13, Jon Hunter wrote:
>
> On 11/13/2012 03:14 AM, Igor Grinberg wrote:
>> On 11/12/12 21:15, Jon Hunter wrote:
>>>
>>> On 11/11/2012 05:28 AM, Igor Grinberg wrote:
>>>>
>>>>
>>>> On 11/08/12 21:16, Jon Hunter
On 11/12/12 21:15, Jon Hunter wrote:
>
> On 11/11/2012 05:28 AM, Igor Grinberg wrote:
>>
>>
>> On 11/08/12 21:16, Jon Hunter wrote:
>>>
>>> On 11/08/2012 12:59 PM, Hiremath, Vaibhav wrote:
>>>> On Fri, Nov 09, 2012 at 00:24:23, Hunter, Jon wr
On 11/12/12 21:05, Jon Hunter wrote:
>
> On 11/11/2012 03:16 AM, Igor Grinberg wrote:
>> On 11/08/12 18:20, Tony Lindgren wrote:
>>> * Igor Grinberg [121107 23:15]:
>>>> On 11/07/12 19:33, Tony Lindgren wrote:
>>>>>
>>>>> I
On 11/12/12 08:38, Hiremath, Vaibhav wrote:
> On Sun, Nov 11, 2012 at 17:05:07, Igor Grinberg wrote:
>>
>>
>> On 11/08/12 20:34, Jon Hunter wrote:
>>>
>>> On 11/08/2012 12:17 PM, Paul Walmsley wrote:
>>>> On Thu, 8 Nov 2012, Jon Hunter wrote:
>
On 11/08/12 20:34, Jon Hunter wrote:
>
> 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 no
On 11/08/12 21:16, Jon Hunter wrote:
>
> 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]
>>>
>>>>
On 11/08/12 18:16, Jon Hunter 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
On 11/08/12 18:20, Tony Lindgren wrote:
> * Igor Grinberg [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,
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 th
On 11/07/12 19:33, Tony Lindgren wrote:
> * Igor Grinberg [121107 06:44]:
>> 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 conv
__omap2_sync32k_clocksource_init()
function. Remove the #ifdef CONFIG_OMAP_32K_TIMER around the
__omap2_sync32k_clocksource_init() function.
Signed-off-by: Igor Grinberg
Cc: Jon Hunter
Cc: Santosh Shilimkar
Cc: Vaibhav Hiremath
---
Finally I'm sending this out...
I've lost follow
Cc: Tony Lindgren, Afzal Mohammed,
On 11/06/12 12:51, Matthieu CASTET wrote:
> This allow to clean the omap nand driver that were trying in x8 and x16 bits
> mode.
>
> This also make work onfi detection on beagleboard :
>
> Before :
> [1.954803] NAND device: Manufacturer ID: 0x2c, Chip ID:
On 10/23/12 20:19, Kevin Hilman wrote:
> Kevin Hilman writes:
>
>> +Igor
>>
>> Paul Walmsley writes:
>>
>>> Here are some basic OMAP test results for Linux v3.7-rc2.
>>> Logs and other details at:
>>>
>>> http://www.pwsan.com/omap/testlogs/test_v3.7-rc2/20121020134755/
>>
>> [...]
>>
>>> * 3
1 - 100 of 381 matches
Mail list logo
