Thomas Abraham wrote:
>
> This patch series allows device tree enabled platforms to setup a runtime
> I/O mapping for the chip-id controller. This helps to remove statically
> defined I/O mapping for the Chip-ID controller.
>
> Thomas Abraham (2):
> ARM: Exynos: Create virtual I/O mapping for C
Hi Kukjin,
On Fri, Mar 15, 2013 at 1:32 PM, Vivek Gautam wrote:
> This patch-set is in continuation with patch-series:
> [PATCH v4 0/4] Enable ehci, ohci and dwc3 devices on exynos5250
> out of which follwowing patches have been picked up:
> ARM: Exynos5250: Enabling ehci-s5p driver
> ARM: Exyno
Hi Kukjin,
On Fri, Mar 15, 2013 at 1:26 PM, Vivek Gautam wrote:
> Based on 'for-next' of linux-samsung tree with following patches
> from Doug on top:
> usb: Document clocks in samsung, exynos4210-ehci/ohci bindings
> ARM: dts: add usb 2.0 clock references to exynos5250 device tree
>
> Also depe
Kukjin,
Please check this series.
On 13 March 2013 10:38, Sachin Kamat wrote:
> Keypad pins/lines are board specific and should be added to respective
> board dts files.
>
> Signed-off-by: Sachin Kamat
> ---
> arch/arm/boot/dts/exynos4x12-pinctrl.dtsi | 56
> -
>
Added clock entry definitions to MFC bindings document.
Signed-off-by: Sachin Kamat
---
.../devicetree/bindings/media/s5p-mfc.txt |5 +
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/media/s5p-mfc.txt
b/Documentation/devicetree/bindings/media/s5
Added MFC related clock entries in exynos4.dtsi file.
Signed-off-by: Sachin Kamat
---
Based on Kukjin's for-next.
Dependent on the below patch:
https://patchwork.kernel.org/patch/2349361/
---
arch/arm/boot/dts/exynos4.dtsi |2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dt
1 -
I have boot tested the setup-sh73a0 change on the kzm9g board, it seems fine.
The tests above were made by merging
git://sources.calxeda.com/kernel/linux.git arm-timers
head commit: df3f518db302caf9fc0511917c5e9021037f6fcd
("devtree: add binding documentation for sp8
On Wednesday, April 03, 2013, Doug Anderson wrote:
> Thomas,
>
> On Mon, Apr 1, 2013 at 11:09 PM, Thomas Abraham
> wrote:
> > With device core now able to setup the default pin configuration,
> > the pin configuration code based on the deprecated Samsung specific
> > gpio bindings is removed.
> >
Tushar Behera wrote:
>
> Arndale board support has been updated using pin-control and
> common clock framework.
>
> The patchset is based on Kukjin's for-next.
> commit d58f6a153f40 ("Merge branch 'next/clk-exynos-2' into for-next")
>
> It depends on following patchset.
>
> [PATCH 0/2] ARM: dts
Hi Sarah,
On Wed, Apr 3, 2013 at 10:57 PM, Sarah Sharp
wrote:
> Question: Do you still need this patch for 3.10?
Felipe's 'next' is closed for 3.10, so this series won't be making it
to 3.10 now, as a whole. :-(
>
> http://marc.info/?l=linux-usb&m=136057666911621&w=2
>
> Does this patchset bui
Mike Turquette wrote:
>
> Quoting Kukjin Kim (2013-03-25 02:26:34)
> > Heiko Stübner wrote:
> > >
> > > Second version of the fixes to address comments gathered from the
> first
> > > version, like not entering the dt code on non-dt platforms even if
> > > dt-support is present in the kernel.
> >
From: Naveen Krishna Chatradhi
This patch does the following
1. Handle the return values of wait_for_completion_interruptible_timeout
2. Reset software if a timeout happes.
Note: submitted for review at https://patchwork.kernel.org/patch/2279591/
Signed-off-by: Naveen Krishna Chatradhi
Cc: Dou
Alexander Shiyan wrote:
>
> > On Saturday 02 March 2013, Alexander Shiyan wrote:
> > > Board options are already under "if ARCH_S3C24XX" condition, so
> > > additional dependencies on this symbol can be removed.
> > >
> > > Signed-off-by: Alexander Shiyan
> >
> > Hi Alexander,
> >
> > Is this jus
Alexander Shiyan wrote:
>
> When CONFIG_S3C_BOOT_UART_FORCE_FIFO symbol is set, we should
> enable FIFO but actually switch command is missing in the code.
> This patch adds this switch.
>
> Signed-off-by: Alexander Shiyan
> ---
> arch/arm/plat-samsung/include/plat/uncompress.h | 2 ++
> 1 file
On Wednesday, March 27, 2013 10:04 PM, Thierry Reding wrote:
>
> On Tue, Mar 26, 2013 at 04:20:23PM +, Andrew Murray wrote:
> > This patch factors out common implementation patterns to reduce overall
> > kernel
> > code and provide a means for host bridge drivers to directly obtain struct
> >
Mike Turquette wrote:
>
> Quoting Kukjin Kim (2013-04-02 01:30:39)
> > Tomasz Figa wrote:
> > >
> > > On Saturday 30 of March 2013 15:33:00 Thomas Abraham wrote:
> > > > Hi Tomasz,
> > > >
> > > > On 27 March 2013 16:32, Tomasz Figa wrote:
> > > > > This series is a collection of various fixes an
Alexandre Courbot wrote:
>
> Hi Romain,
>
> On Sat, Mar 30, 2013 at 3:07 PM, Romain Naour
> wrote:
> > Hi Alex,
> >
> > When I read your mail, I was surprised that you were speaking about
> GPIOs, my pathes for samsung CPUs are intended for timer sub-system.
> >
> > As you can see in this thread
Quoting Kukjin Kim (2013-04-02 01:30:39)
> Tomasz Figa wrote:
> >
> > On Saturday 30 of March 2013 15:33:00 Thomas Abraham wrote:
> > > Hi Tomasz,
> > >
> > > On 27 March 2013 16:32, Tomasz Figa wrote:
> > > > This series is a collection of various fixes and extensions to Exynos4
> > > > clock dr
On Mon, Mar 18, 2013 at 10:31 PM, Tomasz Figa wrote:
> This patch splits pin bank description into two structures, one
> describing bank type (currently only bitfield widths), which can be
> shared across multiple banks and second containing bank-specific
> parameters including a pointer to a ban
On Wed, 3 Apr 2013, Felipe Balbi wrote:
> > Lets suppose DWC3 enables runtime_pm on USB 2 type phy,
> > it will try to go into suspend state and thereby call runtime_suspend(), if
> > any.
> > And PHY will come to active state only when its consumer wakes it up,
> > and this consumer is operation
Question: Do you still need this patch for 3.10?
http://marc.info/?l=linux-usb&m=136057666911621&w=2
Does this patchset build on top of that?
I'm really behind on my patches for 3.10, sorry.
Sarah Sharp
On Mon, Apr 01, 2013 at 07:23:59PM +0530, Vivek Gautam wrote:
> This patch-series enables r
Kukjin,
On Tue, Apr 2, 2013 at 7:16 PM, Kukjin Kim wrote:
>> Applied with 1st one, BTW, do you want to send this for stable tree?
I don't have any need for it to be in stable tree. The ARM Chromebook
hasn't reached critical functionality on any released/upstram Linux
versions so it doesn't make
Lars,
On Sat, Mar 16, 2013 at 7:41 AM, Lars-Peter Clausen wrote:
> I think you still need the mutex for serialization, otherwise the requests
> would just cancel each other out. Btw. what happens if you start a conversion
> while another is still in progress? Is it possible to abort a conversion?
On Tue, Apr 02, 2013 at 04:53:01PM +0530, Padmavathi Venna wrote:
> From: Prathyush K
>
> This patch fixes a possible crash in case drvdata for the secondary
> device is not set.
Applied both, thanks.
signature.asc
Description: Digital signature
On Wed, Apr 3, 2013 at 7:48 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Apr 03, 2013 at 07:40:44PM +0530, Vivek Gautam wrote:
>> >> > >> >> +static inline void usb_phy_autopm_enable(struct usb_phy *x)
>> >> > >> >> +{
>> >> > >> >> + if (!x || !x->dev) {
>> >> > >> >> + dev_err(x
Hi,
On Wed, Apr 03, 2013 at 07:40:44PM +0530, Vivek Gautam wrote:
> >> > >> >> +static inline void usb_phy_autopm_enable(struct usb_phy *x)
> >> > >> >> +{
> >> > >> >> + if (!x || !x->dev) {
> >> > >> >> + dev_err(x->dev, "no PHY or attached device
> >> > >> >> available\n");
Hi,
On Wed, Apr 3, 2013 at 7:26 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Apr 03, 2013 at 04:54:14PM +0300, Felipe Balbi wrote:
>> > >> >> +static inline void usb_phy_autopm_enable(struct usb_phy *x)
>> > >> >> +{
>> > >> >> + if (!x || !x->dev) {
>> > >> >> + dev_err(x->dev,
Hi,
On Wed, Apr 03, 2013 at 04:54:14PM +0300, Felipe Balbi wrote:
> > >> >> +static inline void usb_phy_autopm_enable(struct usb_phy *x)
> > >> >> +{
> > >> >> + if (!x || !x->dev) {
> > >> >> + dev_err(x->dev, "no PHY or attached device
> > >> >> available\n");
> > >> >> +
HI,
On Wed, Apr 03, 2013 at 06:42:48PM +0530, Vivek Gautam wrote:
> >> >> Adding APIs to handle runtime power management on PHY
> >> >> devices. PHY consumers may need to wake-up/suspend PHYs
> >> >> when they work across autosuspend.
> >> >>
> >> >> Signed-off-by: Vivek Gautam
> >> >> ---
> >>
Hi Felipe,
On Wed, Apr 3, 2013 at 1:45 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Apr 03, 2013 at 11:48:39AM +0530, Vivek Gautam wrote:
>> >> Adding APIs to handle runtime power management on PHY
>> >> devices. PHY consumers may need to wake-up/suspend PHYs
>> >> when they work across autosuspen
Hi Arun,
On 03/13/2013 05:09 AM, Arun Kumar K wrote:
> Hi Sylwester,
>
>>>
>>> /* Interrupt mask */
>>> #define S5PCSIS_INTMSK 0x10
>>> -#define S5PCSIS_INTMSK_EN_ALL0xf000103f
>>> +#define S5PCSIS_INTMSK_EN_ALL0xfc00103f
>>
>> Do you know w
On 2013年04月03日 18:10, Will Deacon wrote:
> I think the main problem is that you've reported an issue created from a
> randconfig, but you haven't made the config in question available.
excuse me, my English is not quite well.
I guess your meaning is :
I need also provide the related .conf
On Wed, Apr 03, 2013 at 10:46:53AM +0100, Chen Gang wrote:
> Hello Maintainers:
>
> when you have time, could you help to check this suggestion ?
[...]
> >
> > make:
> > make V=1 EXTRA_CFLAGS=-W ARCH=arm randconfig
> > make V=1 EXTRA_CFLAGS=-W ARCH=arm menuconfig
> > set arm-l
Hello Maintainers:
when you have time, could you help to check this suggestion ?
if we really need treat it as an issue, and also no one have time to
fix it, I should try.
thanks.
gchen.
On 2013年03月25日 10:10, Chen Gang wrote:
> Hello Maintainers:
>
> is it an issue that need solving
On 31 March 2013 09:23, Viresh Kumar wrote:
> On 25 March 2013 15:41, Viresh Kumar wrote:
>> This patch moves cpufreq driver of Samsung's ARM based s3c24xx platform to
>> drivers/cpufreq.
>>
>> Cc: Ben Dooks
>> Cc: Kukjin Kim
>> Cc: linux-samsung-soc@vger.kernel.org
>> Signed-off-by: Viresh Kum
Hi,
On Wed, Apr 03, 2013 at 11:35:43AM +0530, Vivek Gautam wrote:
> >> The current code in the dwc3 probe effectively disables runtime pm
> >> from ever working because it calls a get() that was never put() until
> >> device removal. Change the runtime pm code to match the standard
> >> formula a
Hi,
On Wed, Apr 03, 2013 at 11:48:39AM +0530, Vivek Gautam wrote:
> >> Adding APIs to handle runtime power management on PHY
> >> devices. PHY consumers may need to wake-up/suspend PHYs
> >> when they work across autosuspend.
> >>
> >> Signed-off-by: Vivek Gautam
> >> ---
> >> include/linux/us
37 matches
Mail list logo
