Re: [PATCH 1/3] can: m_can: Make hclk optional

2017-07-20 Thread Sergei Shtylyov
Hello! On 7/20/2017 2:09 AM, Franklin S Cooper Jr 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 pm_runtime_get and pm_runtime_put calls.

Re: [PATCH 1/3] can: m_can: Make hclk optional

2017-07-20 Thread Sergei Shtylyov
Hello! On 7/20/2017 2:09 AM, Franklin S Cooper Jr 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 pm_runtime_get and pm_runtime_put calls.

[PATCH 1/3] can: m_can: Make hclk optional

2017-07-19 Thread Franklin S Cooper Jr
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 pm_runtime_get and pm_runtime_put calls. Therefore, this interface clock isn't defined in DT and thus

[PATCH 1/3] can: m_can: Make hclk optional

2017-07-19 Thread Franklin S Cooper Jr
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 pm_runtime_get and pm_runtime_put calls. Therefore, this interface clock isn't defined in DT and thus