Hi Daniel,
On 10/1/20 10:48 AM, Daniel Vetter wrote:
On Wed, Sep 30, 2020 at 01:53:46PM +0200, Alexandre Bailon wrote:
This adds a RPMsg driver that implements communication between the CPU and an
APU.
This uses VirtIO buffer to exchange messages but for sharing data, this uses
a dmabuf
This adds a driver to communicate with the APU available
in the mt8183. The driver is generic and could be used for other APU.
It mostly provides a userspace interface to send messages and
and share big buffers with the APU.
Signed-off-by: Alexandre Bailon
---
drivers/rpmsg/Kconfig
In order to reduce the memory mapping operations we are going to
add an IOCTL to request a mapping.
To make easier to add this new operation, use 2 lists to store the
mappings, one for the request and one for the device.
Signed-off-by: Alexandre Bailon
---
drivers/rpmsg/apu_rpmsg.c | 104
.
Signed-off-by: Alexandre Bailon
---
drivers/rpmsg/apu_rpmsg.c | 52 ++
include/uapi/linux/apu_rpmsg.h | 7 +
2 files changed, 53 insertions(+), 6 deletions(-)
diff --git a/drivers/rpmsg/apu_rpmsg.c b/drivers/rpmsg/apu_rpmsg.c
index 343bd08a859a..4c064feddf5a
From: Julien STEPHAN
In order to improve performances and flexibility,
add support of async request.
Signed-off-by: Julien STEPHAN
Signed-off-by: Alexandre Bailon
---
drivers/rpmsg/apu_rpmsg.c | 208 ++---
include/uapi/linux/apu_rpmsg.h | 6 +-
2 files
hardware accelerator for AI if they use support remoteproc and VirtIO.
For the people interested by the firmware or userspace library,
the sources are available here:
https://github.com/BayLibre/open-amp/tree/v2020.01-mtk/apps/examples/apu
Alexandre Bailon (3):
Add a RPMSG driver for the APU
The DSP could be debugged using JTAG.
The support of JTAG could enabled at build time and it could be enabled
using debugfs.
Signed-off-by: Alexandre Bailon
---
drivers/remoteproc/Kconfig | 9 +++
drivers/remoteproc/mtk_apu.c | 151 ++-
2 files changed, 159
This adds a driver to control the APU present in the MT8183.
This loads the firmware and start the DSP.
Signed-off-by: Alexandre Bailon
---
drivers/remoteproc/Kconfig | 10 ++
drivers/remoteproc/Makefile | 1 +
drivers/remoteproc/mtk_apu.c | 288 +++
3
This adds the support of APU to mt8183.
Signed-off-by: Alexandre Bailon
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 39
1 file changed, 39 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
index
This adds dt bindings for the APU present in the MT8183.
Signed-off-by: Alexandre Bailon
---
.../bindings/remoteproc/mtk,apu.yaml | 107 ++
1 file changed, 107 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/mtk,apu.yaml
diff --git
to use pinctl for JTAG
- fix some minors issues
- fix device tree bindings
Alexandre Bailon (4):
dt bindings: remoteproc: Add bindings for MT8183 APU
remoteproc: Add a remoteproc driver for the MT8183's APU
remoteproc: mtk_vpu_rproc: Add support of JTAG
ARM64: mt8183: Add support of APU
Hi Mathieu,
On 7/21/20 12:17 AM, Mathieu Poirier wrote:
On Mon, Jul 13, 2020 at 03:29:23PM +0200, Alexandre Bailon wrote:
This adds a driver to control the APU present in the MT8183.
This loads the firmware and start the DSP.
Signed-off-by: Alexandre Bailon
---
drivers/remoteproc/Kconfig
On 7/21/20 9:52 PM, Mathieu Poirier wrote:
On Mon, Jul 13, 2020 at 03:29:24PM +0200, Alexandre Bailon wrote:
The DSP could be debugged using JTAG.
The support of JTAG could enabled at build time and it could be enabled
using debugfs.
Signed-off-by: Alexandre Bailon
---
drivers/remoteproc
The DSP could be debugged using JTAG.
The support of JTAG could enabled at build time and it could be enabled
using debugfs.
Signed-off-by: Alexandre Bailon
---
drivers/remoteproc/Kconfig | 9 ++
drivers/remoteproc/mtk_apu_rproc.c | 156 -
2 files changed
This adds a driver to control the APU present in the MT8183.
This loads the firmware and start the DSP.
Signed-off-by: Alexandre Bailon
---
drivers/remoteproc/Kconfig | 10 +
drivers/remoteproc/Makefile| 1 +
drivers/remoteproc/mtk_apu_rproc.c | 308
section).
Because of that issue, the current driver doesn't map the the local RAM.
Alexandre Bailon (6):
dt bindings: remoteproc: Add bindings for MT8183 APU
remoteproc: Add a remoteproc driver for the MT8183's APU
remoteproc: mtk_vpu_rproc: Add support of JTAG
remoteproc: mtk_vpu_rproc
y, the elf load won't try to load the segment.
Signed-off-by: Alexandre Bailon
---
drivers/remoteproc/mtk_apu_rproc.c | 35 +++---
1 file changed, 32 insertions(+), 3 deletions(-)
diff --git a/drivers/remoteproc/mtk_apu_rproc.c
b/drivers/remoteproc/mtk_apu_rpr
This adds the support of APU to mt8183.
Signed-off-by: Alexandre Bailon
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 42
1 file changed, 42 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
index
This adds dt bindings for the APU present in the MT8183.
Signed-off-by: Alexandre Bailon
---
.../bindings/remoteproc/mtk,apu.yaml | 121 ++
1 file changed, 121 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/mtk,apu.yaml
diff --git
Currently, this local RAM is not accessible from the CPU.
If the CPU tries to access it, then the CPU will hang.
Remoteproc may try to use it when it load a firmware
that has some sections in the local RAM.
This workarounds the issue by skiping this section.
Signed-off-by: Alexandre Bailon
Hi Mike,
On 3/15/19 5:17 PM, Michael Turquette wrote:
Hi Alex,
Some nitpick review comments below.
On Wed, Mar 13, 2019 at 12:33 PM Alexandre Bailon wrote:
This series implements busfreq, a framework used in MXP's
s/MXP/NXP/
tree to scale the interconnect and dram frequencies
Hi Aisheng
On 3/15/19 3:39 AM, Aisheng Dong wrote:
+Jacky and Leonard, Ranjani
Hi Alexandre,
From: Alexandre Bailon [mailto:abai...@baylibre.com]
This series implements busfreq, a framework used in MXP's tree to scale the
interconnect and dram frequencies.
In the vendor tree, device's
request for
bandwidth which is use by busfreq to determine a performance level,
and then scale the frequency.
Busfreq platform drivers just have to registers interconnect nodes,
and OPPs.
Signed-off-by: Alexandre Bailon
---
drivers/interconnect/Kconfig | 1 +
drivers/interconnect/Makefile
, it won't be hard make it work.
As exemple, this series implements busfreq for
Alexandre Bailon (3):
drivers: interconnect: Add a driver for i.MX SoC
drivers: interconnect: imx: Add support of i.MX8MM
dt-bindings: interconnect: Document fsl,busfreq-imx8mm bindings
.../bindings/interconnect
Document the device-tree bindings interconnect driver for i.MX8MM SoC.
Signed-off-by: Alexandre Bailon
---
.../bindings/interconnect/imx8mm.txt | 24 +++
1 file changed, 24 insertions(+)
create mode 100644 Documentation/devicetree/bindings/interconnect/imx8mm.txt
diff
This adds a platform driver for the i.MX8MM SoC.
Signed-off-by: Alexandre Bailon
---
drivers/interconnect/imx/Kconfig | 4 +
drivers/interconnect/imx/Makefile | 1 +
drivers/interconnect/imx/busfreq-imx8mm.c | 132 ++
include/dt-bindings/interconnect
Hi Georgi,
Sorry for the late response, I have just seen today that you have
reviewed my patch.
On 1/21/19 6:41 PM, Georgi Djakov wrote:
Thank you for working on this! I am expecting the next version.
I'm going to send a new patchset soon.
I have rewritten pretty much everything, to handle
Hi Dong Aisheng,
On 07/26/2018 03:50 AM, A.s. Dong wrote:
> Hi Stephen,
>
> Do you have a chance to look at it?
> This patch series has been pending for quite a long time without much
> comments.
I'm not a kernel maintainer but I would not review a series that has
checkpatch errors.
Please run
Hi Dong Aisheng,
On 07/26/2018 03:50 AM, A.s. Dong wrote:
> Hi Stephen,
>
> Do you have a chance to look at it?
> This patch series has been pending for quite a long time without much
> comments.
I'm not a kernel maintainer but I would not review a series that has
checkpatch errors.
Please run
On 07/09/2018 05:50 PM, Georgi Djakov wrote:
> This patch introduces a new API to get requirements and configure the
> interconnect buses across the entire chipset to fit with the current
> demand.
>
> The API is using a consumer/provider-based model, where the providers are
> the interconnect
On 07/09/2018 05:50 PM, Georgi Djakov wrote:
> This patch introduces a new API to get requirements and configure the
> interconnect buses across the entire chipset to fit with the current
> demand.
>
> The API is using a consumer/provider-based model, where the providers are
> the interconnect
On 07/09/2018 05:51 PM, Georgi Djakov wrote:
> Add driver for the Qualcomm interconnect buses found in msm8916 based
> platforms.
>
> Signed-off-by: Georgi Djakov
> ---
> drivers/interconnect/Kconfig| 5 +
> drivers/interconnect/Makefile | 1 +
>
On 07/09/2018 05:51 PM, Georgi Djakov wrote:
> Add driver for the Qualcomm interconnect buses found in msm8916 based
> platforms.
>
> Signed-off-by: Georgi Djakov
> ---
> drivers/interconnect/Kconfig| 5 +
> drivers/interconnect/Makefile | 1 +
>
Hi Georgi,
On 07/09/2018 05:50 PM, Georgi Djakov wrote:
> This patch introduces a new API to get requirements and configure the
> interconnect buses across the entire chipset to fit with the current
> demand.
>
> The API is using a consumer/provider-based model, where the providers are
> the
Hi Georgi,
On 07/09/2018 05:50 PM, Georgi Djakov wrote:
> This patch introduces a new API to get requirements and configure the
> interconnect buses across the entire chipset to fit with the current
> demand.
>
> The API is using a consumer/provider-based model, where the providers are
> the
On 03/09/2018 10:09 PM, Georgi Djakov wrote:
> This patch introduce a new API to get requirements and configure the
> interconnect buses across the entire chipset to fit with the current
> demand.
>
> The API is using a consumer/provider-based model, where the providers are
> the interconnect
On 03/09/2018 10:09 PM, Georgi Djakov wrote:
> This patch introduce a new API to get requirements and configure the
> interconnect buses across the entire chipset to fit with the current
> demand.
>
> The API is using a consumer/provider-based model, where the providers are
> the interconnect
This adds the device tree node for the usb otg
controller present in the da850 family of SoC's.
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
---
arch/arm/boot/dts/da850.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/bo
This adds the device tree node for the usb otg
controller present in the da850 family of SoC's.
Signed-off-by: Alexandre Bailon
---
arch/arm/boot/dts/da850.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi
index
This enables the usb otg controller for the lcdk board.
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
---
arch/arm/boot/dts/da850-lcdk.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/da850-lcdk.dts b/arch/arm/boot/dts/da850-lcdk.dts
index 7
This enables the usb otg controller for the lcdk board.
Signed-off-by: Alexandre Bailon
---
arch/arm/boot/dts/da850-lcdk.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/da850-lcdk.dts b/arch/arm/boot/dts/da850-lcdk.dts
index 7b8ab21..03f9bfd 100644
--- a/arch
ted the patch in two: one for the board and one for the SoC.
Alexandre Bailon (2):
ARM: dts: da850: Add the usb otg device node
ARM: dts: da850-lcdk: Enable the usb otg device node
arch/arm/boot/dts/da850-lcdk.dts | 8
arch/arm/boot/dts/da850.dtsi | 10 ++
2 files ch
ted the patch in two: one for the board and one for the SoC.
Alexandre Bailon (2):
ARM: dts: da850: Add the usb otg device node
ARM: dts: da850-lcdk: Enable the usb otg device node
arch/arm/boot/dts/da850-lcdk.dts | 8
arch/arm/boot/dts/da850.dtsi | 10 ++
2 files ch
From: Petr Kulhavy <p...@barix.com>
DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver.
Signed-off-by: Petr Kulhavy <p...@barix.com>
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
Acked-by: Rob Herring <r...@kernel.org>
---
.../devicetree/bi
From: Petr Kulhavy <p...@barix.com>
This adds the function musb_get_mode() to get the DT property "dr_mode"
Signed-off-by: Petr Kulhavy <p...@barix.com>
Acked-by: Sergei Shtylyov <sshtyl...@ru.mvista.com>
Signed-off-by: Alexandre Bailon <abai...@baylibre.co
From: Petr Kulhavy
DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver.
Signed-off-by: Petr Kulhavy
Signed-off-by: Alexandre Bailon
Acked-by: Rob Herring
---
.../devicetree/bindings/usb/da8xx-usb.txt | 43 ++
1 file changed, 43 insertions(+)
create
From: Petr Kulhavy
This adds the function musb_get_mode() to get the DT property "dr_mode"
Signed-off-by: Petr Kulhavy
Acked-by: Sergei Shtylyov
Signed-off-by: Alexandre Bailon
Tested-by: David Lechner
Reviewed-by: Kevin Hilman
---
drivers/usb/musb/musb_c
From: Petr Kulhavy <p...@barix.com>
This adds DT support for TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver
Signed-off-by: Petr Kulhavy <p...@barix.com>
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
Tested-by: David Lechner <da...@lechnology.com>
---
drive
Changes in v2:
* Remove unrelated changes in patch 3
* Rename the device node in patch 4
Changes in v3:
* Fix few mistakes in DT binding sample
* Only build the device table if DT is enabled
Change in v4:
* Fix a nit
Changes in v5:
* Nothing. Resent the v4 in two seppaated series: one for
From: Petr Kulhavy
This adds DT support for TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver
Signed-off-by: Petr Kulhavy
Signed-off-by: Alexandre Bailon
Tested-by: David Lechner
---
drivers/usb/musb/da8xx.c | 46 ++
1 file changed, 46 insertions
Changes in v2:
* Remove unrelated changes in patch 3
* Rename the device node in patch 4
Changes in v3:
* Fix few mistakes in DT binding sample
* Only build the device table if DT is enabled
Change in v4:
* Fix a nit
Changes in v5:
* Nothing. Resent the v4 in two seppaated series: one for
On 11/16/2016 11:41 AM, Sekhar Nori wrote:
> On Wednesday 16 November 2016 04:05 PM, Alexandre Bailon wrote:
>> On 11/15/2016 11:46 AM, Sekhar Nori wrote:
>>> On Thursday 03 November 2016 09:29 PM, Alexandre Bailon wrote:
>>>> This adds the device tree node for the u
On 11/16/2016 11:41 AM, Sekhar Nori wrote:
> On Wednesday 16 November 2016 04:05 PM, Alexandre Bailon wrote:
>> On 11/15/2016 11:46 AM, Sekhar Nori wrote:
>>> On Thursday 03 November 2016 09:29 PM, Alexandre Bailon wrote:
>>>> This adds the device tree node for the u
On 11/15/2016 11:46 AM, Sekhar Nori wrote:
> On Thursday 03 November 2016 09:29 PM, Alexandre Bailon wrote:
>> This adds the device tree node for the usb otg
>> controller present in the da850 family of SoC's.
>> This also enables the otg usb controller for the lcdk bo
On 11/15/2016 11:46 AM, Sekhar Nori wrote:
> On Thursday 03 November 2016 09:29 PM, Alexandre Bailon wrote:
>> This adds the device tree node for the usb otg
>> controller present in the da850 family of SoC's.
>> This also enables the otg usb controller for the lcdk bo
The DA8xx OTG PHY has some issues when it is forced in host or
peripheral mode. Actually, most of the time, OTG is the best mode
because host or peripheral mode are only required for hardware that
miss some circuitry.
Init the PHY mode OTG mode by default.
Signed-off-by: Alexandre Bailon <a
The DA8xx OTG PHY has some issues when it is forced in host or
peripheral mode. Actually, most of the time, OTG is the best mode
because host or peripheral mode are only required for hardware that
miss some circuitry.
Init the PHY mode OTG mode by default.
Signed-off-by: Alexandre Bailon
() is called from
init.
Changes in v6:
* Remove the patch that was adding a new parametter to musb_platform_set_mode().
Instead, use the variable is_initialized.
* The patch fixing the phy has been merged to phy-next, so I removed it from
this series.
Alexandre Bailon (2):
usb: musb: da8xx
() is called from
init.
Changes in v6:
* Remove the patch that was adding a new parametter to musb_platform_set_mode().
Instead, use the variable is_initialized.
* The patch fixing the phy has been merged to phy-next, so I removed it from
this series.
Alexandre Bailon (2):
usb: musb: da8xx
The first attempt to read a register may fail because the clock may not
be enabled, and then the probe of musb driver will fail.
Call clk_prepare_enable() before the first register read.
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
---
drivers/usb/musb/da8xx.c | 17 --
The first attempt to read a register may fail because the clock may not
be enabled, and then the probe of musb driver will fail.
Call clk_prepare_enable() before the first register read.
Signed-off-by: Alexandre Bailon
---
drivers/usb/musb/da8xx.c | 17 -
1 file changed, 8
On 11/14/2016 06:36 PM, Bin Liu wrote:
> Hi,
>
> On Mon, Nov 07, 2016 at 02:05:07PM +0100, Alexandre Bailon wrote:
>> During the init, the driver will use musb_platform_set_mode()
>> to configure the controller mode and the PHY mode.
>> The PHY of DA8xx has some is
On 11/14/2016 06:36 PM, Bin Liu wrote:
> Hi,
>
> On Mon, Nov 07, 2016 at 02:05:07PM +0100, Alexandre Bailon wrote:
>> During the init, the driver will use musb_platform_set_mode()
>> to configure the controller mode and the PHY mode.
>> The PHY of DA8xx has some is
.
Changes in v5:
* Add the init argument to musb_platform_set_mode() and set_mode() callback.
* Remove the quirk
* Configure the DA8xx phy in OTG mode if da8xx_musb_set_mode() is called from
init.
Alexandre Bailon (4):
usb: musb: da8xx: Call earlier clk_prepare_enable()
phy: da8xx-usb: Configure
.
Changes in v5:
* Add the init argument to musb_platform_set_mode() and set_mode() callback.
* Remove the quirk
* Configure the DA8xx phy in OTG mode if da8xx_musb_set_mode() is called from
init.
Alexandre Bailon (4):
usb: musb: da8xx: Call earlier clk_prepare_enable()
phy: da8xx-usb: Configure
argument to musb_platform_set_mode() in order to let the
callback change its behavior if it is called during the init.
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
---
drivers/usb/musb/am35x.c | 2 +-
drivers/usb/musb/blackfin.c | 2 +-
drivers/usb/musb/da8xx.c | 2 +-
d
The first attempt to read a register may fail because the clock may not
be enabled, and then the probe of musb driver will fail.
Call clk_prepare_enable() before the first register read.
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
---
drivers/usb/musb/da8xx.c | 17 --
argument to musb_platform_set_mode() in order to let the
callback change its behavior if it is called during the init.
Signed-off-by: Alexandre Bailon
---
drivers/usb/musb/am35x.c | 2 +-
drivers/usb/musb/blackfin.c | 2 +-
drivers/usb/musb/da8xx.c | 2 +-
drivers/usb/musb/davinci.c
The first attempt to read a register may fail because the clock may not
be enabled, and then the probe of musb driver will fail.
Call clk_prepare_enable() before the first register read.
Signed-off-by: Alexandre Bailon
---
drivers/usb/musb/da8xx.c | 17 -
1 file changed, 8
The DA8xx OTG PHY has some issues when it is forced in host or
peripheral mode. Actually, most of the time, OTG is the best mode
because host or peripheral mode are only required for hardware that
miss some circuitry.
Init the PHY mode OTG mode by default.
Signed-off-by: Alexandre Bailon <a
require the VBUS sense and the session end
comparator to enabled.
Enable them if the phy is configured in OTG mode.
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
---
drivers/phy/phy-da8xx-usb.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/phy/phy-da8xx-usb.c b/drive
require the VBUS sense and the session end
comparator to enabled.
Enable them if the phy is configured in OTG mode.
Signed-off-by: Alexandre Bailon
---
drivers/phy/phy-da8xx-usb.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/phy/phy-da8xx-usb.c b/drivers/phy/phy-da8xx-usb.c
index
The DA8xx OTG PHY has some issues when it is forced in host or
peripheral mode. Actually, most of the time, OTG is the best mode
because host or peripheral mode are only required for hardware that
miss some circuitry.
Init the PHY mode OTG mode by default.
Signed-off-by: Alexandre Bailon
.
Alexandre Bailon (4):
usb: musb: da8xx: Call earlier clk_prepare_enable()
phy: da8xx-usb: Configure CFGCHIP2 to support OTG workaround
usb: musb: Add a quirk flag to skip the phy set mode
usb: musb: da8xx: Set phy in OTG mode by default
drivers/phy/phy-da8xx-usb.c | 20
.
Alexandre Bailon (4):
usb: musb: da8xx: Call earlier clk_prepare_enable()
phy: da8xx-usb: Configure CFGCHIP2 to support OTG workaround
usb: musb: Add a quirk flag to skip the phy set mode
usb: musb: da8xx: Set phy in OTG mode by default
drivers/phy/phy-da8xx-usb.c | 20
The first attempt to read a register may fail because the clock may not
be enabled, and then the probe of musb driver will fail.
Call clk_prepare_enable() before the first register read.
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
---
drivers/usb/musb/da8xx.c | 17 --
During the init, the driver will use the mode to configure
the controller mode and the phy mode.
The PHY of DA8xx has some issues when the phy is forced in host or device.
Add way to skip the set mode and let the da8xx glue manage the phy mode.
Signed-off-by: Alexandre Bailon <a
require the VBUS sense and the session end
comparator to enabled.
Enable them if the phy is configured in OTG mode.
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
---
drivers/phy/phy-da8xx-usb.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/phy/phy-da8xx-usb.c b/drive
The DA8xx OTG PHY has some issues when it is forced in host or
peripheral mode. Actually, most of the time, OTG is the best mode
because host or peripheral mode are only required for hardware that
miss some circuitry.
Init the PHY mode OTG mode by default.
Signed-off-by: Alexandre Bailon <a
The first attempt to read a register may fail because the clock may not
be enabled, and then the probe of musb driver will fail.
Call clk_prepare_enable() before the first register read.
Signed-off-by: Alexandre Bailon
---
drivers/usb/musb/da8xx.c | 17 -
1 file changed, 8
During the init, the driver will use the mode to configure
the controller mode and the phy mode.
The PHY of DA8xx has some issues when the phy is forced in host or device.
Add way to skip the set mode and let the da8xx glue manage the phy mode.
Signed-off-by: Alexandre Bailon
---
drivers/usb
require the VBUS sense and the session end
comparator to enabled.
Enable them if the phy is configured in OTG mode.
Signed-off-by: Alexandre Bailon
---
drivers/phy/phy-da8xx-usb.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/phy/phy-da8xx-usb.c b/drivers/phy/phy-da8xx-usb.c
index
The DA8xx OTG PHY has some issues when it is forced in host or
peripheral mode. Actually, most of the time, OTG is the best mode
because host or peripheral mode are only required for hardware that
miss some circuitry.
Init the PHY mode OTG mode by default.
Signed-off-by: Alexandre Bailon
On 11/03/2016 06:50 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Thursday 03 November 2016 10:56 PM, Alexandre Bailon wrote:
>> On 11/03/2016 05:34 PM, Kishon Vijay Abraham I wrote:
>>> Hi,
>>>
>>> On Thursday 03 November 2016 08:56 PM, Alexan
On 11/03/2016 06:50 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Thursday 03 November 2016 10:56 PM, Alexandre Bailon wrote:
>> On 11/03/2016 05:34 PM, Kishon Vijay Abraham I wrote:
>>> Hi,
>>>
>>> On Thursday 03 November 2016 08:56 PM, Alexan
On 11/03/2016 06:27 PM, Bin Liu wrote:
> On Thu, Nov 03, 2016 at 12:18:53PM -0500, David Lechner wrote:
>> On 11/03/2016 10:26 AM, Alexandre Bailon wrote:
>>> The USB PHY is able to operate in OTG, host or peripheral.
>>> Some board may be wired to work act
On 11/03/2016 06:27 PM, Bin Liu wrote:
> On Thu, Nov 03, 2016 at 12:18:53PM -0500, David Lechner wrote:
>> On 11/03/2016 10:26 AM, Alexandre Bailon wrote:
>>> The USB PHY is able to operate in OTG, host or peripheral.
>>> Some board may be wired to work act
On 11/03/2016 05:53 PM, David Lechner wrote:
> On 11/03/2016 10:26 AM, Alexandre Bailon wrote:
>> The USB PHY is able to operate in OTG, host or peripheral.
>> Some board may be wired to work act only as host or peripheral.
>> In such case, the dr_mode property of controller m
On 11/03/2016 05:53 PM, David Lechner wrote:
> On 11/03/2016 10:26 AM, Alexandre Bailon wrote:
>> The USB PHY is able to operate in OTG, host or peripheral.
>> Some board may be wired to work act only as host or peripheral.
>> In such case, the dr_mode property of controller m
On 11/03/2016 05:34 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Thursday 03 November 2016 08:56 PM, Alexandre Bailon wrote:
>> The USB PHY is able to operate in OTG, host or peripheral.
>> Some board may be wired to work act only as host or peripheral.
>> In such
On 11/03/2016 05:34 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Thursday 03 November 2016 08:56 PM, Alexandre Bailon wrote:
>> The USB PHY is able to operate in OTG, host or peripheral.
>> Some board may be wired to work act only as host or peripheral.
>> In such
Changes in v2:
* Remove unrelated changes in patch 3
* Rename the device node in patch 4
Changes in v3:
* Fix few mistakes in DT binding sample
* Only build the device table if DT is enabled
Change in v4:
* Fix a nit
Alexandre Bailon (1):
ARM: dts: da850: Add the usb otg device node
Petr
Changes in v2:
* Remove unrelated changes in patch 3
* Rename the device node in patch 4
Changes in v3:
* Fix few mistakes in DT binding sample
* Only build the device table if DT is enabled
Change in v4:
* Fix a nit
Alexandre Bailon (1):
ARM: dts: da850: Add the usb otg device node
Petr
From: Petr Kulhavy <p...@barix.com>
This adds DT support for TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver
Signed-off-by: Petr Kulhavy <p...@barix.com>
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
Tested-by: David Lechner <da...@lechnology.com>
---
drive
From: Petr Kulhavy
This adds DT support for TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver
Signed-off-by: Petr Kulhavy
Signed-off-by: Alexandre Bailon
Tested-by: David Lechner
---
drivers/usb/musb/da8xx.c | 46 ++
1 file changed, 46 insertions
From: Petr Kulhavy <p...@barix.com>
This adds the function musb_get_mode() to get the DT property "dr_mode"
Signed-off-by: Petr Kulhavy <p...@barix.com>
Acked-by: Sergei Shtylyov <sshtyl...@ru.mvista.com>
Signed-off-by: Alexandre Bailon <abai...@baylibre.co
From: Petr Kulhavy
This adds the function musb_get_mode() to get the DT property "dr_mode"
Signed-off-by: Petr Kulhavy
Acked-by: Sergei Shtylyov
Signed-off-by: Alexandre Bailon
Tested-by: David Lechner
Reviewed-by: Kevin Hilman
---
drivers/usb/musb/musb_c
From: Petr Kulhavy <p...@barix.com>
DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver.
Signed-off-by: Petr Kulhavy <p...@barix.com>
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
Acked-by: Rob Herring <r...@kernel.org>
---
.../devicetree/bi
From: Petr Kulhavy
DT binding for the TI DA8xx/OMAP-L1x/AM17xx/AM18xx MUSB driver.
Signed-off-by: Petr Kulhavy
Signed-off-by: Alexandre Bailon
Acked-by: Rob Herring
---
.../devicetree/bindings/usb/da8xx-usb.txt | 43 ++
1 file changed, 43 insertions(+)
create
This adds the device tree node for the usb otg
controller present in the da850 family of SoC's.
This also enables the otg usb controller for the lcdk board.
Signed-off-by: Alexandre Bailon <abai...@baylibre.com>
---
arch/arm/boot/dts/da850-lcdk.dts | 8
arch/arm/boot/dts/da85
1 - 100 of 189 matches
Mail list logo
