Palmas class of devices can provide 32K clock(s) to be used by other devices
on the board. Depending on the actual device the provided clocks can be:
CLK32K_KG and CLK32K_KGAUDIO
or only one:
CLK32K_KG (TPS659039 for example)
Use separate compatible flags for the two 32K clock.
A system which
Palmas class of devices can provide 32K clock(s) to be used by other devices
on the board. Depending on the actual device the provided clocks can be:
CLK32K_KG and CLK32K_KGAUDIO
or only one:
CLK32K_KG (TPS659039 for example)
Use separate compatible flags for the two 32K clock.
A system which
Hi Mike,
This is a resend of the v2 version of the palmas clock driver which seamingly
missed the 3.16 merge window. I have added Nishanth's Reviewed-by tag to the
patches.
Changes since v1:
- binding documentation and driver has been separated based on Nishanth Menon's
comment
v2 of the
On Wed, Jun 25, 2014 at 3:37 PM, Tomasz Figa t.f...@samsung.com wrote:
For certain platforms (e.g. Exynos) it is necessary to read back some
values from registers before they can be written (i.e. SMC calls that
set multiple registers per call), so base address of L2C controller is
needed for
On Wed, 18 Jun 2014, Keerthy wrote:
Add palmas_pmic_driver_data structure.
Signed-off-by: Keerthy j-keer...@ti.com
---
include/linux/mfd/palmas.h | 25 +
1 file changed, 25 insertions(+)
diff --git a/include/linux/mfd/palmas.h b/include/linux/mfd/palmas.h
On Wed, 18 Jun 2014, Keerthy wrote:
add driver data and modularize the probe.
Nit: This is a sentence, it should start with a capital letter.
Signed-off-by: Keerthy j-keer...@ti.com
---
Changes in V2:
* Fixed the order of variable declarations.
drivers/mfd/palmas.c
Hello Nishanth,
On Friday 27 June 2014 12:01 AM, Nishanth Menon wrote:
We use regmap regulator ops to enable/disable and check if regulator
is enabled for various SMPS. However, these depend on valid
enable_reg, enable_mask and enable_value in regulator descriptor.
So, similar to fix we did in
Hi Lee Jones,
On Friday 27 June 2014 01:53 PM, Lee Jones wrote:
On Wed, 18 Jun 2014, Keerthy wrote:
add driver data and modularize the probe.
Nit: This is a sentence, it should start with a capital letter.
The series is already pulled by Mark. I Can send fixes on top of
that patch set.
On 26/06/14 22:05, Jyri Sarha wrote:
On 06/24/2014 01:03 PM, Tomi Valkeinen wrote:
We no longer need the horrible driver internal videmode tables, which
were used to decide if a given videomode is a HDMI or DVI mode. So
remove all related code.
Signed-off-by: Tomi Valkeinen
On 27/06/14 13:16, Tomi Valkeinen wrote:
On 26/06/14 22:05, Jyri Sarha wrote:
On 06/24/2014 01:03 PM, Tomi Valkeinen wrote:
We no longer need the horrible driver internal videmode tables, which
were used to decide if a given videomode is a HDMI or DVI mode. So
remove all related code.
On 26/06/14 22:20, Jyri Sarha wrote:
The hdmi_wp physical base address is needed for hdmi audio dma.
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(+)
On 26/06/14 22:20, Jyri Sarha wrote:
Integrate ASoC DAI component driver in to the OMAP hdmi driver. The
patch also updates the relevant entry in ti,omap5-dss DT binding
document. The driver registers a dummy hdmi codec driver and a
simple-card driver to produce a fully functional ALSA device.
On 06/27/2014 01:41 PM, Tomi Valkeinen wrote:
On 26/06/14 22:20, Jyri Sarha wrote:
The hdmi_wp physical base address is needed for hdmi audio dma.
...
Maybe it would be better to have a function which returns the phys
address for audio DMA? Only that one register is needed, right?
That
On 26/06/14 22:20, Jyri Sarha wrote:
Add audio datamember to hdmi struct and call register and unregister
functions form hdmi_audio.c. Register function registers the
integrated cpu dai, dummy HDMI codec, and simple-card machine driver
for complete HDMI audio support.
Signed-off-by: Jyri
Hi Daren, Guido,
From: Etheridge, Darren
On 06/26/2014 10:40 AM, Guido Martínez wrote:
I had some issues with this patch. Booting linux-next on a BeagleBone
Black with this exact LCD left me with an unusable white screen. Please
see below for some details.
On Tue, Jun 24, 2014 at 05:54:26PM
On 26/06/14 22:20, Jyri Sarha wrote:
Adds help section and SND_SOC dependency to OMAP4_DSS_HDMI_AUDIO.
Selects SND_OMAP_SOC, SND_SOC_HDMI_CODEC, and SND_SIMPLE_CARD if
OMAP4_DSS_HDMI_AUDIO is enabled.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/Kconfig | 16
On Thu, Jun 26, 2014 at 12:40:33PM +0530, Sricharan R wrote:
From: Nishanth Menon n...@ti.com
The current crossbar description does not include the description
required for the consumer of the crossbar, a.k.a devices whoes events
pass through the crossbar into the GIC interrupt controller.
On 26/06/14 22:20, Jyri Sarha wrote:
Integrate ASoC DAI component driver in to the OMAP hdmi driver. The
patch also updates the relevant entry in ti,omap5-dss DT binding
document. The driver registers a dummy hdmi codec driver and a
simple-card driver to produce a fully functional ALSA device.
On Thu, Jun 26, 2014 at 12:40:31PM +0530, Sricharan R wrote:
From: Nishanth Menon n...@ti.com
Currently we attempt to map any crossbar value to an IRQ, however,
this is not correct from hardware perspective. There is a max crossbar
event number upto which hardware supports. So describe the
On Thu, Jun 26, 2014 at 12:42:09AM -0700, Tony Lindgren wrote:
* Sricharan R r.sricha...@ti.com [140626 00:14]:
This series does some cleanups, fixes for handling two interrupts
getting mapped twice to same crossbar and provides support for
hardwired IRQ and crossbar definitions.
On
On 06/27/2014 02:57 PM, Tomi Valkeinen wrote:
On 26/06/14 22:20, Jyri Sarha wrote:
...
--- a/drivers/video/fbdev/omap2/dss/Makefile
+++ b/drivers/video/fbdev/omap2/dss/Makefile
@@ -14,5 +14,7 @@ omapdss-$(CONFIG_OMAP2_DSS_DSI) += dsi.o
omapdss-$(CONFIG_OMAP2_DSS_HDMI_COMMON) += hdmi_common.o
On 26/06/14 22:20, Jyri Sarha wrote:
Integrate ASoC DAI component driver in to the OMAP hdmi driver. The
patch also updates the relevant entry in ti,omap5-dss DT binding
document. The driver registers a dummy hdmi codec driver and a
simple-card driver to produce a fully functional ALSA device.
On Thu, Jun 26, 2014 at 10:21:00PM +0300, Jyri Sarha wrote:
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
On 06/27/2014 03:11 PM, Tomi Valkeinen wrote:
On 26/06/14 22:20, Jyri Sarha wrote:
...
+static struct asoc_simple_card_info card_info = {
+ .name = HDMI,
+ .card = OMAPHDMI,
+ .codec_dai.name = hdmi-hifi,
+};
The above is not const. That, and the contents of the struct make
On 27/06/14 15:26, Jyri Sarha wrote:
On 06/27/2014 03:11 PM, Tomi Valkeinen wrote:
On 26/06/14 22:20, Jyri Sarha wrote:
...
+static struct asoc_simple_card_info card_info = {
+.name = HDMI,
+.card = OMAPHDMI,
+.codec_dai.name = hdmi-hifi,
+};
The above is not const. That, and
On 06/27/2014 04:06 PM, Tomi Valkeinen wrote:
On 27/06/14 15:26, Jyri Sarha wrote:
On 06/27/2014 03:11 PM, Tomi Valkeinen wrote:
On 26/06/14 22:20, Jyri Sarha wrote:
...
+static struct asoc_simple_card_info card_info = {
+.name = HDMI,
+.card = OMAPHDMI,
+.codec_dai.name =
On 06/27/2014 02:39 PM, Tomi Valkeinen wrote:
On 26/06/14 22:20, Jyri Sarha wrote:
...
+#if defined(CONFIG_OMAP4_DSS_HDMI_AUDIO)
+ /* drvdata is only used by HDMI audio */
+ hdmi.audio.hdmi_lock = hdmi.lock;
+ hdmi.audio.wp = hdmi.wp;
+ hdmi.audio.core = hdmi.core;
+
On Wed, Jun 25, 2014 at 02:28:30PM +0200, Rickard Strandqvist wrote:
A struct member variable is set to the same value more than once
This was found using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist rickard_strandqv...@spectrumdigital.se
I think there
On 14:48-20140627, Keerthy wrote:
Hello Nishanth,
On Friday 27 June 2014 12:01 AM, Nishanth Menon wrote:
We use regmap regulator ops to enable/disable and check if regulator
is enabled for various SMPS. However, these depend on valid
enable_reg, enable_mask and enable_value in regulator
Hello Peter,
On Fri, Jun 27, 2014 at 8:01 AM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
Palmas class of devices can provide 32K clock(s) to be used by other devices
on the board. Depending on the actual device the provided clocks can be:
CLK32K_KG and CLK32K_KGAUDIO
or only one:
CLK32K_KG
Add help section to OMAP5_DSS_HDMI_AUDIO with dependency to
OMAP5_DSS_HDMI and select for OMAP_DSS_HDMI_AUDIO.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/Kconfig | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git
Removes the OMAP4 HDMI audio callbacks for an external audio driver and
the old external DAI driver does not work anymore after this patch.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi4.c | 113 -
1 file changed, 113 deletions(-)
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
Call register and unregister functions form hdmi_audio.c. Register
function registers the integrated cpu dai, dummy HDMI codec, and
simple-card machine driver for complete HDMI audio support.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi4.c | 34
Removes the OMAP5 HDMI audio callbacks for an external audio driver and
the old external DAI driver does not work anymore after this patch.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi5.c | 113 -
1 file changed, 113 deletions(-)
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
---
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
Integrate ASoC DAI component driver in to the OMAP hdmi driver. The
patch also updates the relevant entry in ti,omap5-dss DT binding
document. The driver registers a dummy hdmi codec driver and a
simple-card driver to produce a fully functional ALSA device. The DAI
driver is implemented in
Add help section to OMAP4_DSS_HDMI_AUDIO with dependency to
OMAP4_DSS_HDMI and select for newly created OMAP_DSS_HDMI_AUDIO. The
OMAP_DSS_HDMI_AUDIO option is for common HDMI audio support and it is
is dependent on SND_SOC.
Also selects SND_OMAP_SOC, SND_SOC_HDMI_CODEC, and SND_SIMPLE_CARD for
This code is not working currently and it can be removed. There is a
conflict in sharing resources with the actual HDMI driver and with
the ASoC HDMI audio DAI driver.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
arch/arm/mach-omap2/devices.c | 28
1 file changed,
Call register and unregister functions form hdmi_audio.c. Register
function registers the integrated cpu dai, dummy HDMI codec, and
simple-card machine driver for complete HDMI audio support.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
drivers/video/fbdev/omap2/dss/hdmi5.c | 46
Name the anonymous hdmi struct as omap_hdmi. Move the struct definition to
hdmi.h and turn core member into a pointer to deal with it's different
definitions for omap4 and omap5. Make associated changes to hdmi4.c
and hdmi5.c.
Signed-off-by: Jyri Sarha jsa...@ti.com
---
Chanhes since fist version:
- Make hdmi struct public
- http://mailman.alsa-project.org/pipermail/alsa-devel/2014-June/078220.html
- Change hdmi_wp_get_phys_addr() to hdmi_wp_get_audio_dma_addr()
- http://mailman.alsa-project.org/pipermail/alsa-devel/2014-June/078213.html
- Remove unnecessary
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
Hi Linus,
This is a small series with trivial changes to the gpio-omap driver.
There are no functional changes. Patches 1 and 2 removes code that it's
not necessary anymore now that the driver has been converted to use the
gpiolib irqchip and Patch 3 adds an omap prefix to all driver functions,
GPIO irqchips assign to the cascaded IRQs their own lock class
in order to avoid warnings about lockdep recursions since that
allow the lockdep core to keep track of things.
Since commit e45d1c80 (gpio: put GPIO IRQs into their own lock class)
there is no need to do this in a driver if it's using
The linux/irqchip/chained_irq.h header is already included
when selecting GPIOLIB_IRQCHIP so there is no need to do it
in the driver. This is a left over from commit fb655f5
(gpio: omap: convert driver to use gpiolib irqchip).
Signed-off-by: Javier Martinez Canillas jmarti...@softcrates.net
---
The GPIO OMAP driver didn't have a consistent naming scheme for
all its functions. Some of them had an omap prefix while others
didn't. There are many advantages on having a separate namespace
for driver functions so let's add an omap prefix to all of them.
Signed-off-by: Javier Martinez Canillas
From: Guido Martínez [mailto:gu...@vanguardiasur.com.ar]
On Tue, Jun 24, 2014 at 05:54:24PM +0530, Pekon Gupta wrote:
[...]
+gpmc {
+ranges = 0 0 0 0x0100;/* address range = 16MB (minimum GPMC
partition) */
+nand@0,0 {
+status = disabled;
+reg = 0 0
Guido,
On 06/17/2014 09:17 AM, Guido Martínez wrote:
The tilcdc driver could be compiled as a module, but was severely broken
and could not be used as such. This patchset attempts to fix the issues
preventing a proper load/unload of the module.
Issues included dangling sysfs nodes, dangling
50 matches
Mail list logo
