On 10/19/2017 09:55 AM, 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 Kleine-Budde wr
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 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
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 09/20/2017 04:37 PM, Mario Hüttel wrote:
>>>>
On 09/21/2017 09:08 AM, Sekhar Nori wrote:
> 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
On 09/20/2017 04:37 PM, Mario Hüttel wrote:
>
>
> On 09/20/2017 10:19 PM, 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 Sept
sed devices to handle clock management.
>> Therefore, this allows future Texas Instruments SoCs that have the MCAN IP
>> to work with this driver.
>>
>> Signed-off-by: Franklin S Cooper Jr
>
> Thanks,
> Sekhar
>
>> ---
>> drivers/net/can/m_can/m_ca
rom it?
>
> Is there a restriction in OMAP architecture against passing the
> interface clock also in the 'clocks' property in DT. I have not tried it
> myself, but wonder if you hit an issue that led to this patch.
No but not passing the interface clock is typical.
>
similar constraints when there is an
interface and functional clock. However, I haven't seen drivers verify
that this kind of constraint is properly met. Personally I think its a
valid fault but one that can be ignored from the driver perspective.
>
> Regards
>
> Mario
>
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:
>>>
>>> On 08/18/2017 02:39 PM, Franklin S Cooper Jr wrote:
>>>> During test
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 transmitted and with a bit more investigation realized the actual
> MCAN
66AK2G has I2C instances that are not apart of the ALWAYS_ON power domain
unlike other Keystone 2 SoCs and OMAPL138. Therefore, pm_runtime
is required to insure the power domain used by the specific I2C instance is
properly turned on along with its functional clock.
Signed-off-by: Franklin S
Add pm-domains property which is required for 66AK2Gx. Also document 66AK2G
unique clocks property usage.
Signed-off-by: Franklin S Cooper Jr
Acked-by: Rob Herring
Acked-by: Sekhar Nori
---
Documentation/devicetree/bindings/i2c/i2c-davinci.txt | 12
1 file changed, 12 insertions
Version 2 changes:
Moved ordering of pm runtime calls
Version 3 changes:
Dropped first patch since it was pulled in.
Remove clk = NULL statements
Fix error path
Version 4 changes:
Fix typo in commit message
Fix error path
Franklin S Cooper Jr (2):
i2c: davinci: Add PM Runtime Support
dt
On 09/11/2017 06:29 AM, Sekhar Nori 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 ?
>
From: Murali Karicheri
K2G EVM has n25q128a13 SPI NOR flash on SPI1. Enable SPI1 in the DT
node as well as add a subnode for the SPI NOR.
Signed-off-by: Murali Karicheri
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts/keystone-k2g-evm.dts | 37 ++
1
Add pm-domains property which is required for 66AK2Gx. Also document 66AK2G
unique clocks property usage.
Signed-off-by: Franklin S Cooper Jr
---
Documentation/devicetree/bindings/spi/spi-davinci.txt | 10 ++
1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree
Update the binding document to indicate the required requirements
for 66AK2G. In addition add the proper SPI nodes for 66AK2G. For K2G
EVM enable SPI1 which is used for the on board SPI NOR.
Franklin S Cooper Jr (1):
dt-bindings: spi: spi-davinci: Update binding for 66AK2Gx pwr dm
property
From: Vitaly Andrianov
Add nodes for the various SPI instances.
Signed-off-by: Vitaly Andrianov
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts/keystone-k2g.dtsi | 48 +
1 file changed, 48 insertions(+)
diff --git a/arch/arm/boot/dts/keystone
From: Roger Quadros
Enable USB 0 which will be used as a host port and USB 1 which will be
used in peripheral mode.
Signed-off-by: Roger Quadros
Signed-off-by: Murali Karicheri
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts/keystone-k2g-evm.dts | 26 ++
1
From: Vitaly Andrianov
Add nodes for both USB instances supported by 66AK2G.
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts/keystone-k2g.dtsi | 56 +
1 file changed, 56 insertions(+)
diff --git a/arch/arm/boot/dts/keystone-k2g.dtsi
b/arch/arm
Add USB nodes to 66AK2G dtsi. Also enable the two USB nodes that are on
the K2G EVM.
Roger Quadros (1):
ARM: dts: k2g-evm: Enable USB 0 and 1
Vitaly Andrianov (1):
ARM: dts: k2g: Add USB instances
arch/arm/boot/dts/keystone-k2g-evm.dts | 26
arch/arm/boot/dts/keystone-k2g.d
From: Murali Karicheri
K2G EVM has an onboard I2C EEPROM connected to I2C0. This patch adds
the necessary DT entry for the AT24CM01 EEPROM.
Signed-off-by: Murali Karicheri
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts/keystone-k2g-evm.dts | 19 +++
1 file changed
Add I2C DT nodes for 66AK2G. Also enable I2C0 in K2G EVM which is needed
to access the I2C EEPROM.
Version 2 changes:
No real changes. Split patches into their own patchset
Murali Karicheri (1):
ARM: dts: keystone-k2g-evm: Add I2C EEPROM DT entry
Vitaly Andrianov (1):
ARM: dts: keystone-k2g
From: Vitaly Andrianov
Add nodes for the various I2C instances.
Signed-off-by: Vitaly Andrianov
Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Grygorii Strashko
---
arch/arm/boot/dts/keystone-k2g.dtsi | 36
1 file changed, 36 insertions(+)
diff --git
Version 2 changes:
Moved ordering of pm runtime calls
Version 3 changes:
Dropped first patch since it was pulled in.
Remove clk = NULL statements
Fix error path
Franklin S Cooper Jr (2):
i2c: davinci: Add PM Runtime Support
dt-bindings: i2c: i2c-davinci: Update binding for 66AK2Gx pwr dm
66AK2G has I2C instances that are not apart of the ALWAYS_ON power domain
like other Keystone 2 SoCs and OMAPL138. Therefore, pm_runtime
is required to insure the power domain used by the specific I2C instance is
properly turned on along with its functional clock.
Signed-off-by: Franklin S Cooper
Add pm-domains property which is required for 66AK2Gx. Also document 66AK2G
unique clocks property usage.
Signed-off-by: Franklin S Cooper Jr
Acked-by: Rob Herring
Acked-by: Sekhar Nori
---
Documentation/devicetree/bindings/i2c/i2c-davinci.txt | 12
1 file changed, 12 insertions
On 08/23/2017 01:34 AM, Sekhar Nori wrote:
> On Monday 21 August 2017 10:29 PM, Franklin S Cooper Jr wrote:
>>
>>
>> On 08/21/2017 07:20 AM, Sekhar Nori wrote:
>>> On Thursday 17 August 2017 02:25 AM, Franklin S Cooper Jr wrote:
>>>> 66AK2G UART inst
On 08/21/2017 04:05 AM, Sekhar Nori wrote:
> On Thursday 17 August 2017 03:47 AM, Franklin S Cooper Jr wrote:
>
>> @@ -802,7 +821,6 @@ static int davinci_i2c_probe(struct platform_device
>> *pdev)
>> dev->clk = devm_clk_get(&pdev->dev,
On 08/21/2017 07:20 AM, Sekhar Nori wrote:
> On Thursday 17 August 2017 02:25 AM, Franklin S Cooper Jr wrote:
>> 66AK2G UART instances are not apart of the ALWAYS_ON power domain.
>> Therefore, pm_runtime calls must be made to properly insure the appropriate
>> power domai
Add documentation to describe usage of the new can-transceiver binding.
This new binding is applicable for any CAN device therefore it exists as
its own document.
Signed-off-by: Franklin S Cooper Jr
Acked-by: Rob Herring
---
Version 5 changes:
Remove @ symbol from can-transceiver example
Add call to new generic functions that provides support via a binding
to limit the arbitration rate and/or data rate imposed by the physical
transceiver connected to the MCAN peripheral.
Signed-off-by: Franklin S Cooper Jr
---
drivers/net/can/m_can/m_can.c | 2 ++
1 file changed, 2 insertions
and not a property in
documentation
Version 3 changes:
Switch from having two "max bitrates" to one universal bitrate.
Version 2 changes:
Rename function
Define proper variable default
Drop unit address
Move check to changelink function
Reword commit message
Reword documentation
Fra
Add information regarding can-transceiver binding. This is especially
important for MCAN since the IP allows CAN FD mode to run significantly
faster than what most transceivers are capable of.
Signed-off-by: Franklin S Cooper Jr
Acked-by: Rob Herring
---
Remove @ symbol from can-transceiver
for a can-transceiver node that
can be reused by other CAN peripheral drivers to determine for both
CAN and CAN-FD what the max bitrate that can be used. If the user
tries to configure CAN to pass these maximum bitrates it will throw
an error.
Signed-off-by: Franklin S Cooper Jr
---
Version 5
set to (1/dbitrate)/2*(Func Clk Freq).
Additional CAN-CIA's "Bit Time Requirements for CAN FD" document indicates
that this TDC mode is only needed for data bit rates above 2.5 Mbps.
Therefore, only enable this mode and only set TDCO when the data bit rate
is above 2.5 Mbps.
Signed-off
Hi,
On 08/10/2017 10:29 AM, Marc Kleine-Budde wrote:
> Hello,
>
> sorry for stepping in late
>
> On 08/10/2017 02:59 AM, Franklin S Cooper Jr wrote:
>> Various CAN or CAN-FD IP may be able to run at a faster rate than
>> what the transceiver the CAN node is con
On 08/10/2017 05:05 AM, Sergei Shtylyov wrote:
> Hello!
>
> On 8/10/2017 3:59 AM, Franklin S Cooper Jr wrote:
>
>> Various CAN or CAN-FD IP may be able to run at a faster rate than
>> what the transceiver the CAN node is connected to. This can lead to
>> u
On 08/17/2017 07:04 AM, Felipe Balbi wrote:
>
> Hi,
>
> Franklin S Cooper Jr writes:
>> For 66AK2Gx there is a requirement to use PM Runtime to properly manage
>> clocks and the power domains. Therefore, add PM runtime support. Remove
>> legacy clock api
Version 2 changes:
Moved ordering of pm runtime calls
Franklin S Cooper Jr (3):
i2c: davinci: Preserve return value of devm_clk_get
i2c: davinci: Add PM Runtime Support
dt-bindings: i2c: i2c-davinci: Update binding for 66AK2Gx pwr dm
property
.../devicetree/bindings/i2c/i2c-davinci.txt
66AK2G has I2C instances that are not apart of the ALWAYS_ON power domain
like other Keystone 2 SoCs and OMAPL138. Therefore, pm_runtime
is required to insure the power domain used by the specific I2C instance is
properly turned on along with its functional clock.
Signed-off-by: Franklin S Cooper
Add pm-domains property which is required for 66AK2Gx. Also document 66AK2G
unique clocks property usage.
Signed-off-by: Franklin S Cooper Jr
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/i2c/i2c-davinci.txt | 12
1 file changed, 12 insertions(+)
diff --git a
devm_clk_get to be passed through and not overwritten.
Signed-off-by: Franklin S Cooper Jr
Reviewed-by: Grygorii Strashko
---
drivers/i2c/busses/i2c-davinci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-davinci.c b/drivers/i2c/busses/i2c-davinci.c
Update various properties to properly indicate their requirement depending
on the SoC.
Signed-off-by: Franklin S Cooper Jr
---
Version 2:
Clarify clock requirements in binding document
Documentation/devicetree/bindings/usb/keystone-usb.txt | 17 +++--
1 file changed, 15 insertions
Add support for 66AK2G usb instances. However, the driver needs to be updated
to support PM_RUNTIME. This update has been validated to work on K2L and boot
tested on K2HK and K2E.
Version 2:
Clarify clock properties requirements in binding document
Franklin S Cooper Jr (2):
usb: dwc3: keystone
For 66AK2Gx there is a requirement to use PM Runtime to properly manage
clocks and the power domains. Therefore, add PM runtime support. Remove
legacy clock api's calls since other users of this driver worked without
these clock apis calls.
Signed-off-by: Franklin S Cooper Jr
---
driver
66AK2G UART instances are not apart of the ALWAYS_ON power domain.
Therefore, pm_runtime calls must be made to properly insure the appropriate
power domains needed by UART are on. Keep legacy clk api calls since other
users of this driver may not support PM runtime.
Signed-off-by: Franklin S
Hi Rob,
On 08/03/2017 12:07 PM, Rob Herring wrote:
> On Mon, Jul 24, 2017 at 06:05:20PM -0500, Franklin S Cooper Jr wrote:
>> Add information regarding fixed transceiver binding. This is especially
>> important for MCAN since the IP allows CAN FD mode to run significantly
>>
Add call to new generic functions that provides support via a binding
to limit the arbitration rate and/or data rate imposed by the physical
transceiver connected to the MCAN peripheral.
Signed-off-by: Franklin S Cooper Jr
---
drivers/net/can/m_can/m_can.c | 2 ++
1 file changed, 2 insertions
itrates" to one universal bitrate.
Version 2 changes:
Rename function
Define proper variable default
Drop unit address
Move check to changelink function
Reword commit message
Reword documentation
Franklin S Cooper Jr (4):
can: dev: Add support for limiting configured bitrate
dt-bindings:
Hi Sergei,
On 08/03/2017 10:38 AM, Franklin S Cooper Jr wrote:
>
>
> On 08/03/2017 07:22 AM, Sergei Shtylyov wrote:
>> On 08/03/2017 12:48 PM, Franklin S Cooper Jr wrote:
>>
>>>>> Add documentation to describe usage of the new fixed transceiver
>
Add documentation to describe usage of the new can-transceiver binding.
This new binding is applicable for any CAN device therefore it exists as
its own document.
Signed-off-by: Franklin S Cooper Jr
---
Version 4 changes:
Drop unit address.
Switch from using fixed-transceiver to can-transceiver
Add information regarding can-transceiver binding. This is especially
important for MCAN since the IP allows CAN FD mode to run significantly
faster than what most transceivers are capable of.
Signed-off-by: Franklin S Cooper Jr
---
Drop unit address.
Switch from using fixed-transceiver to can
for a can-transceiver node that
can be reused by other CAN peripheral drivers to determine for both
CAN and CAN-FD what the max bitrate that can be used. If the user
tries to configure CAN to pass these maximum bitrates it will throw
an error.
Signed-off-by: Franklin S Cooper Jr
---
Version 4
Hi Santosh,
On 08/04/2017 12:07 PM, Santosh Shilimkar wrote:
> Hi Franklin,
>
> On 8/2/2017 1:18 PM, Franklin S Cooper Jr wrote:
>> Add D CAN nodes to 66AK2G based SoC dtsi.
>>
>> Franklin S Cooper Jr (2):
>>dt-bindings: net: c_can: Update binding for clock a
Add basic PM Runtime support.
Signed-off-by: Franklin S Cooper Jr
---
Version 2 changes:
Fix build error.
Build tested using allmodconfig
drivers/tty/serial/8250/8250_of.c | 35 ---
1 file changed, 24 insertions(+), 11 deletions(-)
diff --git a/drivers/tty
On 08/03/2017 07:22 AM, Sergei Shtylyov wrote:
> On 08/03/2017 12:48 PM, Franklin S Cooper Jr wrote:
>
>>>> Add documentation to describe usage of the new fixed transceiver
>>>> binding.
>>>> This new binding is applicable for any CAN device therefo
On 08/03/2017 04:20 AM, Sergei Shtylyov wrote:
> On 8/3/2017 3:51 AM, Franklin S Cooper Jr wrote:
>
>> Add information regarding fixed transceiver binding. This is especially
>> important for MCAN since the IP allows CAN FD mode to run significantly
>> faster than wh
On 08/03/2017 04:18 AM, Sergei Shtylyov wrote:
> Hello!
>
> On 8/3/2017 3:51 AM, Franklin S Cooper Jr wrote:
>
>> Add documentation to describe usage of the new fixed transceiver binding.
>> This new binding is applicable for any CAN device therefore it exist
Add call to new generic functions that provides support via a binding
to limit the arbitration rate and/or data rate imposed by the physical
transceiver connected to the MCAN peripheral.
Signed-off-by: Franklin S Cooper Jr
---
drivers/net/can/m_can/m_can.c | 2 ++
1 file changed, 2 insertions
for a fixed-transceiver node that
can be reused by other CAN peripheral drivers to determine for both
CAN and CAN-FD what the max bitrate that can be used. If the user
tries to configure CAN to pass these maximum bitrates it will throw
an error.
Signed-off-by: Franklin S Cooper Jr
---
drivers/net
Add information regarding fixed transceiver binding. This is especially
important for MCAN since the IP allows CAN FD mode to run significantly
faster than what most transceivers are capable of.
Signed-off-by: Franklin S Cooper Jr
---
Documentation/devicetree/bindings/net/can/m_can.txt | 9
Add documentation to describe usage of the new fixed transceiver binding.
This new binding is applicable for any CAN device therefore it exists as
its own document.
Signed-off-by: Franklin S Cooper Jr
---
.../bindings/net/can/fixed-transceiver.txt | 24 ++
1 file
r does not have to define it in their
device tree.
Version 3 changes:
Switch from having two "max bitrates" to one universal bitrate.
Version 2 changes:
Rename function
Define proper variable default
Drop unit address
Move check to changelink function
Reword commit message
Reword docum
This patch adds PM runtime support to the I2C Davinci driver.
Reviewed-by: Grygorii Strashko
Signed-off-by: Franklin S Cooper Jr
Signed-off-by: Sekhar Nori
---
drivers/i2c/busses/i2c-davinci.c | 61 ++--
1 file changed, 53 insertions(+), 8 deletions
Add pm-domains property which is required for 66AK2Gx. Also document 66AK2G
unique clocks property usage.
Signed-off-by: Franklin S Cooper Jr
---
Documentation/devicetree/bindings/i2c/i2c-davinci.txt | 12
1 file changed, 12 insertions(+)
diff --git a/Documentation/devicetree
From: Vitaly Andrianov
Add nodes for the various I2C instances.
Signed-off-by: Vitaly Andrianov
[d-gerl...@ti.com: Add power domain and clock properties]
Signed-off-by: Dave Gerlach
[fcoo...@ti.com: Update subject and commit message]
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts
devm_clk_get to be passed through and not overwritten.
Reviewed-by: Grygorii Strashko
Signed-off-by: Franklin S Cooper Jr
Signed-off-by: Sekhar Nori
---
drivers/i2c/busses/i2c-davinci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-davinci.c b/drivers
Franklin S Cooper Jr (3):
i2c: davinci: Preserve return value of devm_clk_get
i2c: davinci: Add PM Runtime Support
dt-bindings: i2c: i2c-davinci: Update binding for 66AK2Gx pwr dm
property
Vitaly Andrianov (1):
ARM: dts: keystone-k2g: Add I2C nodes
.../devicetree/bindings/i2c/i2c
Enable C_CAN/D_CAN driver supported by 66AK2G
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/configs/keystone_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/configs/keystone_defconfig
b/arch/arm/configs/keystone_defconfig
index d47ea43..47be99e 100644
--- a/arch
From: Lokesh Vutla
Add nodes for the two DCAN instances included in 66AK2G
Signed-off-by: Lokesh Vutla
[d-gerl...@ti.com: add power-domains and clock information]
Signed-off-by: Dave Gerlach
[fcoo...@ti.com: update subject and commit message. Misc minor updates]
Signed-off-by: Franklin S
Update varous properties to properly indicate their requirement depending
on the SoC.
Signed-off-by: Franklin S Cooper Jr
---
Documentation/devicetree/bindings/usb/keystone-usb.txt | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree
Add D CAN nodes to 66AK2G based SoC dtsi.
Franklin S Cooper Jr (2):
dt-bindings: net: c_can: Update binding for clock and power-domains
property
ARM: configs: keystone: Enable D_CAN driver
Lokesh Vutla (1):
ARM: dts: k2g: Add DCAN nodes
Documentation/devicetree/bindings/net/can
clocks property
require for that SoC.
66AK2G requires a new property. Therefore, update the binding to also make
this property requirement clear. Also clarify that for OMAP based SoCs
ti,hwmod is a required property.
Signed-off-by: Franklin S Cooper Jr
---
Documentation/devicetree/bindings/net/can
Add support for 66AK2G usb instances. However, the driver needs to be updated
to support PM_RUNTIME. This update has been validated to work on K2L and boot
tested on K2HK and K2E.
Franklin S Cooper Jr (2):
usb: dwc3: keystone: Add PM_RUNTIME Support to DWC3 Keystone USB
driver
dt-bindings
From: Vitaly Andrianov
Add nodes for both USB instances supported by 66AK2G.
[d-gerl...@ti.com: Add power domain and clock properties]
Signed-off-by: Dave Gerlach
[fcoo...@ti.com: Update commit message and subject]
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts/keystone-k2g.dtsi
For 66AK2Gx there is a requirement to use PM Runtime to properly manage
clocks and the power domains. Therefore, add PM runtime support. Remove
legacy clock api's calls since other users of this driver worked without
these clock apis calls.
Signed-off-by: Franklin S Cooper Jr
Signed-o
Add basic PM Runtime support.
Signed-off-by: Franklin S Cooper Jr
---
drivers/tty/serial/8250/8250_of.c | 35 ---
1 file changed, 24 insertions(+), 11 deletions(-)
diff --git a/drivers/tty/serial/8250/8250_of.c
b/drivers/tty/serial/8250/8250_of.c
index 6c5a8ca
On 07/28/2017 01:33 PM, Oliver Hartkopp wrote:
> Hi Kurt,
>
> On 07/28/2017 03:02 PM, Kurt Van Dijck wrote:
>
The word 'max-arbitration-bitrate' makes the difference very clear.
>>>
>>> I think you are mixing up ISO layer 1 and ISO layer 2.
>>
>> In order to provide higher data throughput
On 07/27/2017 01:47 PM, Oliver Hartkopp wrote:
> On 07/26/2017 08:29 PM, Franklin S Cooper Jr wrote:
>>
>
>> I'm fine with switching to using bitrate instead of speed. Kurk was
>> originally the one that suggested to use the term arbitration and data
>> si
Hi Kurt,
On 07/26/2017 03:04 PM, Kurt Van Dijck wrote:
> Hi,
>
> I know my response is late ...
>
>> Hi Oliver
>> On 07/20/2017 02:43 AM, Oliver Hartkopp wrote:
>>> Hi Franklin,
>>>
>>> On 07/20/2017 01:36 AM, Franklin S Coo
On 07/26/2017 12:05 PM, Oliver Hartkopp wrote:
> On 07/26/2017 06:41 PM, Andrew Lunn wrote:
>> On Mon, Jul 24, 2017 at 06:05:19PM -0500, Franklin S Cooper Jr wrote:
>
>>> +
>>> +Optional:
>>> + max-arbitration-speed: a positive non 0 value that determines
switch to using dma prefetch by default since
it is likely what most users would prefer.
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts/am335x-evm.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
index 1c37a7
switch to using dma prefetch by default since
it is likely what most users would prefer.
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts/am437x-gp-evm.dts | 1 +
arch/arm/boot/dts/am43x-epos-evm.dts | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/am437x-gp-
Enable NAND DMA prefetch by default for AM335x, AM437x and DRA7x evms that
include NAND.
The below commit went into additional details regarding performance numbers
seen between the two modes.
commit aa7abd312c11 ("mtd: nand: omap2: Support parsing dma channel information
from DT")
switch to using dma prefetch by default since
it is likely what most users would prefer.
Signed-off-by: Franklin S Cooper Jr
---
arch/arm/boot/dts/dra7-evm.dts | 1 +
arch/arm/boot/dts/dra72-evm-common.dtsi | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/dra7
On 07/25/2017 11:32 AM, Oliver Hartkopp wrote:
>
>> + max-data-speed:a positive non 0 value that determines the max
>> data rate
>> +that can be used in CAN-FD mode. A value of -1 implies
>> +CAN-FD is not supported by the transceiver.
>> +
>> +Examples:
>
> (..)
>
Add call to new generic functions that provides support via a binding
to limit the arbitration rate and/or data rate imposed by the physical
transceiver connected to the MCAN peripheral.
Signed-off-by: Franklin S Cooper Jr
---
drivers/net/can/m_can/m_can.c | 2 ++
1 file changed, 2 insertions
Add information regarding fixed transceiver binding. This is especially
important for MCAN since the IP allows CAN FD mode to run significantly
faster than what most transceivers are capable of.
Signed-off-by: Franklin S Cooper Jr
---
Version 2 changes:
Drop unit address
Documentation
r the user does not have to define it in their
device tree.
Version 2 changes:
Rename function
Define proper variable default
Drop unit address
Move check to changelink function
Reword commit message
Reword documentation
Franklin S Cooper Jr (4):
can: dev: Add support for limiting configured bit
Add documentation to describe usage of the new fixed transceiver binding.
This new binding is applicable for any CAN device therefore it exists as
its own document.
Signed-off-by: Franklin S Cooper Jr
---
Version 2:
Tweak commit message working
Tweak wording for properties
Drop unit addressing
for a fixed-transceiver node that
can be reused by other CAN peripheral drivers to determine for both
CAN and CAN-FD what the max bitrate that can be used. If the user
tries to configure CAN to pass these maximum bitrates it will throw
an error.
Signed-off-by: Franklin S Cooper Jr
---
Version 2
T
and thus the driver shouldn't fail if this clock isn't found.
Signed-off-by: Franklin S Cooper Jr
---
Version 2 changes:
Used NULL instead of 0 for unused hclk handle
drivers/net/can/m_can/m_can.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/net
Add PM runtime support to the MCAN driver. To support devices that don't
use PM runtime leave the original clk calls in the driver. Perhaps in the
future when it makes sense we can remove these non pm runtime clk calls.
Version 2 changes:
Used NULL instead of 0 for unused hclk handle
Frank
SoCs that have the MCAN IP
to work with this driver.
Signed-off-by: Franklin S Cooper Jr
---
drivers/net/can/m_can/m_can.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/net/can/m_can/m_can.c b/drivers/net/can/m_can/m_can.c
index ea48e59..93e23f5 100644
--- a/drivers
Update the documentation to reflect that hclk is now an optional clock.
Signed-off-by: Franklin S Cooper Jr
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/net/can/m_can.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/net
On 07/20/2017 04:52 AM, Sergei Shtylyov wrote:
> Hello!
>
> On 7/20/2017 2:36 AM, Franklin S Cooper Jr wrote:
>
>> Various CAN or CAN-FD IP may be able to run at a faster rate than
>> what the transceiver the CAN node is connected to. This can lead to
>> u
Hi Oliver
On 07/20/2017 02:43 AM, Oliver Hartkopp wrote:
> Hi Franklin,
>
> On 07/20/2017 01:36 AM, Franklin S Cooper Jr wrote:
>
>> +#ifdef CONFIG_OF
>> +void of_transceiver_is_fixed(struct net_device *dev)
>> +{
>
> (..)
>
>> +}
>>
for a fixed-transceiver node that
can be reused by other CAN peripheral drivers to determine for both
CAN and CAN-FD what the max bitrate that can be used. If the user
tries to configure CAN to pass these maximum bitrates it will throw
an error.
Signed-off-by: Franklin S Cooper Jr
---
drivers/net
Add call to new generic functions that provides support via a binding
to limit the arbitration rate and/or data rate imposed by the physical
transceiver connected to the MCAN peripheral.
Signed-off-by: Franklin S Cooper Jr
---
drivers/net/can/m_can/m_can.c | 2 ++
1 file changed, 2 insertions
1 - 100 of 376 matches
Mail list logo
