On Thursday 11 January 2018 06:15 PM, Adam Ford wrote:
> On Wed, Jan 10, 2018 at 8:50 PM, David Lechner wrote:
>> On 01/10/2018 04:24 PM, Adam Ford wrote:
>>>
>>>
>>> I am available tomorrow to build and test patches against the
>>> da850-evm. I just need to know which version(s) to test.
>>
>>
On Wednesday 10 January 2018 08:31 AM, David Lechner wrote:
> On 01/09/2018 06:35 AM, Sekhar Nori wrote:
>> On Monday 08 January 2018 09:59 PM, David Lechner wrote:
>>> On 01/08/2018 08:00 AM, Sekhar Nori wrote:
>>>> On Monday 08 January 2018 07:47 AM, David Le
On Wednesday 10 January 2018 08:31 AM, David Lechner wrote:
> On 01/09/2018 06:35 AM, Sekhar Nori wrote:
>> On Monday 08 January 2018 09:59 PM, David Lechner wrote:
>>> On 01/08/2018 08:00 AM, Sekhar Nori wrote:
>>>> On Monday 08 January 2018 07:47 AM, David Le
On Sunday 07 January 2018 08:40 AM, David Lechner wrote:
> This series moves the watchdog restart code from arch/arm/mach-davinci
> to drivers/watchdog.
>
> Tested working on LEGO MINDSTORMS EV3 (TI AM1808 processor).
>
> v2 changes:
> * rebased on linux-davinci/master (fixed conflict with
On Sunday 07 January 2018 08:40 AM, David Lechner wrote:
> This series moves the watchdog restart code from arch/arm/mach-davinci
> to drivers/watchdog.
>
> Tested working on LEGO MINDSTORMS EV3 (TI AM1808 processor).
>
> v2 changes:
> * rebased on linux-davinci/master (fixed conflict with
On Monday 08 January 2018 09:59 PM, David Lechner wrote:
> On 01/08/2018 08:00 AM, Sekhar Nori wrote:
>> On Monday 08 January 2018 07:47 AM, David Lechner wrote:
>>> This adds a new binding for the PLL IP blocks in the mach-davinci family
>>> of processors. Currently,
On Monday 08 January 2018 09:59 PM, David Lechner wrote:
> On 01/08/2018 08:00 AM, Sekhar Nori wrote:
>> On Monday 08 January 2018 07:47 AM, David Lechner wrote:
>>> This adds a new binding for the PLL IP blocks in the mach-davinci family
>>> of processors. Currently,
On Monday 08 January 2018 07:47 AM, David Lechner wrote:
> This adds a new binding for the PLL IP blocks in the mach-davinci family
> of processors. Currently, only the SYSCLKn and AUXCLK outputs are needed,
> but in the future additional child nodes could be added for OBSCLK and
> BPDIV.
>
>
On Monday 08 January 2018 07:47 AM, David Lechner wrote:
> This adds a new binding for the PLL IP blocks in the mach-davinci family
> of processors. Currently, only the SYSCLKn and AUXCLK outputs are needed,
> but in the future additional child nodes could be added for OBSCLK and
> BPDIV.
>
>
On Saturday 06 January 2018 07:12 AM, David Lechner wrote:
> On 01/05/2018 04:42 AM, Sekhar Nori wrote:
>> On Friday 05 January 2018 08:29 AM, David Lechner wrote:
>>> On 01/04/2018 11:50 AM, David Lechner wrote:
>>>> On 1/4/18 6:39 AM, Sekhar Nori wrote:
>>
>
On Saturday 06 January 2018 07:12 AM, David Lechner wrote:
> On 01/05/2018 04:42 AM, Sekhar Nori wrote:
>> On Friday 05 January 2018 08:29 AM, David Lechner wrote:
>>> On 01/04/2018 11:50 AM, David Lechner wrote:
>>>> On 1/4/18 6:39 AM, Sekhar Nori wrote:
>>
>
On Wednesday 27 December 2017 08:21 PM, Julia Lawall wrote:
> gpio_request uses its second argument as a label, so it doesn't seem
> appropriate for it to have a newline. Done using Coccinelle.
>
> Signed-off-by: Julia Lawall
Applied to my v4.16/soc branch
Thanks,
Sekhar
On Wednesday 27 December 2017 08:21 PM, Julia Lawall wrote:
> gpio_request uses its second argument as a label, so it doesn't seem
> appropriate for it to have a newline. Done using Coccinelle.
>
> Signed-off-by: Julia Lawall
Applied to my v4.16/soc branch
Thanks,
Sekhar
On Friday 05 January 2018 08:29 AM, David Lechner wrote:
> On 01/04/2018 11:50 AM, David Lechner wrote:
>> On 1/4/18 6:39 AM, Sekhar Nori wrote:
>>> This is a pretty huge patch again and I hope it can be broken down.
>>> Ideally one per SoC converted and t
On Friday 05 January 2018 08:29 AM, David Lechner wrote:
> On 01/04/2018 11:50 AM, David Lechner wrote:
>> On 1/4/18 6:39 AM, Sekhar Nori wrote:
>>> This is a pretty huge patch again and I hope it can be broken down.
>>> Ideally one per SoC converted and t
.
commit aad70de20fc69970a3080e7e8f02b54a4a3fe3e6
Author: Sekhar Nori <nsek...@ti.com>
AuthorDate: Wed Jul 6 06:01:22 2011 +0000
Commit: Sekhar Nori <nsek...@ti.com>
CommitDate: Fri Jul 8 11:10:09 2011 +0530
davinci: enable forced transitions on PSC
Some DaVinci modules like the SATA on DA850
nee
.
commit aad70de20fc69970a3080e7e8f02b54a4a3fe3e6
Author: Sekhar Nori
AuthorDate: Wed Jul 6 06:01:22 2011 +
Commit: Sekhar Nori
CommitDate: Fri Jul 8 11:10:09 2011 +0530
davinci: enable forced transitions on PSC
Some DaVinci modules like the SATA on DA850
need forced module state transitions.
Define
On Monday 01 January 2018 05:09 AM, David Lechner wrote:
> This converts all of arch/arm/mach-davinci to the common clock framework.
> The clock drivers from clock.c and psc.c have been moved to drivers/clk,
> so these files are removed.
>
> There is one subtle change in the clock trees. AUX,
On Monday 01 January 2018 05:09 AM, David Lechner wrote:
> This converts all of arch/arm/mach-davinci to the common clock framework.
> The clock drivers from clock.c and psc.c have been moved to drivers/clk,
> so these files are removed.
>
> There is one subtle change in the clock trees. AUX,
On Wednesday 03 January 2018 03:01 AM, David Lechner wrote:
> Forgot to cc linux-clk, so doing that now...
>
>
> On 12/31/2017 05:39 PM, David Lechner wrote:
>> This introduces new drivers for arch/arm/mach-davinci. The code is based
>> on the clock drivers from there and adapted to use the
On Wednesday 03 January 2018 03:01 AM, David Lechner wrote:
> Forgot to cc linux-clk, so doing that now...
>
>
> On 12/31/2017 05:39 PM, David Lechner wrote:
>> This introduces new drivers for arch/arm/mach-davinci. The code is based
>> on the clock drivers from there and adapted to use the
On Monday 01 January 2018 05:09 AM, David Lechner wrote:
> There are a number of clocks that were duplicated because they are used by
> more than one device. It is no longer necessary to do this since we are
> explicitly calling clk_register_clkdev() for each clock. In da830.c, some
> clocks were
On Monday 01 January 2018 05:09 AM, David Lechner wrote:
> There are a number of clocks that were duplicated because they are used by
> more than one device. It is no longer necessary to do this since we are
> explicitly calling clk_register_clkdev() for each clock. In da830.c, some
> clocks were
Hi David,
On Monday 01 January 2018 05:09 AM, David Lechner wrote:
> In preparation of moving to the common clock framework, usage of static
> struct clk_lookup is removed. The common clock framework uses an opaque
> struct clk, so we won't be able to use static tables as was previously
> done.
>
Hi David,
On Monday 01 January 2018 05:09 AM, David Lechner wrote:
> In preparation of moving to the common clock framework, usage of static
> struct clk_lookup is removed. The common clock framework uses an opaque
> struct clk, so we won't be able to use static tables as was previously
> done.
>
On Tuesday 02 January 2018 08:40 PM, Adam Ford wrote:
> On Sun, Dec 31, 2017 at 5:39 PM, David Lechner wrote:
>> This series converts macreqh-davinci to use the common clock framework.
>>
>> Basically, this series does some cleanup and rearranging to get things
>> ready for
On Tuesday 02 January 2018 08:40 PM, Adam Ford wrote:
> On Sun, Dec 31, 2017 at 5:39 PM, David Lechner wrote:
>> This series converts macreqh-davinci to use the common clock framework.
>>
>> Basically, this series does some cleanup and rearranging to get things
>> ready for the conversion. Then
ff-by: Atul Garg <ag...@arasan.com>
Apart from the comments given by Adrian, looks good to me.
Reviewed-by: Sekhar Nori <nsek...@ti.com>
Regards,
Sekhar
ff-by: Atul Garg
Apart from the comments given by Adrian, looks good to me.
Reviewed-by: Sekhar Nori
Regards,
Sekhar
On Wednesday 20 December 2017 02:17 PM, Arvind Yadav wrote:
> gpio_led are not supposed to change at runtime.
> struct gpio_led_platform_data working with const gpio_led
> provided by . So mark the non-const structs
> as const.
>
> Signed-off-by: Arvind Yadav
This
On Wednesday 20 December 2017 02:17 PM, Arvind Yadav wrote:
> gpio_led are not supposed to change at runtime.
> struct gpio_led_platform_data working with const gpio_led
> provided by . So mark the non-const structs
> as const.
>
> Signed-off-by: Arvind Yadav
This causes a new section mismatch
On Wednesday 20 December 2017 04:42 AM, David Lechner wrote:
> On 12/19/2017 07:47 AM, Sekhar Nori wrote:
>> Hi David,
>>
>> On Saturday 09 December 2017 07:45 AM, David Lechner wrote:
>>> This converts the clocks in mach-davinci to the common clock framework.
On Wednesday 20 December 2017 04:42 AM, David Lechner wrote:
> On 12/19/2017 07:47 AM, Sekhar Nori wrote:
>> Hi David,
>>
>> On Saturday 09 December 2017 07:45 AM, David Lechner wrote:
>>> This converts the clocks in mach-davinci to the common clock framework.
Hi David,
On Saturday 09 December 2017 07:45 AM, David Lechner wrote:
> This converts the clocks in mach-davinci to the common clock framework.
>
> Most of the patch just involves renaming struct clk to struct davinci_clk.
> There is also a struct clk_hw added to provide the bridge between the
>
Hi David,
On Saturday 09 December 2017 07:45 AM, David Lechner wrote:
> This converts the clocks in mach-davinci to the common clock framework.
>
> Most of the patch just involves renaming struct clk to struct davinci_clk.
> There is also a struct clk_hw added to provide the bridge between the
>
Hi David,
On Monday 11 December 2017 10:51 PM, David Lechner wrote:
> This series moves the watchdog restart code from arch/arm/mach-davinci
> to drivers/watchdog.
>
> Tested working on LEGO MINDSTORMS EV3 (TI AM1808 processor).
The patches look good to me. I also tested them on
Hi David,
On Monday 11 December 2017 10:51 PM, David Lechner wrote:
> This series moves the watchdog restart code from arch/arm/mach-davinci
> to drivers/watchdog.
>
> Tested working on LEGO MINDSTORMS EV3 (TI AM1808 processor).
The patches look good to me. I also tested them on
On Friday 15 December 2017 06:16 PM, Mathieu Malaterre wrote:
> Improve the DTS files by removing all the leading "0x" and zeros to fix the
> following dtc warnings:
>
> Warning (unit_address_format): Node /XXX unit name should not have leading
> "0x"
>
> and
>
> Warning (unit_address_format):
On Friday 15 December 2017 06:16 PM, Mathieu Malaterre wrote:
> Improve the DTS files by removing all the leading "0x" and zeros to fix the
> following dtc warnings:
>
> Warning (unit_address_format): Node /XXX unit name should not have leading
> "0x"
>
> and
>
> Warning (unit_address_format):
On Saturday 02 December 2017 08:04 AM, David Lechner wrote:
> static int dm355leopard_mmc_get_cd(int module)
> {
> if (!gpio_is_valid(leopard_mmc_gpio))
> @@ -269,7 +264,7 @@ static __init void dm355_leopard_init(void)
>
> MACHINE_START(DM355_LEOPARD, "DaVinci DM355 leopard")
>
On Saturday 02 December 2017 08:04 AM, David Lechner wrote:
> static int dm355leopard_mmc_get_cd(int module)
> {
> if (!gpio_is_valid(leopard_mmc_gpio))
> @@ -269,7 +264,7 @@ static __init void dm355_leopard_init(void)
>
> MACHINE_START(DM355_LEOPARD, "DaVinci DM355 leopard")
>
On Thursday 07 December 2017 10:44 PM, David Lechner wrote:
> On 12/07/2017 08:52 AM, Sekhar Nori wrote:
>> On Saturday 02 December 2017 08:04 AM, David Lechner wrote:
>>> This cleans up the map_io functions in the board init files for
>>> mach-davinci.
>>>
On Thursday 07 December 2017 10:44 PM, David Lechner wrote:
> On 12/07/2017 08:52 AM, Sekhar Nori wrote:
>> On Saturday 02 December 2017 08:04 AM, David Lechner wrote:
>>> This cleans up the map_io functions in the board init files for
>>> mach-davinci.
>>>
On Friday 08 December 2017 04:05 PM, Alejandro Mery wrote:
> fix mmc entries in dm365's dma_slave_map to match the actual device names
>
> Fixes: 0c750e1fe481 ("ARM: davinci: dm365: Add dma_slave_map to edma")
> Signed-off-by: Alejandro Mery
Applied to fixes branch of
On Friday 08 December 2017 04:05 PM, Alejandro Mery wrote:
> fix mmc entries in dm365's dma_slave_map to match the actual device names
>
> Fixes: 0c750e1fe481 ("ARM: davinci: dm365: Add dma_slave_map to edma")
> Signed-off-by: Alejandro Mery
Applied to fixes branch of my tree.
Thanks,
Sekhar
On Saturday 02 December 2017 08:04 AM, David Lechner wrote:
> This cleans up the map_io functions in the board init files for
> mach-davinci.
>
> Most of the boards had a wrapper function around _init(). This
> wrapper is removed and the function is used directly. Additionally, the
> _init()
On Saturday 02 December 2017 08:04 AM, David Lechner wrote:
> This cleans up the map_io functions in the board init files for
> mach-davinci.
>
> Most of the boards had a wrapper function around _init(). This
> wrapper is removed and the function is used directly. Additionally, the
> _init()
On Monday 04 December 2017 03:34 AM, David Lechner wrote:
> This fixes the battery voltage monitoring gpio-hog settings.
>
> When the gpio is low, it turns off the battery voltage to the ADC chip.
> However, this needs to be on all of the time so that we can monitor
> battery voltage.
>
> Also,
On Monday 04 December 2017 03:34 AM, David Lechner wrote:
> This fixes the battery voltage monitoring gpio-hog settings.
>
> When the gpio is low, it turns off the battery voltage to the ADC chip.
> However, this needs to be on all of the time so that we can monitor
> battery voltage.
>
> Also,
On Tuesday 28 November 2017 04:33 AM, Vasyl Gomonovych wrote:
> Fix ptr_ret.cocci warnings:
> arch/arm/mach-davinci/devices-da8xx.c:255:8-14: WARNING: PTR_ERR_OR_ZERO can
> be used
> arch/arm/mach-davinci/devices-da8xx.c:300:8-14: WARNING: PTR_ERR_OR_ZERO can
> be used
>
On Tuesday 28 November 2017 04:33 AM, Vasyl Gomonovych wrote:
> Fix ptr_ret.cocci warnings:
> arch/arm/mach-davinci/devices-da8xx.c:255:8-14: WARNING: PTR_ERR_OR_ZERO can
> be used
> arch/arm/mach-davinci/devices-da8xx.c:300:8-14: WARNING: PTR_ERR_OR_ZERO can
> be used
>
mi...@gmail.com>
[nsek...@ti.com: minor commit message adjustment]
Signed-off-by: Sekhar Nori <nsek...@ti.com>
"
With that I applied the patch to v4.16/fixes-non-critical
Thanks,
Sekhar
inci_common_init having the argument as const or their field
cpu_clks of type struct clk_lookup * is passed to the function
davinci_clk_init.
So, the fields are never modified and the structures can be const.
Done using Coccinelle.
Signed-off-by: Bhumika Goyal
[nsek...@ti.com: minor commit m
On Monday 16 October 2017 03:38 PM, Bhumika Goyal wrote:
> Make the function argument of the function davinci_common_init
> as const as it's memory contents are only copied during a
> memcpy call. So, the fields of the structure to which the argument
> soc_info points to never gets modified and
On Monday 16 October 2017 03:38 PM, Bhumika Goyal wrote:
> Make the function argument of the function davinci_common_init
> as const as it's memory contents are only copied during a
> memcpy call. So, the fields of the structure to which the argument
> soc_info points to never gets modified and
On Monday 06 November 2017 12:29 PM, Keerthy wrote:
>
>
> On Monday 06 November 2017 12:25 PM, Sekhar Nori wrote:
>> + linux omap list
>>
>> On Tuesday 31 October 2017 09:57 PM, Alexandre Belloni wrote:
>>> Register an nvmem device to expose the 3 scra
On Monday 06 November 2017 12:29 PM, Keerthy wrote:
>
>
> On Monday 06 November 2017 12:25 PM, Sekhar Nori wrote:
>> + linux omap list
>>
>> On Tuesday 31 October 2017 09:57 PM, Alexandre Belloni wrote:
>>> Register an nvmem device to expose the 3 scra
Looks good to me.
Reviewed-by: Sekhar Nori <nsek...@ti.com>
Curious on what you are using these registers for.
Thanks,
Sekhar
> ---
> drivers/rtc/rtc-omap.c | 45 +
> 1 file changed, 45 insertions(+)
>
> diff --git a/drivers/
+ linux omap list
On Tuesday 31 October 2017 09:57 PM, Alexandre Belloni wrote:
> Register an nvmem device to expose the 3 scratch registers (total of 12
> bytes) to both userspace and kernel space.
>
> Signed-off-by: Alexandre Belloni
Looks good to me.
Reviewed-by: Sekhar No
On Thursday 19 October 2017 08:25 PM, Marc Kleine-Budde wrote:
> On 10/19/2017 03:54 PM, Franklin S Cooper Jr wrote:
>> On 10/19/2017 06:32 AM, Marc Kleine-Budde wrote:
>>> On 10/19/2017 01:09 PM, Sekhar Nori wrote:
>>>> On Thursday 19 October 2017 02:43 PM, Marc Klei
On Thursday 19 October 2017 08:25 PM, Marc Kleine-Budde wrote:
> On 10/19/2017 03:54 PM, Franklin S Cooper Jr wrote:
>> On 10/19/2017 06:32 AM, Marc Kleine-Budde wrote:
>>> On 10/19/2017 01:09 PM, Sekhar Nori wrote:
>>>> On Thursday 19 October 2017 02:43 PM, Marc Klei
On Thursday 19 October 2017 02:43 PM, Marc Kleine-Budde wrote:
> On 10/19/2017 07:07 AM, Sekhar Nori wrote:
>>>>> Sounds reasonable. What's the status of this series?
>>>>
>>>> I have had some offline discussions with Franklin on this, and I am not
>
On Thursday 19 October 2017 02:43 PM, Marc Kleine-Budde wrote:
> On 10/19/2017 07:07 AM, Sekhar Nori wrote:
>>>>> Sounds reasonable. What's the status of this series?
>>>>
>>>> I have had some offline discussions with Franklin on this, and I am not
>
On Wednesday 18 October 2017 07:47 PM, Franklin S Cooper Jr wrote:
>
>
> On 10/18/2017 08:24 AM, Sekhar Nori wrote:
>> Hi Marc,
>>
>> On Wednesday 18 October 2017 06:14 PM, Marc Kleine-Budde wrote:
>>> On 09/21/2017 02:48 AM, Franklin S Cooper Jr wrote:
&
On Wednesday 18 October 2017 07:47 PM, Franklin S Cooper Jr wrote:
>
>
> On 10/18/2017 08:24 AM, Sekhar Nori wrote:
>> Hi Marc,
>>
>> On Wednesday 18 October 2017 06:14 PM, Marc Kleine-Budde wrote:
>>> On 09/21/2017 02:48 AM, Franklin S Cooper Jr wrote:
&
>>>> Hi Wenyou,
>>>>
>>>> On 09/17/2017 10:47 PM, Yang, Wenyou wrote:
>>>>>
>>>>> On 2017/9/14 13:06, Sekhar Nori wrote:
>>>>>> On Thursday 14 September 2017 03:28 AM, Franklin S Cooper Jr wrote:
>>>>>>
>>>> Hi Wenyou,
>>>>
>>>> On 09/17/2017 10:47 PM, Yang, Wenyou wrote:
>>>>>
>>>>> On 2017/9/14 13:06, Sekhar Nori wrote:
>>>>>> On Thursday 14 September 2017 03:28 AM, Franklin S Cooper Jr wrote:
>>>>>>
Hi Atul,
On Tuesday 10 October 2017 11:12 PM, Atul Garg wrote:
> The Arasan controller is based on a FPGA platform and has integrated phy
> with specific phy registers used during the initialization and
> management of different modes. The phy and the controller are integrated
> and registers are
Hi Atul,
On Tuesday 10 October 2017 11:12 PM, Atul Garg wrote:
> The Arasan controller is based on a FPGA platform and has integrated phy
> with specific phy registers used during the initialization and
> management of different modes. The phy and the controller are integrated
> and registers are
Hi David,
On Friday 22 September 2017 10:13 PM, David Lechner wrote:
> On 09/22/2017 11:24 AM, Suman Anna wrote:
>> Hi Sekhar,
>>
>>>
>>> On Thursday 21 September 2017 08:41 PM, Suman Anna wrote:
>>>> On 09/21/2017 09:43 AM, Sekhar Nori wrote:
>>
Hi David,
On Friday 22 September 2017 10:13 PM, David Lechner wrote:
> On 09/22/2017 11:24 AM, Suman Anna wrote:
>> Hi Sekhar,
>>
>>>
>>> On Thursday 21 September 2017 08:41 PM, Suman Anna wrote:
>>>> On 09/21/2017 09:43 AM, Sekhar Nori wrote:
>>
On Friday 22 September 2017 09:54 PM, Suman Anna wrote:
> Hi Sekhar,
>
>>
>> On Thursday 21 September 2017 08:41 PM, Suman Anna wrote:
>>> On 09/21/2017 09:43 AM, Sekhar Nori wrote:
>>>> On Wednesday 20 September 2017 11:31 PM, Suman Anna wrote:
>>&
On Friday 22 September 2017 09:54 PM, Suman Anna wrote:
> Hi Sekhar,
>
>>
>> On Thursday 21 September 2017 08:41 PM, Suman Anna wrote:
>>> On 09/21/2017 09:43 AM, Sekhar Nori wrote:
>>>> On Wednesday 20 September 2017 11:31 PM, Suman Anna wrote:
>>&
On Tuesday 26 September 2017 05:35 AM, Viresh Kumar wrote:
> The drivers/base/power/ directory is special and contains code related
> to power management core like system suspend/resume, hibernation, etc.
> It was fine to keep the OPP code inside it when we had just one file for
> it, but it is
On Tuesday 26 September 2017 05:35 AM, Viresh Kumar wrote:
> The drivers/base/power/ directory is special and contains code related
> to power management core like system suspend/resume, hibernation, etc.
> It was fine to keep the OPP code inside it when we had just one file for
> it, but it is
Hi Suman,
On Thursday 21 September 2017 08:41 PM, Suman Anna wrote:
> On 09/21/2017 09:43 AM, Sekhar Nori wrote:
>> On Wednesday 20 September 2017 11:31 PM, Suman Anna wrote:
>>> Enable the CMA and DMA_CMA Kconfig options by default for
>>> Davinci platforms. Davin
Hi Suman,
On Thursday 21 September 2017 08:41 PM, Suman Anna wrote:
> On 09/21/2017 09:43 AM, Sekhar Nori wrote:
>> On Wednesday 20 September 2017 11:31 PM, Suman Anna wrote:
>>> Enable the CMA and DMA_CMA Kconfig options by default for
>>> Davinci platforms. Davin
On Wednesday 20 September 2017 11:31 PM, Suman Anna wrote:
> Enable the CMA and DMA_CMA Kconfig options by default for
> Davinci platforms. Davinci remoteproc driver is one of the
> modules that depends on these options, and this allows the
> driver to be made visible for selection with
On Wednesday 20 September 2017 11:31 PM, Suman Anna wrote:
> Enable the CMA and DMA_CMA Kconfig options by default for
> Davinci platforms. Davinci remoteproc driver is one of the
> modules that depends on these options, and this allows the
> driver to be made visible for selection with
On Thursday 21 September 2017 06:01 AM, Franklin S Cooper Jr wrote:
>
>
> On 08/24/2017 03:00 AM, Sekhar Nori wrote:
>> + some OMAP folks and Linux OMAP list
>>
>> On Tuesday 25 July 2017 04:21 AM, Franklin Cooper wrote:
>>> Hclk is the MCAN's interface cl
On Thursday 21 September 2017 06:01 AM, Franklin S Cooper Jr wrote:
>
>
> On 08/24/2017 03:00 AM, Sekhar Nori wrote:
>> + some OMAP folks and Linux OMAP list
>>
>> On Tuesday 25 July 2017 04:21 AM, Franklin Cooper wrote:
>>> Hclk is the MCAN's interface cl
Hi Suman,
On Tuesday 19 September 2017 05:58 AM, Suman Anna wrote:
> Hi Sekhar,
>
> The following series adds the DT node for the DSP device present on
> on DA850/OMAPL138 SoCs. The node is disabled in the base dts file, and
> enabled in the corresponding LCDK board file alongside the reserved
>
Hi Suman,
On Tuesday 19 September 2017 05:58 AM, Suman Anna wrote:
> Hi Sekhar,
>
> The following series adds the DT node for the DSP device present on
> on DA850/OMAPL138 SoCs. The node is disabled in the base dts file, and
> enabled in the corresponding LCDK board file alongside the reserved
>
ments
> Fix error path
>
> Version 4 changes:
> Fix typo in commit message
> Fix error path
Acked-by: Sekhar Nori <nsek...@ti.com>
Tested on DA850 LCDK board with some basic i2cdetect/i2cdump and
suspend/resume tests.
Thanks,
Sekhar
ments
> Fix error path
>
> Version 4 changes:
> Fix typo in commit message
> Fix error path
Acked-by: Sekhar Nori
Tested on DA850 LCDK board with some basic i2cdetect/i2cdump and
suspend/resume tests.
Thanks,
Sekhar
On Thursday 14 September 2017 03:28 AM, Franklin S Cooper Jr wrote:
>
>
> On 08/18/2017 02:39 PM, Franklin S Cooper Jr wrote:
>> During test transmitting using CAN-FD at high bitrates (4 Mbps) only
>> resulted in errors. Scoping the signals I noticed that only a single bit
>> was being
On Thursday 14 September 2017 03:28 AM, Franklin S Cooper Jr wrote:
>
>
> On 08/18/2017 02:39 PM, Franklin S Cooper Jr wrote:
>> During test transmitting using CAN-FD at high bitrates (4 Mbps) only
>> resulted in errors. Scoping the signals I noticed that only a single bit
>> was being
On Tuesday 12 September 2017 02:44 PM, Baolin Wang wrote:
> Hi,
>
> On 12 September 2017 at 16:48, Sekhar Nori <nsek...@ti.com> wrote:
>> On Tuesday 12 September 2017 07:28 AM, Baolin Wang wrote:
>>>> @@ -802,13 +821,24 @@ static int davinci_i2c_probe(s
On Tuesday 12 September 2017 02:44 PM, Baolin Wang wrote:
> Hi,
>
> On 12 September 2017 at 16:48, Sekhar Nori wrote:
>> On Tuesday 12 September 2017 07:28 AM, Baolin Wang wrote:
>>>> @@ -802,13 +821,24 @@ static int davinci_i2c_probe(struct platform_device
>&g
On Tuesday 12 September 2017 07:28 AM, Baolin Wang wrote:
>> @@ -802,13 +821,24 @@ static int davinci_i2c_probe(struct platform_device
>> *pdev)
>> dev->clk = devm_clk_get(>dev, NULL);
>> if (IS_ERR(dev->clk))
>> return PTR_ERR(dev->clk);
>> -
On Tuesday 12 September 2017 07:28 AM, Baolin Wang wrote:
>> @@ -802,13 +821,24 @@ static int davinci_i2c_probe(struct platform_device
>> *pdev)
>> dev->clk = devm_clk_get(>dev, NULL);
>> if (IS_ERR(dev->clk))
>> return PTR_ERR(dev->clk);
>> -
On Tuesday 12 September 2017 01:41 AM, Grygorii Strashko wrote:
>
>
> On 09/11/2017 03:07 PM, Franklin S Cooper Jr wrote:
>>
>>
>> On 09/11/2017 06:29 AM, Sekhar Nori wrote:
>>> On Friday 08 September 2017 11:24 PM, Franklin S Cooper Jr wrote:
>>>
On Tuesday 12 September 2017 01:41 AM, Grygorii Strashko wrote:
>
>
> On 09/11/2017 03:07 PM, Franklin S Cooper Jr wrote:
>>
>>
>> On 09/11/2017 06:29 AM, Sekhar Nori wrote:
>>> On Friday 08 September 2017 11:24 PM, Franklin S Cooper Jr wrote:
>>>
On Friday 08 September 2017 11:24 PM, Franklin S Cooper Jr wrote:
> 66AK2G has I2C instances that are not apart of the ALWAYS_ON power domain
> like other Keystone 2 SoCs and OMAPL138. Therefore, pm_runtime
unlike ?
> is required to insure the power domain used by the specific I2C instance is
>
On Friday 08 September 2017 11:24 PM, Franklin S Cooper Jr wrote:
> 66AK2G has I2C instances that are not apart of the ALWAYS_ON power domain
> like other Keystone 2 SoCs and OMAPL138. Therefore, pm_runtime
unlike ?
> is required to insure the power domain used by the specific I2C instance is
>
On Friday 01 September 2017 08:37 PM, Adam Ford wrote:
> At the request of Sekhar Nori from TI, this is a follow-up to
This can be:
Suggested-by: Sekhar Nori <nsek...@ti.com>
> pending ("ARM: dts: da850-evm: add serial and ethernet aliases")
Any patch dependency refer
On Friday 01 September 2017 08:37 PM, Adam Ford wrote:
> At the request of Sekhar Nori from TI, this is a follow-up to
This can be:
Suggested-by: Sekhar Nori
> pending ("ARM: dts: da850-evm: add serial and ethernet aliases")
Any patch dependency references need to go bel
+ OMAP mailing list
On Tuesday 25 July 2017 04:21 AM, Franklin Cooper wrote:
> Add support for PM Runtime which is the new way to handle managing clocks.
> However, to avoid breaking SoCs not using PM_RUNTIME leave the old clk
> management approach in place.
Since hclk is the interface clock, I
+ OMAP mailing list
On Tuesday 25 July 2017 04:21 AM, Franklin Cooper wrote:
> Add support for PM Runtime which is the new way to handle managing clocks.
> However, to avoid breaking SoCs not using PM_RUNTIME leave the old clk
> management approach in place.
Since hclk is the interface clock, I
+ some OMAP folks and Linux OMAP list
On Tuesday 25 July 2017 04:21 AM, Franklin Cooper wrote:
> Hclk is the MCAN's interface clock. However, for OMAP based devices such as
> DRA7 SoC family the interface clock is handled by hwmod. Therefore, this
> interface clock is managed by hwmod driver via
601 - 700 of 2392 matches
Mail list logo