On Tue, Nov 27, 2012 at 09:33:43AM +0900, Kukjin Kim wrote:
I checked Samsung audio driver stuff just now. If you don't mind, I will
drop the patch 48a2050d (ARM: SAMSUNG: Delete the unnecessary variable)
instead of applying this.
That works just as well for me, thanks. Padma, as I said in
On Tue, Nov 27, 2012 at 02:04:32PM +0530, Thomas Abraham wrote:
Add device tree based discovery support for max8997.
Applied, thanks.
signature.asc
Description: Digital signature
On Wed, Nov 28, 2012 at 11:21:31AM +0530, Padma Venkat wrote:
On Wed, Nov 28, 2012 at 10:55 AM, Sangbeom Kim sbki...@samsung.com wrote:
The requirement for an alias is also very odd, where does that come from?
I don't know that Which one is odd. Please let me know.
Having them at all is
On Wed, Nov 28, 2012 at 04:17:48PM +0530, Padmavathi Venna wrote:
As the I2S src clks are registered with clkdev using generic
connection id, driver can get the clk name using generic id.
So the variable representing the array of rclk src clks is
deleted.
Applied, thanks.
signature.asc
On Thu, Nov 29, 2012 at 10:35:35AM +0530, Naveen Krishna Chatradhi wrote:
The arbitrator is a general purpose function which uses two GPIOs to
communicate with another device to claim/release a bus. We use it to
arbitrate an i2c port between the AP and the EC.
Should this not be layerd on top
On Thu, Nov 29, 2012 at 10:14:58PM -0800, Olof Johansson wrote:
On Thu, Nov 29, 2012 at 6:13 PM, Simon Glass s...@chromium.org wrote:
It was originally done separately but I think it was felt that this
was overly complex. Olof can you please comment on this?
it is indeed not controller
On Sat, Dec 01, 2012 at 03:37:26PM +0530, Padmavathi Venna wrote:
Add the basic device tree based lookup.
Signed-off-by: Padmavathi Venna padm...@samsung.com
---
sound/soc/samsung/smdk_wm8994.c | 23 +++
Any new device tree bindings need binding documentation.
Your
On Fri, Nov 30, 2012 at 08:00:10PM +0900, Kukjin Kim wrote:
Mark, I'm holding on Padma's changes for Samsung audio.
If any updates about this from your side?
Is it ok to send current next/audio-samsung in my tree to upstream for v3.8?
They didn't seem to have broken anything in -next for
On Sat, Dec 01, 2012 at 03:37:27PM +0530, Padmavathi Venna wrote:
sound/soc/samsung/dma.c | 24 ++--
sound/soc/samsung/dma.h |3 +++
sound/soc/samsung/i2s.c |3 +++
sound/soc/samsung/smdk_wm8994.c |7 +--
4 files changed, 17
On Thu, Dec 06, 2012 at 09:31:40AM +0530, Padma Venkat wrote:
On Wed, Nov 28, 2012 at 4:17 PM, Padmavathi Venna padm...@samsung.com wrote:
Padmavathi Venna (2):
ASoC: Samsung: Get I2S src_clk from clock alias id.
ASoC: SAMSUNG: Add DT support for i2s
Any comments on DT support for
On Thu, Dec 06, 2012 at 09:20:36AM +0530, Padmavathi Venna wrote:
Previously, the ASoC 'platform' (PCM/DMA) object was instantiated via a
platform_device. This didn't represent the hardware well, since there
was no separate hardware associated with this platform_device; it was a
virtual device
On Fri, Dec 07, 2012 at 01:59:21PM +0530, Padmavathi Venna wrote:
Previously, the ASoC 'platform' (PCM/DMA) object was instantiated via a
platform_device. This didn't represent the hardware well, since there
was no separate hardware associated with this platform_device; it was a
virtual device
On Sat, Dec 08, 2012 at 10:07:54AM +0530, Padma Venkat wrote:
Samsung i2s driver registers the platform device twice one for the
samsung-i2s.0,1 or 2 and two for samsung-i2s.4(which actually doesn't
represent any H/W peripheral). The max number of I2S blocks on any
Samsung SoC are 3, the
On Mon, Dec 10, 2012 at 04:30:50PM +0530, Padma Venkat wrote:
Could you please explain me in more detail about single DT link
automatically expanded into two DAI links.
How this can be done?
The device tree should only represent the single physical link that
exists and the handling of the
On Mon, Dec 10, 2012 at 06:19:39PM +0530, Amit Daniel Kachhap wrote:
Signed-off-by: Amit Daniel Kachhap amit.dan...@samsung.com
Applied, thanks.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info
On Mon, Dec 10, 2012 at 06:19:40PM +0530, Amit Daniel Kachhap wrote:
This patch modifies the DVS register read function to select correct DVS1
register. This change is required because the GPIO select pin is 000 in
unintialized state and hence selects the DVS1 register.
Applied, thanks.
--
To
On Mon, Dec 10, 2012 at 06:19:41PM +0530, Amit Daniel Kachhap wrote:
Signed-off-by: Amit Daniel Kachhap amit.dan...@samsung.com
Applied, thanks.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info
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 signals that the other side (Client)
+wants to claim the bus. This
On Wed, Dec 19, 2012 at 01:24:14PM +, Grant Likely wrote:
On Thu, 13 Dec 2012 16:12:53 +0530, Padmavathi Venna padm...@samsung.com
wrote:
+- compatible : samsung,samsung-i2s
Isn't that kind of redundant? :-)
The format of the compatible strings should be vendor,part-number-i2s.
On Wed, Dec 19, 2012 at 12:32:01PM +, Grant Likely wrote:
I'm not convinced on the design of this protocol. It won't scale beyond
2 bus masters and it seems very specific to the design of a specific
piece of hardware. I don't think it is mature enough to bake into the
I ought to point out
On Tue, Nov 03, 2009 at 11:42:21AM +0900, jassi brar wrote:
On Mon, Nov 2, 2009 at 8:17 PM, Mark Brown
+ local_irq_save(irqs);
Why local_irq_save()? On existing uniprocessor systems they should be
Don't we need to protect critical mode change in PCM control register?
Since
On Thu, Nov 19, 2009 at 11:44:14AM +0900, jassi brar wrote:
Let each platform code(SoC specific) define names of all possible
source clocks and let the board init code pass on the potential source
clocks by some bit-mask(or some other mechanism) while setting the
platform data.
This is going
On Thu, Nov 19, 2009 at 11:38:41AM +, Russell King - ARM Linux wrote:
I'm not sure what you're commenting on precisely, but the Samsung code as
a whole doesn't use the clk API very well, and I suspect that is starting
to cause people to have to pass clock names around.
That's what I'd
On Fri, Dec 11, 2009 at 12:00:11PM +0100, Marc Zyngier wrote:
Kukjin Kim kgene@samsung.com wrote:
+/* define the number of gpios we need to the one after the GPR() range */
+#define ARCH_NR_GPIOS (S5P6440_GPR(S5P6440_GPIO_R_NR) + 1)
Doing so prevents the use of GPIO
On Fri, Dec 11, 2009 at 02:47:06PM +0100, Lukasz Majewski wrote:
The clock API used at S3C64xx seems not to allow for setting rate of two
clocks simultaneously (or am I wrong? :-) ).
Yes, the Linux clock API doesn't support that.
If this change would not be possible, then have anyone
On Mon, Dec 14, 2009 at 08:37:24PM +0900, Kukjin Kim wrote:
Ok, as I already reply another posting, I couldn't consider patch
atomicity. And all(almost?) my patches need so that can support
s5p6440. Of course they can be modified.
Normally what's done for things like that is to arrange to put
On Thu, Dec 17, 2009 at 05:54:21PM +0100, Lukasz Majewski wrote:
In general if you want advice on a kernel subsystem it's best to CC the
maintainers of the relevant subsystem - messages posted only to mailing
lists (particularly high volume ones such as this) can easily get lost
in the flow.
On Wed, Jan 20, 2010 at 02:02:02AM +, Ben Dooks wrote:
I've written a git pre-commit[1] hook which stops any commits happening if
checkpatch.pl reports problems with the patch. Any comments?
[1] http://www.fluff.org/ben/linux/githooks/pre-commit
Checkpatch does sometimes generate the
-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Jan 26, 2010 at 02:51:40PM +0900, jassisinghb...@gmail.com wrote:
This looks good overall, just a few smallish issues:
+static void s3c_ac97_activate(struct snd_ac97 *ac97)
+{
+ u32 ac_glbctrl, stat;
+
+ stat = readl(s3c_ac97.regs + S3C_AC97_GLBSTAT) 0x7;
+ switch
On Tue, Jan 26, 2010 at 07:52:45PM +0900, jassi brar wrote:
On Tue, Jan 26, 2010 at 7:19 PM, Mark Brown
This one needs a bit more explanation - why are you changing the AC97
slot? Is this a general problem with the S3C AC97 controller? It'd
also be better to use the symbolic register
On Tue, Jan 26, 2010 at 08:03:09PM +0900, jassi brar wrote:
The only reason I didn't submit patch to delete s3c2443-ac97.c is that my
smdk2443 didn't produce any sound. (btw the s3c2443-ac97.c also fails to do
so)
If they both work equally well please just go ahead and remove the old
On Tue, Jan 26, 2010 at 08:17:25PM +0900, jassi brar wrote:
On Tue, Jan 26, 2010 at 7:47 PM, Mark Brown
+ default:
+ s3c_ac97_cold_reset(ac97);
+ s3c_ac97_warm_reset(ac97);
+ break;
+ }
This automatic cold and warm reset looks a bit fishy
On Tue, Jan 26, 2010 at 08:57:56PM +0900, jassi brar wrote:
On Tue, Jan 26, 2010 at 8:09 PM, Mark Brown
If they both work equally well please just go ahead and remove the old
driver. Keeping the old driver around if it doesn't work is likely to
result in any fixups going into that.
ok
On Tue, Jan 26, 2010 at 09:11:55PM +0900, jassi brar wrote:
On Tue, Jan 26, 2010 at 8:52 PM, Mark Brown
That's not addressing the problem, though - the big issue is not
bringing up the AC97 link, it's the fact that you're doing an
uncontrolled cold reset. If we hit this code path it'll
On Wed, Jan 27, 2010 at 02:58:58PM +0900, jassisinghb...@gmail.com wrote:
From: Jassi Brar jassi.b...@samsung.com
Modify the AC97 platform backend so that the controller can be run
by the s3c-ac97.c
Signed-off-by: Jassi Brar jassi.b...@samsung.com
Acked-by: Mark Brown broo
On Wed, Jan 27, 2010 at 02:59:29PM +0900, jassisinghb...@gmail.com wrote:
From: Jassi Brar jassi.b...@samsung.com
Add AC97 controller to platform devices and initialize the AC97 gpios.
Signed-off-by: Jassi Brar jassi.b...@samsung.com
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
On Wed, Jan 27, 2010 at 03:01:20PM +0900, jassisinghb...@gmail.com wrote:
From: Jassi Brar jassi.b...@samsung.com
Add AC97 controller to platform devices and initialize the AC97 gpios.
Signed-off-by: Jassi Brar jassi.b...@samsung.com
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
On Wed, Jan 27, 2010 at 02:56:55PM +0900, jassisinghb...@gmail.com wrote:
A machine driver, for SMDKs with wm9713 as AC97 codec attached, has also
been added. The driver is generic enough to be used as such with newer SoCs.
OK, works for me with a smoke test so I've applied all the sound/soc
On Thu, Jan 28, 2010 at 07:05:18AM +, Ben Dooks wrote:
My first response is that this forces the user to rebuild the kernel
every time they decide to change the subsytems included, which if just
building things as modules isn't nice. However this wasn't a strong enough
objection at the
On Fri, Jan 29, 2010 at 10:08:04AM +0900, jassi brar wrote:
I will submit a patch for it, though I used exact control names and their
values before every command.
Normally the renumbering happens as a result of a source code change
such as the addition of a new control or some change in ALSA
On Tue, Mar 09, 2010 at 07:09:18PM +0530, Thomas Abraham wrote:
+#ifdef CONFIG_MMC_SDHCI_S3C
+int s5p_setup_sdhci_sclk(struct platform_device *pdev, struct clk *parent)
+{
+ struct s3c_sdhci_platdata *pdata = pdev-dev.platform_data;
+ struct device *dev = pdev-dev;
+ struct clk
On Mon, Apr 12, 2010 at 11:39:05AM +0200, Lukasz Majewski wrote:
Some SoCs allow for entering IDLE mode when they know that the system will
be
inactive for some time (to be more precise it will execute the idle task -
which prepares system to enter IDLE state). In that mode CPU core is not
On Thu, Apr 29, 2010 at 03:45:09PM +0300, Yauhen Kharuzhy wrote:
Can anybody explain current status of S3C6410 power management support
in mainline? Suspend-to-RAM looks completely broken in the current
Linus's git tree.
What problems are you experiencing?
--
To unsubscribe from this list:
On Tue, May 18, 2010 at 09:03:04AM +0100, Ben Dooks wrote:
it would be really helpful if you composed a covering message
for patch series so that any general comments can be attached
there... also it means the series doesn't end up getting
fragmeneted in my mailbox.
There's more going on
On Sun, May 30, 2010 at 02:04:39PM +0900, Jassi Brar wrote:
I believe on most implementations, if not all, sizeof char, short and
int are resp
1, 2 and 4 bytes. whereas long denotes the native capacity of the arch.
This is very common for interoperability with code making the assumption
that
On Tue, Jun 01, 2010 at 05:16:33AM +0100, Ben Dooks wrote:
On Tue, Jun 01, 2010 at 12:23:39PM +0900, Kyungmin Park wrote:
It's common function. Please add it to platform init instead of each board
init.
I know Mark Brown would rather this be the case too, but the original intent
On Fri, Jun 11, 2010 at 06:24:07AM +0100, Ben Dooks wrote:
Hmm, Mr Park and Co really need to learn how to handle the treatment of
patches. I'm really disapointed that these patches get submitted without
the proper authour accreditation. If this isn't sorted out then I for
one will start
On Mon, Jun 28, 2010 at 10:53:18AM +0530, Naveen Krishna Ch wrote:
On 24 June 2010 22:05, Mark Brown broo...@opensource.wolfsonmicro.comwrote:
That smells rather like a compiler bug to me - the two versions
ought to be equivalent apart from the ordering of the comparisons.
I'm not sure
On Thu, Jul 01, 2010 at 08:07:45AM +0200, Marek Szyprowski wrote:
+static struct regulator_consumer_supply aquila_ldo3_consumers[] = {
+ { .supply = VMIPI_1.1V, },
+};
+static struct regulator_consumer_supply aquila_ldo8_consumers[] = {
+ { .supply = VADC_3.3V, },
+};
On Thu, Jul 01, 2010 at 08:07:46AM +0200, Marek Szyprowski wrote:
+static struct regulator_consumer_supply goni_ldo3_consumers[] = {
+ { .supply = VMIPI_1.1V, },
+};
A similar issue to the previous patch applies here - you should be
defining consumers using struct device based
On Thu, Jul 01, 2010 at 03:32:17PM +0200, Marek Szyprowski wrote:
One more question - should I enable the regulators in the driver itself
or in the platform callback (like a poweron() callback)?
I don't understand what you mean by platform callback. Normally the
driver would unconditionally
On Fri, Jul 02, 2010 at 12:25:33PM +0100, Ben Dooks wrote:
On 28/06/10 12:28, Maurus Cuelenaere wrote:
No need for the '? 1 : 0'
I tihnk there is, IIRC there is no neccessity for a compiler to produce
one for true, just that the result be !0
The compiler will *produce* 1 for true, but it
On Sun, Jul 04, 2010 at 11:19:37AM +0200, Maurus Cuelenaere wrote:
I don't see what power there is to save? The speaker and headphone
jack are connected to the same physical pins, so when disabling the
pins for one of them, the other is also disabled.
Meh, so they are. That's a slightly
On 4 Jul 2010, at 19:03, Maurus Cuelenaere mcuelena...@gmail.com wrote:
Op 03-07-10 02:46, Maurus Cuelenaere schreef:
+static struct snd_soc_jack_pin smartq_jack_pins[] = {
+/* Disable speaker when headphone is plugged in */
+{
+.pin= Internal Speaker,
+
interrupt).
Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
For the regulator API usage:
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc
On Fri, Jul 16, 2010 at 05:09:20PM +0900, MyungJoo Ham wrote:
Two issues are addressed for max8998_set_voltage function.
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
Ideally you should've submitted this as two separate patches.
--
To unsubscribe from this list: send the line
:
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Still:
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Jul 20, 2010 at 08:07:07AM +0200, Marek Szyprowski wrote:
From: MyungJoo Ham myungjoo@samsung.com
Two issues are addressed for max8998_set_voltage function.
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
but as IIRC I said last time it would be nicer to fix one issue
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Jul 28, 2010 at 07:06:22PM +0200, Maurus Cuelenaere wrote:
Op 28-07-10 17:41, Mark Brown schreef:
+ if (sc-vmmc) {
+ int ret = regulator_disable(sc-vmmc);
+ if (ret)
+ return ret;
+ mdelay(2);
Shouldn't these delays be handled
On Wed, Jul 28, 2010 at 04:19:57PM +0200, Marek Szyprowski wrote:
static int sdhci_s3c_suspend(struct platform_device *dev, pm_message_t pm)
{
+ int ret = 0;
struct sdhci_host *host = platform_get_drvdata(dev);
+ struct sdhci_s3c *sc = sdhci_priv(host);
-by: Kyungmin Park kyungmin.p...@samsung.com
Looks good from a regulator point of view.
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info
On Wed, Jul 28, 2010 at 12:04:44PM +0900, Chanwoo Choi wrote:
+static struct regulator_consumer_supply wm8994_fixed_voltage0_supplies[] = {
+ {
+ .dev_name = 5-001a,
+ .supply = DBVDD,
+ }, {
+ .dev_name = 5-001a,
+
On Wed, Aug 04, 2010 at 03:16:51PM +0900, Chanwoo Choi wrote:
Mark Brown wrote:
OK, good - the fact that the connection wasn't being made with the PMIC
was my main point here.
Did you read writed mail about consumer supply of WM8994 by MyungJoo Ham?
I saw it, yes.
He is in charge
On Thu, Aug 19, 2010 at 04:05:15PM +0900, MyungJoo Ham wrote:
If MAX8952's EN is not going to be changed by this driver, the user
should set gpio_en_writable as false. In S5PC210/UNIVERSL board,
controlling EN pin at MAX8952 driver can be dangerous because this gpio
pin is shared with another
On Fri, Aug 20, 2010 at 02:24:22PM +0900, MyungJoo Ham wrote:
However, could you please clarify more about this? They are already
from platform data (pdata-ramp_speed and pdata-sync_freq).
Sorry, I misread - the code is fine.
--
To unsubscribe from this list: send the line unsubscribe
On Wed, Sep 01, 2010 at 09:15:36AM +0900, Kukjin Kim wrote:
Seems almost same between the operation of max8649 and max8952 except output
voltage range.
How do you think that can support max8952 with small modifying max8649?
Take a look at something like the WM831x drivers for how you can
On Wed, Sep 01, 2010 at 06:44:11PM +0900, Kukjin Kim wrote:
MM...but I'm not sure if I can submit other patch for max8952...
Actually, Mr. Ham's max8952 code has been applied by Liam.
We can always remove that if it makes more sense to combine the code.
- return (MAX8649_DCDC_VMIN +
On Wed, Sep 01, 2010 at 07:36:40PM +0900, Kyungmin Park wrote:
As your word, first check the ID1 to detect the 8649 and 8952 and read
ID2 again to distinguish it. But actually we pass the max8952 as
platform device, so don't need to read ID2.
If you can read the ID from the chip it's always
-by: Changhwan Youn chaos.y...@samsung.com
Signed-off-by: Kukjin Kim kgene@samsung.com
Cc: Mark Brown broo...@opensource.wolfsonmicro.com
This is OK but it should also include removal of the separate max8952
driver since the functionality is now merged into this driver. With
that
Acked-by: Mark
point since given dev you can always use dev_name but
you don't always have dev.
Acked-by: Mark Brown broo...@opoensource.wolfsonmicro.com
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
On Fri, Sep 10, 2010 at 06:55:50PM +0900, Kukjin Kim wrote:
+static struct fixed_voltage_config mmc2_fixed_voltage_config = {
+ .supply_name= T_FLASH_EN,
+ .microvolts = 280,
+ .gpio = S5PV210_MP05(4), /* XM0ADDR_12 */
...
On Mon, Sep 20, 2010 at 03:12:34PM +0900, Kukjin Kim wrote:
The reason the implementation is located in machine-specific code is that
the way to handle power domain in S5PV210 and S5PV310 is different but we
can handle this using platform_device_id.
Yes, I think it's reasonable to implement
...@samsung.com
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
CC: Mark Brown broo...@opensource.wolfsonmicro.com
Looks good from a regulator API point of view:
Reviewed-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from this list: send the line unsubscribe linux
On Fri, Oct 01, 2010 at 01:23:25PM +0900, Chanwoo Choi wrote:
Additionally, I explain the constraints of the regulator of WM8994 codec.
All these consumer supply of WM8994 codec connected the regulator(VCC_1.8V)
on a circuit diagram. VCC_1.8V regulator is always enabled, because it is
used to
On Fri, Oct 01, 2010 at 02:40:02PM +0900, Kyungmin Park wrote:
FYI: now wm8994 codec is connected to I/O power directly. and there's
no connection with PMIC.
Presumably there's a power rail connection...
Maybe you mean the I/O power LDO and use it. but it's always on in
case of s5pc110.
On Mon, Oct 04, 2010 at 09:50:04PM +0900, Chanwoo Choi wrote:
Do you have additional comment on this patch?
No, just what I said already.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Mon, Oct 04, 2010 at 08:52:34PM +0900, Seungwhan Youn wrote:
This patch add SCLK_SPDIF clock to support source clock of S/PDIF
on S5PV210.
Signed-off-by: Seungwhan Youn sw.y...@samsung.com
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
but this looks like an example of where
On Mon, Oct 04, 2010 at 08:42:25PM +0900, Seungwhan Youn wrote:
This patch add SCLK_SPDIF clock to support source clock of S/PDIF
on S5PC100.
Signed-off-by: Seungwhan Youn sw.y...@samsung.com
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
but...
+static int
On Mon, Oct 04, 2010 at 08:31:59PM +0900, Seungwhan Youn wrote:
This patch add S/PDIF platform device to support S/PDIF PCM audio
on S5PC100.
Signed-off-by: Seungwhan Youn sw.y...@samsung.com
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe from this list: send
On Mon, Oct 04, 2010 at 08:57:48PM +0900, Seungwhan Youn wrote:
This patch adds audio clocks(SCLK_AUDIO{0,1,2} and SCLK_AUDIO) to be
initial as a sysclk on boot-time.
Signed-off-by: Seungwhan Youn sw.y...@samsung.com
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
--
To unsubscribe
On Mon, Oct 04, 2010 at 09:16:23PM +0900, Seungwhan Youn wrote:
+/* Audio clock settings are belonged to board specific part. Every
+ * board can set audio source clock setting which is matched with H/W
+ * like this function-'set_audio_clock_heirachy'.
+ */
+static int
On Tue, Oct 05, 2010 at 02:39:00PM +0900, Jassi Brar wrote:
Yes we can have a kconfig entry for 'Controllable EPLL' but that seems
orthogonal to ASoC because, for SMDKs, we choose to produce
accurate signals hence need to manipulate EPLL. The only point is
where to do it.
Well, there's two
On Sat, Oct 09, 2010 at 10:52:26AM +0900, Jassi Brar wrote:
On Fri, Oct 8, 2010 at 6:07 PM, Seungwhan Youn claude.y...@gmail.com wrote:
Now, I'm almost finished 2nd patch for submit except this audio clock
setting. For now, I can only think that remove audio clock setting
from this machine
On Wed, Oct 13, 2010 at 04:55:55PM +0900, Kukjin Kim wrote:
Seungwhan Youn wrote:
This patch adds warning about changing EPLL rate to notice that other
driver that controls H/W, which is using EPLL, will has unknown effects
by this EPLL rate change.
+ printk(KERN_WARNING EPLL Rate
On Thu, Oct 14, 2010 at 10:17:11AM +0900, Jassi Brar wrote:
It's not exactly. GPIO pins are different.
Maybe the GPIO differences could be handled at one place and other codes
compressed ?
Platform data for the audio driver, perhaps? That's being used by some
other systems, and should be
On Tue, Oct 12, 2010 at 08:51:23PM +0900, Seungwhan Youn wrote:
This patch adds S/PDIF CPU driver for various Samsung SoCs.
Signed-off-by: Seungwhan Youn sw.y...@samsung.com
Applied this and the machine driver, thanks!
--
To unsubscribe from this list: send the line unsubscribe
On Wed, Dec 26, 2012 at 04:21:58PM +0530, Padma Venkat wrote:
Hi,
On Mon, Dec 24, 2012 at 9:33 AM, Padma Venkat padma@gmail.com wrote:
Hi,
You should always delete irrelevant text from mails, it makes it much
easier for people to find whatever content you've added.
I agree with using
On Thu, Jan 03, 2013 at 11:54:23AM -0600, Rob Herring wrote:
From: Rob Herring rob.herr...@calxeda.com
Numerous includes of asm/hardware/vic.h aren't needed, so remove them.
Acked-by: Mark Brown broo...@opensource.wolfsonmicro.com
signature.asc
Description: Digital signature
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
---
drivers/spi/spi-s3c64xx.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/spi/spi-s3c64xx.c b/drivers/spi/spi-s3c64xx.c
index ad93231..6495352 100644
--- a/drivers/spi/spi-s3c64xx.c
+++ b/drivers/spi/spi-s3c64xx.c
On Thu, Jan 10, 2013 at 12:41:47AM +0100, Tomasz Figa wrote:
+ * The following lookup table is used to override device names when devices
+ * are registered from device tree. This is temporarily added to enable
+ * device tree support addition for the Exynos4 architecture.
Cut'n'paste.
On Thu, Jan 10, 2013 at 12:41:43AM +0100, Tomasz Figa wrote:
+- interrupt-mask : Bit mask of valid interrupt sources (defaults to all
valid)
+- wakeup-mask : Bit mask of interrupt sources that can wake up the system
+ (defaults to all allowed)
Should this really be configured in the VIC
On Thu, Jan 10, 2013 at 12:41:45AM +0100, Tomasz Figa wrote:
This patch modifies IRQ initialization code of S3C64xx to support
Device Tree-based initialization of VICs.
Reviewed-by: Mark Brown broo...@opensource.wolfsonmicro.com
signature.asc
Description: Digital signature
On Thu, Jan 10, 2013 at 12:10:38PM +0100, Tomasz Figa wrote:
This is not the runtime interrupt/wakeup mask, but a global mask of
available interrupt/wakeup lines on particular platform, which still have
to be configured and enabled appropriately by user.
Ah, OK.
Reviewed-by: Mark Brown
From: Dimitris Papastamos d...@opensource.wolfsonmicro.com
We are using S3C_EINT(4) instead of S3C_EINT(5).
Signed-off-by: Dimitris Papastamos d...@opensource.wolfsonmicro.com
Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com
Cc: sta...@vger.kernel.org
---
arch/arm/mach-s3c64xx/mach
On Fri, Jan 18, 2013 at 05:17:00PM +0530, Padmavathi Venna wrote:
All Samsung SoCs has max 3 i2s controllers. So the i2s secondary fifo
interface device id was named as samsung-i2s.4. Renaming this to
samsung-i2s-sec to support device tree in i2s driver.
Applied, thanks.
signature.asc
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 12:39:48PM +0100, Wolfram Sang wrote:
On Thu, Jan 24, 2013 at 07:18:47PM +0800, Mark Brown wrote:
A read is typically implemented as a write of the register address
followed by a read of the value, usually with the ability to free the
bus in between. If two devices
101 - 200 of 1104 matches
Mail list logo
