On 09/11/2014 06:02 PM, Ezequiel Garcia wrote:
This commit adds a new platform-data boolean property that enables use
of a flash-based bad block table. This can also be enabled by setting
the 'nand-on-flash-bbt' devicetree property.
If the flash BBT is not enabled, the driver falls back to
On 09/11/2014 06:02 PM, Ezequiel Garcia wrote:
The current code abuses ifdefs to determine if the selected ECC scheme
is supported by the running kernel. As a result the code is hard to read,
and it also fails to load as a module.
This commit removes all the ifdefs and instead introduces a
On 09/11/2014 06:02 PM, Ezequiel Garcia wrote:
Usage of pr_err is frowned upon, so replace it with dev_err.
Aditionally, the message on nand_bch_init() error is redundant,
since proper error is showed if the function fails.
You could have omitted the details about nand_bch_init() in the commit
On Mon, Sep 15, 2014 at 01:31:56PM -0400, Peter Hurley wrote:
On 09/15/2014 11:39 AM, Peter Hurley wrote:
On 09/15/2014 10:00 AM, Frans Klaver wrote:
At 3.6Mbaud, with slightly over 2Mbit/s data coming in, we see 1600 uart
rx buffer overflows within 30 seconds. Threading the interrupt
On Mon, Sep 15, 2014 at 06:42:04PM +0200, Sebastian Andrzej Siewior wrote:
On 09/12/2014 12:28 PM, Frans Klaver wrote:
port config is 115200 8N1. I don't recall doing anything special. I
boot, login, less file and get a lock.
So I booted my mini Debian 7.6 (basic system + openssh) on my
The OMAP5 HDMI audio implementation needs HDMI_AUDIO_LAYOUT_6CH in
hdmi_core_audio_layout enum. I found the correct value from ti-linux
3.8 tree.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi.h |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
The booleans are not used anymore. Just select SND_OMAP_SOC_HDMI_AUDIO
to enable OMAP HDMI audio support.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/Kconfig |7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/video/fbdev/omap2/dss/Kconfig
The patches are based on:
git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git for-next
The base, the patches, and couple of additional not-to-be-merged
omap2plus_defconfig patches can be found here:
In new model these callbacks are obsolete since the ASoC component
drivers are integrated into the HDMI drivers and no callbacks are
needed anymore.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
.../fbdev/omap2/displays-new/connector-hdmi.c | 99
Removes the OMAP5 HDMI audio callbacks for the old external DAI driver.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi5.c | 113 -
1 file changed, 113 deletions(-)
diff --git a/drivers/video/fbdev/omap2/dss/hdmi5.c
This is used to store omap-hdmi-audio pdev for unregistering it.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi.h |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/video/fbdev/omap2/dss/hdmi.h
b/drivers/video/fbdev/omap2/dss/hdmi.h
index
Unify the private anonymous struct in hdmi4.c and hdmi5.c, name it as
struct omap_hdmi, and make it public in hdmi.h.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi.h | 21 +
drivers/video/fbdev/omap2/dss/hdmi4.c | 31
It does not waste too many bytes to compile all audio related core
functions always in with HDMI support. It should help readability and
in keeping the audio code in working shape. Leave the options just for
disabling and enabling the functionality in hdmi[45].c.
Signed-off-by: Jyri Sarha
Implements callbacks for OMAP HDMI audio platform driver and registers
it in probe function. Unregistering is done in remove function.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi5.c | 97 +
1 file changed, 97 insertions(+)
Removes the OMAP4 HDMI audio callbacks for the old external DAI driver.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi4.c | 113 -
1 file changed, 113 deletions(-)
diff --git a/drivers/video/fbdev/omap2/dss/hdmi4.c
Removes omap-hdmi DAI driver, omap-hdmi-card driver, the related
Kconfig options, and Makefile entries. The HDMI DAI drivers has been
integrated directly to OMAP4+ HDMI drivers and simple-card driver is
used instead of omap-hdmi-card driver.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
Implements callbacks for OMAP HDMI audio platform driver and registers
it in probe function. Unregistering is done in remove function.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi4.c | 103 +
1 file changed, 103 insertions(+)
hdmi4_audio_get_dma_port() is unused and and broken.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi4_core.c |9 -
drivers/video/fbdev/omap2/dss/hdmi4_core.h |2 --
2 files changed, 11 deletions(-)
diff --git
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/fbdev/omap2/dss/hdmi.h
b/drivers/video/fbdev/omap2/dss/hdmi.h
index a6e08ff..6d129f2 100644
---
The audio dma port is found in the hdmi_wp physical address space.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi.h|2 ++
drivers/video/fbdev/omap2/dss/hdmi_wp.c |6 ++
2 files changed, 8 insertions(+)
diff --git
The platform device should only be registered from OMAPDSS HDMI
driver. The platfrom driver registers and unregisters all ASoC
components needed for OMAP HDMI audio.
The hdmi audio driver implements cpu-dai component using the callbacks
provided by OMAPDSS. Omap-pcm is registered for platform
On Tue, Sep 16, 2014 at 11:05:40AM +0200, Frans Klaver wrote:
On Mon, Sep 15, 2014 at 06:42:04PM +0200, Sebastian Andrzej Siewior wrote:
On 09/12/2014 12:28 PM, Frans Klaver wrote:
port config is 115200 8N1. I don't recall doing anything special. I
boot, login, less file and get a lock.
On 09/15/2014 01:50 PM, Sebastian Andrzej Siewior wrote:
I changed the restore function the fix the am335x-evm + less freeze.
And now we have this. So let me search…
IER was 0 by accident. It fixed in TX path.
I pushed uart_v10_pre1 which should have it fixed aport from other
things…
I am going
When the audio stream is paused or suspended we stop the sDMA and when it
is unpsues/resumed we start the channel without reconfiguring it.
The omap_dma_stop() clears the link configuration when we pause the dma, but
it is not setting it back on start. This will result only one audio buffer
to be
On Tue, Sep 16, 2014 at 04:06:25PM +0300, Peter Ujfalusi wrote:
When the audio stream is paused or suspended we stop the sDMA and when it
is unpsues/resumed we start the channel without reconfiguring it.
The omap_dma_stop() clears the link configuration when we pause the dma, but
it is not
On 09/16/2014 04:22 PM, Russell King - ARM Linux wrote:
On Tue, Sep 16, 2014 at 04:06:25PM +0300, Peter Ujfalusi wrote:
When the audio stream is paused or suspended we stop the sDMA and when it
is unpsues/resumed we start the channel without reconfiguring it.
The omap_dma_stop() clears the
Hi,
When the audio is paused/resumed (application paused the sream or board suspend)
the audio was only playing back one period worth of data and then stops because
the omap_dam_stop() clears the link configuration and it is not restored in
start.
Also add memory barrier call to resume path
Add mb() call to resume path to ensure the necessary barrier.
Resume can happen after waking up from suspend for example.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/dma/omap-dma.c
When the audio stream is paused or suspended we stop the sDMA and when it
is unpaused/resumed we start the channel without reconfiguring it.
The omap_dma_stop() clears the link configuration when we pause the dma, but
it is not setting it back on start. This will result only one audio buffer
to be
On Tue, Sep 16, 2014 at 04:53:49PM +0300, Peter Ujfalusi wrote:
When the audio stream is paused or suspended we stop the sDMA and when it
is unpaused/resumed we start the channel without reconfiguring it.
The omap_dma_stop() clears the link configuration when we pause the dma, but
it is not
On 09/16/14 15:56, Russell King - ARM Linux wrote:
On Tue, Sep 16, 2014 at 04:53:49PM +0300, Peter Ujfalusi wrote:
When the audio stream is paused or suspended we stop the sDMA and when it
is unpaused/resumed we start the channel without reconfiguring it.
The omap_dma_stop() clears the link
On 09/09/2014 04:39 PM, Roger Quadros wrote:
On 09/09/2014 05:34 PM, Marc Kleine-Budde wrote:
On 09/09/2014 04:31 PM, Roger Quadros wrote:
Pass the correct 'mask' and 'value' bits to c_can_hw_raminit_wait_ti().
They seem to have been swapped in the usage instances.
Can you split this fix
On Tue, Sep 16, 2014 at 02:42:00PM +0200, Frans Klaver wrote:
On Tue, Sep 16, 2014 at 11:05:40AM +0200, Frans Klaver wrote:
On Mon, Sep 15, 2014 at 06:42:04PM +0200, Sebastian Andrzej Siewior wrote:
If there is nothing specific to the file you do less on I have no idea
what else it could
On Wed, Sep 10, 2014 at 12:10 AM, Kevin Hilman khil...@kernel.org wrote:
What I think you need to do (and what I've recommended at least once in
earlier reviews) put all the (non-rproc) wkup_m3 IPC into into one
driver and create a well-described, well-documented API that the
platform PM code
On Mon, 15 Sep 2014, Tony Lindgren wrote:
Commit cc824534d4fe (ARM: OMAP2+: hwmod: Rearm wake-up interrupts
for DT when MUSB is idled) fixed issues with hung UART wake-up
events by calling _reconfigure_io_chain() when MUSB is connected
or disconnected.
As pointed out by Paul Walmsley, we
Hi Ohad,
On 09/16/2014 10:08 AM, Ohad Ben-Cohen wrote:
On Wed, Sep 10, 2014 at 12:10 AM, Kevin Hilman khil...@kernel.org wrote:
What I think you need to do (and what I've recommended at least once in
earlier reviews) put all the (non-rproc) wkup_m3 IPC into into one
driver and create a
Daniel,
On 09/05/2014 04:18 PM, Nishanth Menon wrote:
Daniel,
On 13:22-20140827, Kevin Hilman wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
On Wednesday 27 August 2014 03:35 PM, Nishanth Menon wrote:
On Wed, Aug 27, 2014 at 2:13 PM, Kevin Hilman
khil...@deeprootsystems.com
Add DSS related pinmux and display data nodes required to support HDMI
and DVI video out on CM-T54.
Signed-off-by: Dmitry Lifshitz lifsh...@compulab.co.il
---
arch/arm/boot/dts/omap5-cm-t54.dts | 158
1 files changed, 158 insertions(+), 0 deletions(-)
diff
Add extcon and vbus-supply properties of DWC3 node.
Signed-off-by: Dmitry Lifshitz lifsh...@compulab.co.il
---
arch/arm/boot/dts/omap5-cm-t54.dts |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-cm-t54.dts
b/arch/arm/boot/dts/omap5-cm-t54.dts
Add DT support for Startek KD050C LCD 800x480 panel.
Signed-off-by: Dmitry Lifshitz lifsh...@compulab.co.il
---
arch/arm/boot/dts/omap5-cm-t54.dts | 44
1 files changed, 44 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-cm-t54.dts
Add ADS7846 touchscreen support.
Signed-off-by: Dmitry Lifshitz lifsh...@compulab.co.il
---
arch/arm/boot/dts/omap5-cm-t54.dts | 61
1 files changed, 61 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-cm-t54.dts
Add CM-T54 DT nodes:
* enable HDMI/DVI/LCD video output support
* add ADS7846 touchscreen support
* enchance DWC3 setup to enable power supply for USB3.0 OTG port
Dmitry Lifshitz (4):
ARM: dts: cm-t54: add HDMI/DVI display data
ARM: dts: cm-t54: add Startek LCD support
ARM: dts: cm-t54:
On 09/16/2014 11:35 AM, Dmitry Lifshitz wrote:
Add DSS related pinmux and display data nodes required to support HDMI
and DVI video out on CM-T54.
Signed-off-by: Dmitry Lifshitz lifsh...@compulab.co.il
---
arch/arm/boot/dts/omap5-cm-t54.dts | 158
1
* Sebastian Andrzej Siewior bige...@linutronix.de [140916 05:58]:
On 09/15/2014 01:50 PM, Sebastian Andrzej Siewior wrote:
I changed the restore function the fix the am335x-evm + less freeze.
And now we have this. So let me search…
IER was 0 by accident. It fixed in TX path.
I pushed
On 09/15/2014 07:01 PM, Sebastian Andrzej Siewior wrote:
On 09/11/2014 04:35 PM, Peter Hurley wrote:
I do need to find out if omap hardware sets UART_MSR_DCTS when auto CTS
is on. Would you mind running the debug patch below with HW flow control on?
I didn't forget about this. However I told
Hi
A few comments
On Mon, 15 Sep 2014, Tony Lindgren wrote:
In sprz318f.pdf Usage Note 2.7 says that UARTs cannot acknowledge
idle requests in smartidle mode when configured for DMA operations.
I don't have Rev. F here. But reading between the typos in Rev. E, all it
says that the UART
On 09/11/2014 01:57 PM, Peter Hurley wrote:
Hi Sebastian,
Hi Peter,
Nice work. Minor comments within.
Thanks.
After this is merged, it may be worth investigating how to use Yoshihiro's
newly-added 8250-based tunable RX trigger interface for omap.
We need to overwrite the FCR callback.
Here are some basic OMAP test results for Linux v3.17-rc5.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.17-rc5/20140916100200/
Test summary
Build: uImage:
Pass ( 3/ 3): omap1_defconfig, omap1_defconfig_1510innovator_only,
* Paul Walmsley p...@pwsan.com [140916 10:01]:
On Mon, 15 Sep 2014, Tony Lindgren wrote:
In sprz318f.pdf Usage Note 2.7 says that UARTs cannot acknowledge
idle requests in smartidle mode when configured for DMA operations.
I don't have Rev. F here. But reading between the typos in Rev.
The buffers to be used for communication are allocated during the
rpmsg virtio driver's probe, and the total number of buffers is
currently hard-coded to 512. The vring configuration can vary from
one platform to another or between different remote processors. The
setup of the receive buffers will
Hi,
Changes since v2:
- fix typo in patch two
- Acked-by added from Russell
When the audio is paused/resumed (application paused the sream or board suspend)
the audio was only playing back one period worth of data and then stops because
the omap_dam_stop() clears the link configuration and it is
Add mb() call to resume path to ensure the necessary barrier.
Resume can happen after waking up from suspend for example.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Russell King rmk+ker...@arm.linux.org.uk
---
drivers/dma/omap-dma.c | 2 ++
1 file changed, 2 insertions(+)
When the audio stream is paused or suspended we stop the sDMA and when it
is unpaused/resumed we start the channel without reconfiguring it.
The omap_dma_stop() clears the link configuration when we pause the dma, but
it is not setting it back on start. This will result only one audio buffer
to be
Hi Ohad,
The following is an updated patchset addressing the review comments on v1.
The patches are mainly developed to support the WkupM3 remote processor
driver on TI AM335x/AM437x SoCs. The patches are rebased onto 3.17-rc3
(rc independent actually).
I haven't made any major updates to Patch2
A remote processor may need to load certain firmware sections into
internal memories (eg: RAM at L1 or L2 levels) for performance or
other reasons. Introduce a new resource type (RSC_INTMEM) and add
an associated handler function to handle such memories. The handler
creates a kernel mapping for
The remoteproc driver core currently relies on iommu_present() on
the bus the device is on, to perform MMU management. However, this
logic doesn't scale for multi-arch, especially for processors that
do not have an IOMMU. Replace this logic instead by using a h/w
capability flag for the presence
By moving i2c devices to DT we can clean up
i2c_board_info and fix a problem with moving
INTC to irq domain where IRQs can be renumbered
on each boot.
Cc: Aaro Koskinen aaro.koski...@iki.fi
Signed-off-by: Felipe Balbi ba...@ti.com
---
arch/arm/boot/dts/omap2420-n810.dts | 7 +++
On Tue, Sep 16, 2014 at 03:31:40PM -0500, Felipe Balbi wrote:
By moving i2c devices to DT we can clean up
i2c_board_info and fix a problem with moving
INTC to irq domain where IRQs can be renumbered
on each boot.
Cc: Aaro Koskinen aaro.koski...@iki.fi
Signed-off-by: Felipe Balbi
The configuration is needed for HDMI audio. The swap and mirr
parameters have to be correctly set in the configuration in order to
have proper colors in the HDMI picture.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/gpu/drm/tilcdc/tilcdc_slave.c | 24 +++-
1 file
Add machine driver support for BeagleBone-Black HDMI audio. BBB has
NXP TDA998X HDMI transmitter connected to McASP port in I2S mode. The
44100 Hz sample-rate and it's multiples can not be accurately produced
on BBB. The only supported sample format is SNDRV_PCM_FORMAT_S32_LE.
The 8 least
The added ti,gpio-gate-clock is a basic clock that can be enabled and
disabled trough a gpio output. The DT binding document for the clock
is also added. For EPROBE_DEFER handling the registering of the clock
has to be delayed until of_clk_get() call time.
Signed-off-by: Jyri Sarha jsa...@ti.com
Changes since v2:
- Change compatible property from ti,gpio-clock to ti,gpio-gate-clock
- Some minor cleanups
The code has a functional dependency to:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg109264.html
Without the above patch the audio card does not probe.
The code has been
Adds mcasp0_pins, clk_mcasp0_fixed, clk_mcasp0, mcasp0, hdmi_audio,
and sound nodes.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
arch/arm/boot/dts/am335x-boneblack.dts | 52
1 file changed, 52 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-boneblack.dts
Adds configuration option for HDMI audio support for AM33XX based
boards with NXP TDA998x HDMI transmitter. The audio is connected to
NXP TDA998x trough McASP running in i2s mode.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
sound/soc/davinci/Kconfig | 12
1 file changed, 12
* Russell King - ARM Linux li...@arm.linux.org.uk [140912 16:16]:
On Fri, Sep 12, 2014 at 11:32:25AM -0700, Tony Lindgren wrote:
On some ARMs at least the memory can be mapped pgprot_noncached()
and still be working for atomic operations. As pointed out by
Colin Cross ccr...@android.com, in
* Tony Lindgren t...@atomide.com [140916 09:49]:
* Sebastian Andrzej Siewior bige...@linutronix.de [140916 05:58]:
On 09/15/2014 01:50 PM, Sebastian Andrzej Siewior wrote:
I changed the restore function the fix the am335x-evm + less freeze.
And now we have this. So let me search…
IER
The omap1's debug-macro.S is similar to the generic 8250 code. Compared to
the 8520 code the omap1 macro automatically determines what UART to use
based on breadcrumbs left by the bootloader and automatically copes with
the eccentric register layout on OMAP7XX.
This patch drops both these
Hi,
On Tue, Sep 16, 2014 at 11:46:24PM +0100, Daniel Thompson wrote:
+ config DEBUG_OMAP1UART1
+ bool Kernel low-level debugging via OMAP1 UART1
+ depends on ARCH_OMAP1
+ select DEBUG_UART_8250
+ help
+ Say Y here if you want
On 16/09/14 15:58, Aaro Koskinen wrote:
Hi,
On Tue, Sep 16, 2014 at 11:46:24PM +0100, Daniel Thompson wrote:
+config DEBUG_OMAP1UART1
+bool Kernel low-level debugging via OMAP1 UART1
+depends on ARCH_OMAP1
+select DEBUG_UART_8250
+help
On Mon, 08 Sep 2014, Tony Lindgren wrote:
* Nishanth Menon n...@ti.com [140903 12:07]:
ti,system-power-controller is more or less the standard way of
indicating that the PMIC is the system wide power controller and hence
may be used to switch off the system. Almost ALL TI PMIC drivers and
The omap1's debug-macro.S is similar to the generic 8250 code. Compared to
the 8520 code the omap1 macro automatically determines what UART to use
based on breadcrumbs left by the bootloader and automatically copes with
the eccentric register layout on OMAP7XX.
This patch drops both these
We're moving to the dmaengine API, so let's remove the unused
pieces of the omap legacy DMA code to make sure we don't get
any new users for these:
omap_set_dma_color_mode
omap_set_dma_src_index
omap_set_dma_dest_index
omap_dma_unlink_lch
omap_clear_dma
omap_dma_running
omap_dma_set_prio_lch
On 17 September 2014 06:40, Jyri Sarha jsa...@ti.com wrote:
Changes since v2:
- Change compatible property from ti,gpio-clock to ti,gpio-gate-clock
- Some minor cleanups
The code has a functional dependency to:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg109264.html
Without
73 matches
Mail list logo
