On 05/20/2014 08:09 PM, Joachim Eastwood wrote:
> On 20 May 2014 16:25, Florian Vaussard wrote:
>> Add the necessary DTS nodes to enable the micro-HDMI output on Parlor
>> board.
>>
>> Signed-off-by: Florian Vaussard
>> ---
>> arch/arm/boot/dts/omap4-duovero-parlor.dts | 42
>>
On 21/05/14 11:14, Florian Vaussard wrote:
>> I think Parlor has one and the "hdmi-connector" binding now supports
>> it. See Tomi's 3.16/fbdev-omap branch.
>>
>
> Looking into the details, the HPD pin of the parlor board is connected
> to the OMAP4 HDMI IP. The LINK_CONNECT and LINK_DISCONNECT e
On 05/21/2014 10:26 AM, Tomi Valkeinen wrote:
> On 21/05/14 11:14, Florian Vaussard wrote:
>
>>> I think Parlor has one and the "hdmi-connector" binding now
>>> supports it. See Tomi's 3.16/fbdev-omap branch.
>>>
>>
>> Looking into the details, the HPD pin of the parlor board is
>> connected to
Add the necessary DTS nodes to enable the micro-HDMI output on Parlor
board.
Signed-off-by: Florian Vaussard
---
v1->v2:
- Rebased on Tony's omap-for-v3.16/dt-v2
- Use OMAP4_IOPAD macro
- Use hpd pin as GPIO with hdmi-connector
arch/arm/boot/dts/omap4-duovero-parlor.dts | 44 +++
On Mon, May 19, 2014 at 10:42:31PM +0200, Alexandre Belloni wrote:
> Hi,
>
> Originally sent on Apr 14th, note that this series is blocking another 16
> patches series, I would like it to be taken in 3.16 if we can agree on this
> implementation.
>
> A patch set as suggested by Thierry to make lo
On Tue, 20 May 2014, Tony Lindgren wrote:
> * Lee Jones [140520 08:18]:
> >
> > Ah, I forgot to Ack this last time, didn't I?
> >
> > Acked-by: Lee Jones
>
> Yeah, here's this one updated with your ack.
Has the code changed at all, or are you just reposting with my Ack
applied?
> 8< -
> Here's an updated set of patches to enable low-power idle modes
> for some omap3 boards when booted with device tree.
>
> This series when applied on top of the patches in tread
>
>
> "[PATCH
On 9 May 2014 18:46, Balaji T K wrote:
> v2:
> use devm_ioremap_resource
> add cmd23 multiblock read/write fix
>
> Balaji T K (6):
> mmc: omap_hsmmc: use devm_clk_get
> mmc: omap_hsmmc: use devm_request_irq
> mmc: omap_hsmmc: use devm_request_threaded_irq
> mmc: omap_hsmmc: use devm_iorema
On 15 May 2014 15:23, Balaji T K wrote:
> Debounce clock is optional, use IS_ERR macro instead of NULL pointer check.
>
> Signed-off-by: Balaji T K
Thanks Balaji,
I will include this in the next PR I send to Chris.
Kind regards
Ulf Hansson
--
To unsubscribe from this list: send the line "unsub
Kernel: vanilla 3.15-rc5
kexec: latest git (21.05.2014)
I can load the zImage + dtb from u-boot, but invoking kexec prints
following data and nothing happens after "Bye!":
# kexec -d -f --dtb=/mnt/boot/am335x-evmsk.dtb /mnt/boot/zImage
kernel: 0xb5eab008 kernel_size: 0x2036c
kexec_load: entry = 0
The NAND controller must be a child node of the Chip select (CS) node.
NAND specific parameters are moved to the NAND node.
Move NAND specific device tree parsing to NAND driver.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/gpmc.c | 183 +--
dri
The beagle board contains a 16-bit NAND device connected to
chip select 0 of the GPMC controller.
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap3-beagle.dts | 66 ++
1 file changed, 66 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
b/
Copy all the platform data parameters to the driver's local data
structure 'omap_nand_info' and use it in the entire driver. This will
make it easer for device tree migration.
Signed-off-by: Roger Quadros
---
drivers/mtd/nand/omap2.c | 27 ++-
1 file changed, 18 insertion
Fix the following warning when CONFIG_MTD_NAND_OMAP_BCH is disabled.
warning: ‘erased_sector_bitflips’ defined but not used [-Wunused-function]
Signed-off-by: Roger Quadros
---
drivers/mtd/nand/omap2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/omap2.c b
Since the Interrupt Events are used only by the NAND driver,
there is no point in managing the Interrupt registers
in the GPMC driver and complicating it with irqchip modeling.
Let's manage the interrupt registers directly in the NAND driver
and get rid of irqchip model from GPMC driver.
Get rid
Add compatible id and other mandatory properties.
Remove deprecated 'elm_id' property as it is no longer used.
Update usage example.
Signed-off-by: Roger Quadros
---
.../devicetree/bindings/mtd/gpmc-nand.txt | 86 +++---
1 file changed, 42 insertions(+), 44 deletions(-)
Provide NAND specific resources and platform data.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/gpmc.c | 77 ++
1 file changed, 77 insertions(+)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
index 26b26ec..f4ee6e9 100644
The write protect (WP) pin is only used for NAND devices. So move
the code into the NAND driver.
Get rid of gpmc_configure() and gpmc_write_reg() as they are no longer
used.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/gpmc.c | 42
arch/arm
This function should only be called by board init code for
legacy boot.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/gpmc-nand.c | 79 -
1 file changed, 14 insertions(+), 65 deletions(-)
diff --git a/arch/arm/mach-omap2/gpmc-nand.c b/arch/arm/mach
Add gpmc_probe_legacy() that will be called for non DT boots. This function
will use platform data to setup each chip select and populate the child
platform device for each of the chip selects.
Re-arrange init order so that gpmc device is created after
the gpmc platform data is initialized by boar
Add device_timings, gpmc_timings and gpmc_setting to
gpmc platform data.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/gpmc.h | 125 --
include/linux/platform_data/gpmc-omap.h | 131
2 files changed, 131 insertions(
This will make it easier to move the GPMC driver out of arch/arm/mach-omap2.
Just the context save/restore code can remain there without any dependency
with the GPMC driver.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/gpmc.c | 121 +++--
arch/arm/
Add a platform data structure for GPMC. It contains all the necessary
platform information that needs to be passed from platform init code
to GPMC driver.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/gpmc.h | 4 +---
include/linux/platform_data/gpmc-omap.h | 37
Hi,
The existing OMAP GPMC driver has been suffering from ad-hoc architecture
with no clear separation between GPMC driver, Chip Select timing/settings and
Memory Device driver. The device tree implementation also reflects the same
issues.
The purpose of this series is to clean up the OMAP GPMC d
This function populates platform data for the specified Chip Select.
It should be called by board init code.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/gpmc.c | 69 ++
arch/arm/mach-omap2/gpmc.h | 6
2 files changed, 75 insertions(+)
d
The meaning of ranges and how address mapping is done has changed.
Ranges should now contain 2 ranges
- GPMC I/O map. ~1GB. This map will be partitioned among the
chip select (CS) nodes
- GPMC register map. This is common for all the CS nodes
and is shared only by the NAND controller.
GPMC and NAND drivers share the same register space but never use the
same registers. As there is no clear address seperation between the
registers for GPMC and NAND, we can't easily split it up into 2 regions
i.e. one for GPMC and other for NAND. Instead, we simply remap the entire
register space
On 21/05/14 12:15, Florian Vaussard wrote:
> Add the necessary DTS nodes to enable the micro-HDMI output on Parlor
> board.
>
> Signed-off-by: Florian Vaussard
> ---
> v1->v2:
> - Rebased on Tony's omap-for-v3.16/dt-v2
> - Use OMAP4_IOPAD macro
> - Use hpd pin as GPIO with hdmi-connector
>
> ar
We need set-rate-parent flags for the display's clock path so that the
DSS driver can change the clock rate of the PLL.
This patchs adds the ti,set-rate-parent flag to disp_clk and
dpll_disp_m2_ck clock nodes.
Signed-off-by: Tomi Valkeinen
---
arch/arm/boot/dts/am43xx-clocks.dtsi | 2 ++
1 file
Add ti,set-rate-parent to dss_dss_clk so that the DSS driver can
set the rate.
Signed-off-by: Tomi Valkeinen
---
arch/arm/boot/dts/omap54xx-clocks.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/omap54xx-clocks.dtsi
b/arch/arm/boot/dts/omap54xx-clocks.dtsi
index d487f
On 14/05/14 00:32, Tony Lindgren wrote:
> +&dss {
> + status = "ok";
> + vdds_dsi-supply = <&vpll2>;
> + port {
> + dpi_out: endpoint {
> + remote-endpoint = <&lcd_in>;
> + data-lines = <18>;
> + };
> + };
> +};
I jus
Hi,
Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock
related changes separately, and I removed OMAP5's RFBI node, which depends on
more clock changes. The RFBI driver doesn't work at the moment anyway, so
removing the RFBI node should not be an issue.
Tony, if these loo
From: Sathya Prakash M R
Add DT data for the display subsystem for AM4372. The DSS on AM4372 is
basically OMAP3's DSS, without DSI and VENC blocks.
Signed-off-by: Sathya Prakash M R
Signed-off-by: Tomi Valkeinen
---
arch/arm/boot/dts/am4372.dtsi | 30 ++
1 file cha
From: Sathya Prakash M R
Add DT data for am437x-gp-evm's LCD panel.
Signed-off-by: Sathya Prakash M R
Signed-off-by: Tomi Valkeinen
---
arch/arm/boot/dts/am437x-gp-evm.dts | 97 +
1 file changed, 97 insertions(+)
diff --git a/arch/arm/boot/dts/am437x-gp-ev
Add OMAP5 DSS nodes to omap5.dtsi.
Signed-off-by: Tomi Valkeinen
---
arch/arm/boot/dts/omap5.dtsi | 61
1 file changed, 61 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index f8c9855ce587..b80f4c5d0a5b 100644
Add DT data for am43x-epos-evm's LCD panel.
Signed-off-by: Tomi Valkeinen
---
arch/arm/boot/dts/am43x-epos-evm.dts | 101 +++
1 file changed, 101 insertions(+)
diff --git a/arch/arm/boot/dts/am43x-epos-evm.dts
b/arch/arm/boot/dts/am43x-epos-evm.dts
index 167dbc8
omap5-uevm has a tca6424a I/O expander. Add it to the .dts file.
Signed-off-by: Tomi Valkeinen
---
arch/arm/boot/dts/omap5-uevm.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
index 3b99ec25b748..76877516f6df 1006
omap5-uevm has a single HDMI output. Add the necessary display
information, including pinmuxing.
Signed-off-by: Tomi Valkeinen
---
arch/arm/boot/dts/omap5-uevm.dts | 82
1 file changed, 82 insertions(+)
diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arc
On 19/05/14 22:51, Tony Lindgren wrote:
>>> 4. Having this hack limited to device tree based booting while we are
>>>trying to unify the functions for drivers to use to get their
>>>resources.
>>
>> I don't understand this one. With non-DT boot we don't have the issue at
>> all, there's no
On Wed, May 21, 2014 at 12:26 PM, Yegor Yefremov
wrote:
> Kernel: vanilla 3.15-rc5
> kexec: latest git (21.05.2014)
>
> I can load the zImage + dtb from u-boot, but invoking kexec prints
> following data and nothing happens after "Bye!":
>
> # kexec -d -f --dtb=/mnt/boot/am335x-evmsk.dtb /mnt/boot
Hi,
On Wed, May 21, 2014 at 04:05:56PM +0300, Tomi Valkeinen wrote:
> I'll try and see how the other options work, which are:
>
> - Bailing out from module_init in each display driver. The reason I
> don't like this (although I haven't tried it) is that all the display
> drivers need the modifica
* Lee Jones [140521 02:19]:
> On Tue, 20 May 2014, Tony Lindgren wrote:
>
> > * Lee Jones [140520 08:18]:
> > >
> > > Ah, I forgot to Ack this last time, didn't I?
> > >
> > > Acked-by: Lee Jones
> >
> > Yeah, here's this one updated with your ack.
>
> Has the code changed at all, or are
* Lee Jones [140521 02:24]:
> > Here's an updated set of patches to enable low-power idle modes
> > for some omap3 boards when booted with device tree.
> >
> > This series when applied on top of the patches in tread
> >
* Tomi Valkeinen [140521 05:45]:
> On 14/05/14 00:32, Tony Lindgren wrote:
>
> > +&dss {
> > + status = "ok";
> > + vdds_dsi-supply = <&vpll2>;
> > + port {
> > + dpi_out: endpoint {
> > + remote-endpoint = <&lcd_in>;
> > + data-lines = <18>;
>
* Tomi Valkeinen [140521 05:51]:
> Hi,
>
> Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock
> related changes separately, and I removed OMAP5's RFBI node, which depends on
> more clock changes. The RFBI driver doesn't work at the moment anyway, so
> removing the RFBI no
> > > * Lee Jones [140520 08:18]:
> > > >
> > > > Ah, I forgot to Ack this last time, didn't I?
> > > >
> > > > Acked-by: Lee Jones
> > >
> > > Yeah, here's this one updated with your ack.
> >
> > Has the code changed at all, or are you just reposting with my Ack
> > applied?
>
> No change
* Tomi Valkeinen [140521 05:04]:
> On 21/05/14 12:15, Florian Vaussard wrote:
> > Add the necessary DTS nodes to enable the micro-HDMI output on Parlor
> > board.
> >
> > Signed-off-by: Florian Vaussard
> > ---
> > v1->v2:
> > - Rebased on Tony's omap-for-v3.16/dt-v2
> > - Use OMAP4_IOPAD macro
On 21/05/14 18:02, Tony Lindgren wrote:
> * Tomi Valkeinen [140521 05:51]:
>> Hi,
>>
>> Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock
>> related changes separately, and I removed OMAP5's RFBI node, which depends on
>> more clock changes. The RFBI driver doesn't work a
* Tomi Valkeinen [140521 08:18]:
> On 21/05/14 18:02, Tony Lindgren wrote:
> > * Tomi Valkeinen [140521 05:51]:
> >> Hi,
> >>
> >> Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock
> >> related changes separately, and I removed OMAP5's RFBI node, which depends
> >> on
>
On 21/05/14 18:26, Tony Lindgren wrote:
> * Tomi Valkeinen [140521 08:18]:
>> On 21/05/14 18:02, Tony Lindgren wrote:
>>> * Tomi Valkeinen [140521 05:51]:
Hi,
Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock
related changes separately, and I removed
* Tomi Valkeinen [140521 08:33]:
> On 21/05/14 18:26, Tony Lindgren wrote:
> > * Tomi Valkeinen [140521 08:18]:
> >> On 21/05/14 18:02, Tony Lindgren wrote:
> >>> * Tomi Valkeinen [140521 05:51]:
> Hi,
>
> Here are the AM43xx and OMAP5 display DT changes again. I've sent the
> >>
Signed-off-by: Joachim Eastwood
---
Hi,
The mach-omap2 directory contains full register defines for OMAP4
control module but only around 27 of those are used. There are is
a total of 1795 register defines in four files with only 27 in use.
That is pretty low usefulness ratio...
I guess alot mor
Hi Roger,
On 21 May 02:20 PM, Roger Quadros wrote:
>
> For DT boot:
> - The GPMC controller node should have a chip select (CS) node for each used
> chip select. The CS node must have a child device node for each device
> attached to that chip select. Properties for that child are GPMC agnost
Hi,
This adds device tree support for the tsc2005 touchscreen
controller, which is currently only used by the Nokia N900
board.
The patch does not update the reset pin handling for platform
data based probe to avoid merge conflicts. The n900 platform
code will be removed in the near future (3.17?
Add common DT binding documentation for touchscreen devices and
implement input_parse_touchscreen_of_params, which parses the common
properties and configures the input device accordingly.
The method currently does not interpret the axis inversion properties,
since there is no matching flag in the
Add devicetree binding documentation for TSC2005 touchscreen.
Reviewed-by: Pavel Machek
Acked-by: Aaro Koskinen
Signed-off-by: Sebastian Reichel
---
.../bindings/input/touchscreen/tsc2005.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
Documentati
This adds support for the tsc2005 touchscreen
to the Nokia N900 DTS file.
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/omap3-n900.dts | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dt
This adds DT support to the tsc2005 touchscreen
driver. It also adds regulator support to the
driver if booted via DT.
Reviewed-by: Pavel Machek
Acked-by: Aaro Koskinen
Signed-off-by: Sebastian Reichel
---
drivers/input/touchscreen/tsc2005.c | 122 ++--
1 file c
Hi,
On Mon, May 19, 2014 at 05:35:39PM -0700, Tony Lindgren wrote:
> * Tony Lindgren [140514 14:57]:
> > * Sebastian Reichel [140510 09:40]:
> > > Add SSI device tree data for OMAP3 and Nokia N900.
> >
> > Picking this patch into omap-for-v3.16/dt thanks.
>
> Just noticed that this patch seems
* Sebastian Reichel [140521 11:26]:
> Hi,
>
> On Mon, May 19, 2014 at 05:35:39PM -0700, Tony Lindgren wrote:
> > * Tony Lindgren [140514 14:57]:
> > > * Sebastian Reichel [140510 09:40]:
> > > > Add SSI device tree data for OMAP3 and Nokia N900.
> > >
> > > Picking this patch into omap-for-v3.
* Tony Lindgren [140521 11:44]:
> * Sebastian Reichel [140521 11:26]:
> > The hwmod data may be wrong. The information from commit
> > 398917ce161e10d3c66afaefdb89c73c64c4b02d was simply
> > interpolated from all information I found. The OMAP3
> > public TRM does not contain *any* information abo
Hi,
On Wed, May 21, 2014 at 11:43:19AM -0700, Tony Lindgren wrote:
> > > Just noticed that this patch seems to somehow break idle
> > > modes on n900, so dropping both dts changes for now.
> > >
> > > Basically the n900 debug LEDs won't ever go off with
> > > these two dts patches enabled, even w
* Sebastian Reichel [140521 13:10]:
> Hi,
>
> On Wed, May 21, 2014 at 11:43:19AM -0700, Tony Lindgren wrote:
> > > > Just noticed that this patch seems to somehow break idle
> > > > modes on n900, so dropping both dts changes for now.
> > > >
> > > > Basically the n900 debug LEDs won't ever go o
Hi,
On Wed, May 21, 2014 at 12:45:28PM -0700, Tony Lindgren wrote:
> * Tony Lindgren [140521 11:44]:
> > * Sebastian Reichel [140521 11:26]:
> > > The hwmod data may be wrong. The information from commit
> > > 398917ce161e10d3c66afaefdb89c73c64c4b02d was simply
> > > interpolated from all inform
On Fri, May 16, 2014 at 02:05:35PM -0700, Tony Lindgren wrote:
> Commit 6ddeb6d84459 (dmaengine: omap-dma: move IRQ handling to omap-dma)
> added support for handling interrupts in the omap dmaengine driver
> instead of the legacy driver. Because of different handling for
> interrupts this however
* Sebastian Reichel [140521 14:51]:
> On Wed, May 21, 2014 at 12:45:28PM -0700, Tony Lindgren wrote:
>
> Right. The only documentation of the SSI module is existing
> code sent by Carlos / included in the maemo kernel.
That's probably better than any documentation though :)
> > > It's probably
* Sebastian Reichel [140521 10:38]:
> This adds support for the tsc2005 touchscreen
> to the Nokia N900 DTS file.
>
> Signed-off-by: Sebastian Reichel
Dmitry, if no other comments, feel free to pick this one too.
This does not seem to conflict with anything I have queued:
Acked-by: Tony Lindgr
Hi Tony,
Now that I have added the dma fix in addition to the idle support
patchset I can do clean shutdowns (versus removing battery :)) and
see the following final warning during shutdown:
[ 3724.136474] reboot: Power down
[ 3724.139770] [ cut here ]
[ 3724.144683] WARNI
Hi,
On Wed, May 21, 2014 at 03:08:07PM -0700, Tony Lindgren wrote:
> * Sebastian Reichel [140521 14:51]:
> > On Wed, May 21, 2014 at 12:45:28PM -0700, Tony Lindgren wrote:
> >
> > Right. The only documentation of the SSI module is existing
> > code sent by Carlos / included in the maemo kernel.
* Sebastian Reichel [140521 16:55]:
> Hi Tony,
>
> Now that I have added the dma fix in addition to the idle support
> patchset I can do clean shutdowns (versus removing battery :)) and
> see the following final warning during shutdown:
>
> [ 3724.136474] reboot: Power down
> [ 3724.139770]
On Wednesday, May 21, 2014 8:21 PM, Roger Quadros wrote:
>
> Fix the following warning when CONFIG_MTD_NAND_OMAP_BCH is disabled.
> warning: ‘erased_sector_bitflips’ defined but not used [-Wunused-function]
>
> Signed-off-by: Roger Quadros
(+cc Christian Engelmayer)
The same patch was already
On Tue, May 20, 2014 at 04:26:09PM +0530, Sekhar Nori wrote:
> On Monday 19 May 2014 10:23 PM, Peter Ujfalusi wrote:
> > On 05/19/2014 04:06 PM, Sekhar Nori wrote:
> >> On Friday 16 May 2014 05:47 PM, Peter Ujfalusi wrote:
> >>> Hi,
> >>>
> >>> Changes since v2:
> >>> - Comments from Sekhar and Arn
The TPS65917 chip is a power management IC for Portable Navigation Systems
and Tablet Computing devices. It contains the following components:
- Regulators.
- GPADC.
- Over Temperature warning and Shut down.
This patch series adds support for TPS65917 mfd device. At this time only
the regulato
Add the various binding files for the TPS65917 family of chips. There is a
top level MFD binding then a seperate binding for regulators IP blocks on chips.
Signed-off-by: Keerthy
---
Documentation/devicetree/bindings/mfd/tps65917.txt | 35
1 file changed, 35 insertions(+)
This patch adds support for TPS65917 PMIC regulators.
The regulators set consists of 5 SMPSs and 5 LDOs. The output
voltages are configurable and are meant to supply power to the
main processor and other components.
Signed-off-by: Keerthy
---
v3 Changes:
removed NULL ops structure
Corrected
The series does some refactoring on dwc3_probe()
Patch 1 - Now that we use driver compatible for revision check, remove the
unnecessary logic.
Patch 2-4 - reduce the size of dwc3_probe()
Patch 5 - Fix the crash on dwc3_omap removal
Patch 6 - Addresses the issue of xhci hang while resuming from s
Move find and set the utmi mode to its own seperate function.
Improve code readability, decrease the dwc3_probe() size.
Signed-off-by: George Cherian
---
drivers/usb/dwc3/dwc3-omap.c | 44 +---
1 file changed, 25 insertions(+), 19 deletions(-)
diff --git
Following crash is seen on dwc3_omap removal
Unable to handle kernel NULL pointer dereference at virtual address 0018
pgd = ec098000
[0018] *pgd=ad1f9831, *pte=, *ppte=
Internal error: Oops: 17 [#1] SMP ARM
Modules linked in: usb_f_ss_lb g_zero usb_f_acm u_serial usb_f_ecm u
The dwc3 wrapper driver should not be fiddling with the core interrupts.
Disabling the core interrupts in prepare stops xhci from proper operation.
So remove disable/enable of core interrupts from prepare/complete.
Signed-off-by: George Cherian
---
drivers/usb/dwc3/dwc3-omap.c | 15 +
Move map offset to its own seperate function.
Improve code readability, decrease the dwc3_probe() size.
Signed-off-by: George Cherian
---
drivers/usb/dwc3/dwc3-omap.c | 33 -
1 file changed, 20 insertions(+), 13 deletions(-)
diff --git a/drivers/usb/dwc3/dwc3-oma
Move the extcon related code to its own function.
Improve code readability, decrease the dwc3_probe() size.
Signed-off-by: George Cherian
---
drivers/usb/dwc3/dwc3-omap.c | 65 ++--
1 file changed, 39 insertions(+), 26 deletions(-)
diff --git a/drivers/us
Add TPS65917 Bindings.
Signed-off-by: Keerthy
---
.../bindings/regulator/tps65917-pmic.txt | 67
1 file changed, 67 insertions(+)
create mode 100644
Documentation/devicetree/bindings/regulator/tps65917-pmic.txt
diff --git a/Documentation/devicetree/bindings/re
Remove the x_major calculation logic from the wrapper revision register
to differentiate between OMAP5 and AM437x. This was done to find the
register offsets of wrapper register. Now that We do it using dt
compatible, remove the whole logic.
Signed-off-by: George Cherian
---
drivers/usb/dwc3/dwc
On Mon, May 19, 2014 at 05:34:20PM -0700, Tony Lindgren wrote:
> The following changes since commit 89ca3b881987f5a4be4c5dbaa7f0df12bbdde2fd:
>
> Linux 3.15-rc4 (2014-05-04 18:14:42 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/li
BABBLE and RESET share the same interrupt. The interrupt
is considered to be RESET if MUSB is in peripheral mode and
as a BABBLE if MUSB is in HOST mode.
Handle babble condition iff MUSB is in HOST mode.
Signed-off-by: George Cherian
---
drivers/usb/musb/musb_core.c | 2 +-
1 file changed, 1 in
For DSPS platform usb_phy_vbus(_off/_on) are NOPs.
So during musb_platform_reset() call usb_phy(_shutdown/_init)
Signed-off-by: George Cherian
---
drivers/usb/musb/musb_dsps.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/musb/musb_dsps.c b/drivers/usb/musb
Currently musb_platform_reset() is only used by dsps.
In case of BABBLE interrupt for other platforms the musb_platform_reset()
is a NOP. In such situations no need to re-initialize the endpoints.
Also in the latest silicon revision of AM335x, we do have a babble recovery
mechanism without resetti
Add sw_babble_control() logic to differentiate between transient
babble and real babble condition. Also add the SW babble control
register definitions.
Babble control register logic is implemented in the latest
revision of AM335x.
Signed-off-by: George Cherian
---
drivers/usb/musb/musb_dsps.c |
Find whether we are running on newer silicon. The babble control
register reads 0x4 by default in newer silicon as opposed to 0
in old versions of AM335x. Based on this enable the sw babble
control logic.
Signed-off-by: George Cherian
---
drivers/usb/musb/musb_dsps.c | 38 +++
Series add support for SW babble control logic found in
new silicon versions of AM335x. Runtime differentiation of
silicon version is done by checking the BABBLE_CTL register.
For newer silicon the register default value read is 0x4 and
for older versions its 0x0.
Patch 1 -> Handle Babble only if
During babble condition both first disconnect of devices are
initiated. Make sure MUSB controller is reset and re-initialized
after all disconnects.
To acheive this schedule a delayed work for babble rrecovery.
While at that convert udelay to usleep_range.
Refer Documentation/timers/timers-howto.
91 matches
Mail list logo
