On 01/24/2013 12:21 PM, Alim Akhtar wrote:
+
+ i2c@12CC {
+ status = disabled;
+ };
+
+ i2c@12CD {
+ status = disabled;
+ };
+
+ i2c@121D {
+ status = disabled;
+ };
+
Why to disable these
On 01/24/2013 01:42 AM, Doug Anderson wrote:
Lars,
On Wed, Jan 23, 2013 at 4:52 AM, Lars-Peter Clausen l...@metafoo.de wrote:
Few doubts regarding the mappings and child device handling.
Kindly, suggest me better methods.
The patch looks mostly good now. As for the mappings, the problem is
This patchset cleans up the probe function of i2c-s3c2410 driver.
These have been tested on Exynos4210 based Origen board.
Changes since V2:
* Rebased to v3.8-rc4.
* devm_request_and_ioremap() has already been implemented.
Changes since V1:
* devm_request_mem_region and devm_ioremap calls
err_noclk label redirects to a simple return statement. Move the
return statement to the caller location and remove the label.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
Changes since V2:
* Rebased to v3.8-rc4.
drivers/i2c/busses/i2c-s3c2410.c |9 +++--
1 files changed,
err_cpufreq label is now used only once. It can be removed and related
code can be moved to the caller location.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
Changes since V2:
* Rebased to v3.8-rc4.
Changes since V1:
* Rebased as per the V2 patch series.
i2c-s3c2410 driver is modified to use devm_clk_get()
and devm_request_irq(). This also simplifies the
return path in driver's probe.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
Changes since V2:
* Rebased on v3.8-rc4. devm_request_and_ioremap implementaion
has already been merged.
Audio Subsystem has own clocks for I2S0 and PCM0 in all EXYNOS series.
This patch add clocks for I2S0 and PCM0 I/F.
Signed-off-by: Sangsu Park sangsu4u.p...@samsung.com
---
arch/arm/mach-exynos/Makefile |1 +
arch/arm/mach-exynos/clock-audss.c | 64
Hi,
On Sat, Dec 15, 2012 at 11:21:36PM +0900, Mark Brown wrote:
On Fri, Dec 14, 2012 at 09:06:49AM -0700, Stephen Warren wrote:
On 12/13/2012 10:50 PM, Naveen Krishna Chatradhi wrote:
+The first should be an output, and is used to claim the I2C bus,
+the second should be an input, and
On Thu, Jan 24, 2013 at 12:13:29PM +0100, Wolfram Sang wrote:
On Sat, Dec 15, 2012 at 11:21:36PM +0900, Mark Brown wrote:
also get things like read operations which appear as multiple
transactions on the I2C bus so require something higher level than what
multi-master provides.
I don't
On Thu, Jan 24, 2013 at 07:18:47PM +0800, Mark Brown wrote:
On Thu, Jan 24, 2013 at 12:13:29PM +0100, Wolfram Sang wrote:
On Sat, Dec 15, 2012 at 11:21:36PM +0900, Mark Brown wrote:
also get things like read operations which appear as multiple
transactions on the I2C bus so require
On Thu, Nov 29, 2012 at 10:35:34AM +0530, Naveen Krishna Chatradhi wrote:
From: Simon Glass s...@chromium.org
There is a rather odd feature of the exynos i2c controller that if it
is left enabled, it can lock itself up with the clk line held low.
This makes the bus unusable.
From: R. Chandrasekar rcse...@samsung.com
This patch adds runtime suspend to resume support for I2S.
Signed-off-by: Padmavathi Venna padm...@samsung.com
Signed-off-by: R. Chandrasekar rcse...@samsung.com
---
sound/soc/samsung/i2s.c | 26 ++
1 file changed, 26
From: Padmavathi Venna padm...@samsung.com
I2S module need to be reset after S2R. Keeping the S/W rst
control part in resume didn't help in playing audio after resume.
So this patch adds S/W RST control part in startup function which
gets triggered for every new audio stream playback.
Hi Santosh,
On 01/23/2013 11:55 AM, Santosh Shilimkar wrote:
Looping Marc, Benoit
On Wednesday 23 January 2013 04:06 PM, Mark Rutland wrote:
On Tue, Jan 22, 2013 at 10:05:18PM +, Kukjin Kim wrote:
Mark Rutland wrote:
+ devicetree-discuss, Grant Likely, Rob Herring and Tony Lindgren
On Thursday 24 January 2013 06:12 PM, Benoit Cousson wrote:
Hi Santosh,
On 01/23/2013 11:55 AM, Santosh Shilimkar wrote:
Looping Marc, Benoit
On Wednesday 23 January 2013 04:06 PM, Mark Rutland wrote:
On Tue, Jan 22, 2013 at 10:05:18PM +, Kukjin Kim wrote:
Mark Rutland wrote:
+
Hi Benoit,
On 24/01/13 12:42, Benoit Cousson wrote:
Hi Santosh,
On 01/23/2013 11:55 AM, Santosh Shilimkar wrote:
Looping Marc, Benoit
On Wednesday 23 January 2013 04:06 PM, Mark Rutland wrote:
On Tue, Jan 22, 2013 at 10:05:18PM +, Kukjin Kim wrote:
Mark Rutland wrote:
+
On Wed, Nov 07, 2012 at 11:44:37AM +0100, Jean Delvare wrote:
On Wed, 07 Nov 2012 15:58:26 +0530, Naveen Krishna Chatradhi wrote:
Don't unmark the device as suspended until after it's been re-setup.
The main race would be w.r.t. an i2c driver that gets resumed at the same
time
Using chip specific compatible string as it should be.
So fixing this for ehci-s5p, ohci-exynos and dwc3-exynos
which till now used a generic 'exynos' in their compatible strings.
Changes from v1:
- Changing compatible string from samsung,exynos5250-dwc3 to
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
Reviewed-by: Doug Anderson diand...@chromium.org
---
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
Reviewed-by: Doug Anderson diand...@chromium.org
---
On Thu, Jan 24, 2013 at 7:15 PM, Vivek Gautam gautam.vi...@samsung.com wrote:
Using chip specific compatible string as it should be.
So fixing this for ehci-s5p, ohci-exynos and dwc3-exynos
which till now used a generic 'exynos' in their compatible strings.
Changes from v1:
-
On 24 January 2013 15:24, Lars-Peter Clausen l...@metafoo.de wrote:
On 01/24/2013 01:42 AM, Doug Anderson wrote:
Lars,
On Wed, Jan 23, 2013 at 4:52 AM, Lars-Peter Clausen l...@metafoo.de wrote:
Few doubts regarding the mappings and child device handling.
Kindly, suggest me better
Currently all UDC drivers are calling
device_register() before calling
usb_add_gadget_udc(). In order to avoid
code duplication, we can allow udc-core.c
register that device.
However that would become a really large patch,
so to cope with the meanwhile and allow us
to write bite-sized patches,
By simply setting a flag, we can delete a little
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/musb/musb_gadget.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/usb/musb/musb_gadget.c b/drivers/usb/musb/musb_gadget.c
index
By simply setting a flag, we drop some boilerplate
code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/omap_udc.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/usb/gadget/omap_udc.c b/drivers/usb/gadget/omap_udc.c
index
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/bcm63xx_udc.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/usb/gadget/bcm63xx_udc.c b/drivers/usb/gadget/bcm63xx_udc.c
index
By simply setting a flag, we can remove some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/at91_udc.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/usb/gadget/at91_udc.c b/drivers/usb/gadget/at91_udc.c
index
Hi folks,
Please comment on this series as I need help testing it
on all UDC controllers so we can send it for v3.10 merge
window.
NOTE: I will queue this series for v3.10 merge window, so
make sure to test and comment.
cheers
Felipe Balbi (32):
usb: gadget: udc-core: allow udc class
We don't need to register that device ourselves
if we simply set gadget-register_my_device.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/dwc3/gadget.c | 17 ++---
1 file changed, 2 insertions(+), 15 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c
By simply setting a flag, we drop some boilerplate
code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/amd5536udc.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/drivers/usb/gadget/amd5536udc.c b/drivers/usb/gadget/amd5536udc.c
index
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/fsl_qe_udc.c | 15 ++-
1 file changed, 2 insertions(+), 13 deletions(-)
diff --git a/drivers/usb/gadget/fsl_qe_udc.c b/drivers/usb/gadget/fsl_qe_udc.c
index
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/atmel_usba_udc.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/usb/gadget/atmel_usba_udc.c
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/fusb300_udc.c | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/drivers/usb/gadget/fusb300_udc.c b/drivers/usb/gadget/fusb300_udc.c
index
Fix the following compile warning:
mv_u3d_core.c:1766:12: warning: 'mv_u3d_remove' \
defined but not used [-Wunused-function]
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/mv_u3d_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/net2280.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/usb/gadget/net2280.c b/drivers/usb/gadget/net2280.c
index 708c0b5..630f715 100644
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/pch_udc.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/usb/gadget/pch_udc.c b/drivers/usb/gadget/pch_udc.c
index a787a8e..7032145
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/s3c2410_udc.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/usb/gadget/s3c2410_udc.c b/drivers/usb/gadget/s3c2410_udc.c
index
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/s3c-hsudc.c | 11 +--
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/drivers/usb/gadget/s3c-hsudc.c b/drivers/usb/gadget/s3c-hsudc.c
index
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/chipidea/udc.c | 13 ++---
1 file changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/usb/chipidea/udc.c b/drivers/usb/chipidea/udc.c
index f64fbea..e95e8bb
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/pxa25x_udc.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/usb/gadget/pxa25x_udc.c b/drivers/usb/gadget/pxa25x_udc.c
index
We don't need the -register_my_device flag
anymore because all UDC drivers have been
properly converted.
Let's remove every history of it.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/chipidea/udc.c | 1 -
drivers/usb/dwc3/gadget.c | 1 -
Don't register anything non-generic under
the gadget's device as we don't really *own*
it.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/chipidea/udc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/chipidea/udc.c b/drivers/usb/chipidea/udc.c
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/renesas_usbhs/mod_gadget.c | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/renesas_usbhs/mod_gadget.c
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/s3c-hsotg.c | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/drivers/usb/gadget/s3c-hsotg.c b/drivers/usb/gadget/s3c-hsotg.c
index
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/r8a66597-udc.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/usb/gadget/r8a66597-udc.c
b/drivers/usb/gadget/r8a66597-udc.c
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/m66592-udc.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/usb/gadget/m66592-udc.c b/drivers/usb/gadget/m66592-udc.c
index
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/mv_u3d_core.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/usb/gadget/mv_u3d_core.c b/drivers/usb/gadget/mv_u3d_core.c
index
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/goku_udc.c | 10 +-
drivers/usb/gadget/goku_udc.h | 3 +--
2 files changed, 2 insertions(+), 11 deletions(-)
diff --git a/drivers/usb/gadget/goku_udc.c
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/imx_udc.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/usb/gadget/imx_udc.c b/drivers/usb/gadget/imx_udc.c
index
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/dummy_hcd.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/usb/gadget/dummy_hcd.c b/drivers/usb/gadget/dummy_hcd.c
index
Lars,
Thank you for your comments / thoughts...
On Thu, Jan 24, 2013 at 1:54 AM, Lars-Peter Clausen l...@metafoo.de wrote:
adc: adc@12D1 {
#io-channel-cells = 1;
io-channel-output-names = adc1, adc2, ...;
ncp15wb473@0 {
compatible =
On Thu, 24 Jan 2013, Vivek Gautam wrote:
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
Reviewed-by: Doug Anderson
[Silly gmail defaulting to html the first time around, sorry for the
re-send to those not on lists]
2013/1/24 Wolfram Sang w.s...@pengutronix.de:
On Wed, Nov 07, 2012 at 11:44:37AM +0100, Jean Delvare wrote:
On Wed, 07 Nov 2012 15:58:26 +0530, Naveen Krishna Chatradhi wrote:
Don't unmark the
below setting suspended = 1. Upstream implementation of the same
functionality will be implemented differently, most likely.
Thanks, so I'll discard this patch.
--
Pengutronix e.K. | Wolfram Sang|
Industrial Linux Solutions |
On 01/24/2013 03:20 PM, Naveen Krishna Ch wrote:
On 24 January 2013 15:24, Lars-Peter Clausen l...@metafoo.de wrote:
On 01/24/2013 01:42 AM, Doug Anderson wrote:
Lars,
On Wed, Jan 23, 2013 at 4:52 AM, Lars-Peter Clausen l...@metafoo.de wrote:
Few doubts regarding the mappings and child
On 01/24/2013 05:12 PM, Doug Anderson wrote:
Lars,
Thank you for your comments / thoughts...
Hi,
On Thu, Jan 24, 2013 at 1:54 AM, Lars-Peter Clausen l...@metafoo.de wrote:
adc: adc@12D1 {
#io-channel-cells = 1;
io-channel-output-names = adc1, adc2, ...;
Hi Laurent,
Thanks for the review.
On 01/24/2013 11:16 AM, Laurent Pinchart wrote:
[...]
+Data interfaces on all video devices are described by their child 'port'
+nodes. Configuration of a port depends on other devices participating in
+the data transfer and is described by 'endpoint'
Hi Felipe,
On Thursday 24 of January 2013 17:46:10 Felipe Balbi wrote:
We don't need the -register_my_device flag
anymore because all UDC drivers have been
properly converted.
Let's remove every history of it.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/chipidea/udc.c
Hi Felipe,
On Thursday 24 of January 2013 17:45:39 Felipe Balbi wrote:
Currently all UDC drivers are calling
device_register() before calling
usb_add_gadget_udc(). In order to avoid
code duplication, we can allow udc-core.c
register that device.
However that would become a really large
Hi Felipe,
On Thursday 24 of January 2013 17:46:02 Felipe Balbi wrote:
By simply setting a flag, we can drop some
boilerplate code.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/s3c-hsotg.c | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff
On Thu, Jan 24, 2013 at 07:52:52PM +0100, Tomasz Figa wrote:
Hi Felipe,
On Thursday 24 of January 2013 17:46:10 Felipe Balbi wrote:
We don't need the -register_my_device flag
anymore because all UDC drivers have been
properly converted.
Let's remove every history of it.
Hi,
On Thursday 24 of January 2013 19:19:57 Lars-Peter Clausen wrote:
On 01/24/2013 05:12 PM, Doug Anderson wrote:
Lars,
Thank you for your comments / thoughts...
Hi,
On Thu, Jan 24, 2013 at 1:54 AM, Lars-Peter Clausen l...@metafoo.de
wrote:
adc: adc@12D1 {
From: Giridhar Maruthy giridha...@samsung.com
Signed-off-by: Giridhar Maruthy giridha...@samsung.com
Signed-off-by: Kukjin Kim kgene@samsung.com
---
Resending due to line wrapped from e-mail client.
Documentation/devicetree/bindings/i2c/i2c-s3c2410.txt |2 ++
On 01/24/2013 08:15 PM, Tomasz Figa wrote:
Hi,
On Thursday 24 of January 2013 19:19:57 Lars-Peter Clausen wrote:
On 01/24/2013 05:12 PM, Doug Anderson wrote:
Lars,
Thank you for your comments / thoughts...
Hi,
On Thu, Jan 24, 2013 at 1:54 AM, Lars-Peter Clausen l...@metafoo.de
wrote:
Wolfram Sang wrote:
On Tue, Jan 22, 2013 at 06:47:39PM -0800, Kukjin Kim wrote:
From: Giridhar Maruthy giridha...@samsung.com
Signed-off-by: Giridhar Maruthy giridha...@samsung.com
Signed-off-by: Kukjin Kim kgene@samsung.com
Looks OK but is line wrapped, can't apply.
Oh, OK.
On Thu, Jan 24, 2013 at 07:15:30PM +0530, Vivek Gautam wrote:
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
Hi,
On Thu, Jan 24, 2013 at 01:32:13PM -0800, Greg KH wrote:
On Thu, Jan 24, 2013 at 07:15:30PM +0530, Vivek Gautam wrote:
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam
Hi Sylwester,
On Thursday 24 January 2013 19:30:10 Sylwester Nawrocki wrote:
On 01/24/2013 11:16 AM, Laurent Pinchart wrote:
[...]
+Data interfaces on all video devices are described by their child 'port'
+nodes. Configuration of a port depends on other devices participating in
+the
On Thursday, January 24, 2013 10:45 PM, Vivek Gautam wrote
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
On Thursday, January 24, 2013 10:45 PM, Vivek Gautam wrote
Using specific chip in compatible strings. Newer SOCs can claim
device by using older string in the compatible list.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
Acked-by: Grant Likely grant.lik...@secretlab.ca
From: Girish K S ks.g...@samsung.com
Arndale is a low cost board based on the Samsung Exynos5250 SoC. This
patch adds initial device tree support for this board.
Signed-off-by: Girish K S ks.g...@samsung.com
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
Changes for V2:
* Addressed
Hi Tushar,
On Fri, Jan 25, 2013 at 10:36 AM, Tushar Behera
tushar.beh...@linaro.org wrote:
From: Girish K S ks.g...@samsung.com
Arndale is a low cost board based on the Samsung Exynos5250 SoC. This
patch adds initial device tree support for this board.
Signed-off-by: Girish K S
On 01/25/2013 10:59 AM, Alim Akhtar wrote:
[ ... ]
+
+ dwmmc_2: dwmmc2@1222 {
+ num-slots = 1;
+ supports-highspeed;
+ fifo-depth = 0x80;
+ card-detect-delay = 200;
+ samsung,dw-mshc-ciu-div = 3;
+
73 matches
Mail list logo
