+ ARM maintainers.
It's Gear 2 board support.
Thank you,
Kyungmin Park
On Tue, Sep 30, 2014 at 8:07 PM, Chanwoo Choi wrote:
> This patchset adds new board dts file for Samsung Rinato board (Gear 2) which
> is based on Exynos3250 SoC and adds sleep mode pin configuration using pinctrl
> subsyste
+ Adding ARM maintainers.
I know it's too late. just to know we trying to push product board
support at mainline.
Thank you,
Kyungmin Park
On Thu, Oct 2, 2014 at 9:50 AM, YoungJun Cho wrote:
> From: Youngjun Cho
>
> This patch adds new board dts file to support Samsung Monk board which is
> bas
From: Youngjun Cho
This patch adds new board dts file to support Samsung Monk board which is
based on Exynos3250 SoC and has different H/W configuration from Rinato.
This patch is based on linux-samsung.git for-next branch and depends on
[PATCH 0/2] ARM: dts: Add new board dts file for Exynos325
On Wed, Oct 01, 2014 at 04:41:33PM +0200, Ulf Hansson wrote:
> At ->probe() it's common practice for drivers/subsystems to bring their
> devices to full power and without depending on CONFIG_PM_RUNTIME.
>
> We could also expect that drivers/subsystems requires their device's
> corresponding PM dom
Hi Tomasz,
On 10/02/2014 12:13 AM, Tomasz Figa wrote:
> Hi Inki,
>
> On 17.09.2014 15:48, Inki Dae wrote:
>> This interface and relevant codes aren't used anymore.
>>
>
> Hmm, I might be missing something, but after removing this IOCTL, how do
> we obtain an offset to pass to mmap()?
There is D
On Wednesday, October 01, 2014 06:18:58 PM Sylwester Nawrocki wrote:
> On 01/10/14 16:41, Ulf Hansson wrote:
> > At ->probe() it's common practice for drivers/subsystems to bring their
> > devices to full power and without depending on CONFIG_PM_RUNTIME.
> >
> > We could also expect that drivers/s
On Wednesday 01 October 2014 18:49:20 Bartlomiej Zolnierkiewicz wrote:
> On Wednesday, October 01, 2014 06:01:29 PM Arnd Bergmann wrote:
> > On Thursday 25 September 2014, Kukjin Kim wrote:
> > > Exynos 2nd PM related updates for v3.18
> > >
> > > - Firmware supporting suspend and resume to excute
Hi,
On Wednesday, October 01, 2014 06:01:29 PM Arnd Bergmann wrote:
> On Thursday 25 September 2014, Kukjin Kim wrote:
> > Exynos 2nd PM related updates for v3.18
> >
> > - Firmware supporting suspend and resume to excute of low
> >level operations to enter and leave power mode for exynos
>
Remove symbols SERIAL_SAMSUNG_UARTS_4 and SERIAL_SAMSUNG_UARTS which
select the number of UART ports available on the SoC. Replace the usage
of SERIAL_SAMSUNG_UARTS in the serial driver with the maximum number of
UART ports possible. Removal of these symbols also helps in Exynos7
serial enablement.
Remove usage of CONFIG_SERIAL_SAMSUNG_UARTS symbol from platform
specific code.
Signed-off-by: Abhilash Kesavan
Reviewed-by: Tomasz Figa
---
Changes in v2:
- Re-ordered the patches
- Added a define for number of uart ports in
arch/arm/plat-samsung/init.c
- Removed CONFIG
On 01/10/14 16:41, Ulf Hansson wrote:
> There are currently no users of this API, let's remove it.
The sad fact is that removal of pm_genpd_dev_need_restore() calls
from arch/arm/mach-exynos/pm_domains.c introduces regressions in
multiple exynos drivers (I'm sure it breaks media drivers).
I think
On 01/10/14 16:41, Ulf Hansson wrote:
> At ->probe() it's common practice for drivers/subsystems to bring their
> devices to full power and without depending on CONFIG_PM_RUNTIME.
>
> We could also expect that drivers/subsystems requires their device's
> corresponding PM domains to be powered, to
Hi,
On Wed, Oct 1, 2014 at 7:00 AM, Bartlomiej Zolnierkiewicz
wrote:
>
> Hi,
>
> On Wednesday, October 01, 2014 12:47:52 AM YUVARAJ CD wrote:
>
>> Since I am out of station, i dont have an access to my work set up.
>> Can you send me the dts entries of sd crad and their corresponding regulator
>
On Thursday 25 September 2014, Kukjin Kim wrote:
> Exynos 2nd PM related updates for v3.18
>
> - Firmware supporting suspend and resume to excute of low
>level operations to enter and leave power mode for exynos
>: introduce suspend() and resume() firmware operations
>
> - Fix AFTR mode o
On Thursday 25 September 2014, Kukjin Kim wrote:
> Samsung 3rd DT updates for v3.18
>
> - Fix rebase conflcits in previous tags/samsung-dt-2
>: Fix chip select GPIO for exynos5250-smdk5250
>: Remove display timings node for exynos5250-snow
>
> - Fix Exynos USB on kernels with USB Gadget s
On Thursday 25 September 2014, Kukjin Kim wrote:
> The following changes since commit f6361c6b3880063c2248d4e453331e3dc1efbf83:
>
>ARM: S3C24XX: remove separate restart code (2014-09-14 02:43:09 +0900)
>
> are available in the git repository at:
>
>git://git.kernel.org/pub/scm/linux/kern
On Wednesday 24 September 2014, Kukjin Kim wrote:
> The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:
>
>Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)
>
> are available in the git repository at:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.
On Wednesday 24 September 2014, Kukjin Kim wrote:
> Hi Arnd, Olof and Kevin
>
> Here is second bunch of Samsung DT updates for v3.18.
>
> This is based on previous pull-request for tags/samsung-dt but not yet
> pulled into arm-soc.
>
> Please pull and if any problems, kindly let me know.
>
Pu
On Wed, Oct 1, 2014 at 4:12 PM, Daniel Drake wrote:
> On Wed, Oct 1, 2014 at 12:36 AM, Vivek Gautam
> wrote:
>> One reason i doubt why it could be coming is because we are
>> specifically putting the
>> child after doing everything with it.
>>
>> When we are getting the child node using for_each
Hi,
On Wed, Oct 1, 2014 at 6:06 AM, Bartlomiej Zolnierkiewicz
wrote:
>
> Hi,
>
> On Tuesday, September 30, 2014 10:22:34 AM Doug Anderson wrote:
>> Bartlomiej
>>
>> On Mon, Sep 29, 2014 at 5:31 AM, Bartlomiej Zolnierkiewicz
>> wrote:
>> >
>> > Hi,
>> >
>> > On Friday, August 29, 2014 01:34:44 PM
Hi Inki,
On 17.09.2014 15:48, Inki Dae wrote:
> This interface and relevant codes aren't used anymore.
>
Hmm, I might be missing something, but after removing this IOCTL, how do
we obtain an offset to pass to mmap()?
Best regards,
Tomasz
--
To unsubscribe from this list: send the line "unsubscr
On Wed, Oct 1, 2014 at 12:36 AM, Vivek Gautam wrote:
> One reason i doubt why it could be coming is because we are
> specifically putting the
> child after doing everything with it.
>
> When we are getting the child node using for_each_available_child_of_node(),
> which calls for of_get_next_avail
At ->probe() it's common practice for drivers/subsystems to bring their
devices to full power and without depending on CONFIG_PM_RUNTIME.
We could also expect that drivers/subsystems requires their device's
corresponding PM domains to be powered, to successfully complete a
->probe() sequence.
Ali
When there are more than one device in a PM domain these will obviously
be probed at different times. Depending on timing and the implemented
support for runtime PM in a driver/subsystem, genpd may be advised to
power off a PM domain after a successful probe sequence.
Ideally we should have relied
There are currently no users of this API, let's remove it.
Additionally, if such feature would be needed future wise, a better
option is likely use pm_runtime_set_active|suspended() in some form.
Signed-off-by: Ulf Hansson
Acked-by: Geert Uytterhoeven
Acked-by: Kevin Hilman
---
drivers/base/p
Changes in v2:
-Added some acks.
-Updated commit messages.
-Included a wider audience of the patchset. V1 was lacking SoC
maintainers.
Here are link to the first patchset, were some discussion started.
http://marc.info/?l=linux-pm&m=141208104729597&w=2
When there
At ->probe() it's common practice for drivers/subsystems to bring their
devices to full power and without depending on CONFIG_PM_RUNTIME.
We could also expect that drivers/subsystems requires their device's
corresponding PM domains to be powered, to successfully complete a
->probe() sequence.
Ali
On Wednesday, October 01, 2014 03:57:54 PM Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> On Tuesday, September 30, 2014 02:23:44 PM Jaehoon Chung wrote:
> > Hi
> >
> > On 09/29/2014 09:31 PM, Bartlomiej Zolnierkiewicz wrote:
> > >
> > > Hi,
> > >
> > > On Friday, August 29, 2014 01:34:44 PM Ulf
Hi,
On Wednesday, October 01, 2014 12:47:52 AM YUVARAJ CD wrote:
> Since I am out of station, i dont have an access to my work set up.
> Can you send me the dts entries of sd crad and their corresponding regulator
> entries?
>From arch/arm/boot/dts/exynos5420-arndale-octa.dts:
...
mmc
Hi,
On Tuesday, September 30, 2014 02:23:44 PM Jaehoon Chung wrote:
> Hi
>
> On 09/29/2014 09:31 PM, Bartlomiej Zolnierkiewicz wrote:
> >
> > Hi,
> >
> > On Friday, August 29, 2014 01:34:44 PM Ulf Hansson wrote:
> >> On 22 August 2014 15:47, Yuvaraj Kumar C D wrote:
> >>> This patch makes use
On 10/01/2014 04:36 AM, Pankaj Dubey wrote:
Let's register reboot_notifier from PMU driver for reboot
functionality. So that we can remove restart hooks from
machine specific file, and thus moving ahead when PMU moved
to driver folder, this functionality can be reused for ARM64
based Exynos SoC's
Hello Vikas,
On Wed, Oct 1, 2014 at 12:23 PM, Vikas Sajjan wrote:
>
> My git log looks like below on top of Kukjin's for-next branch,
>
> d861ddd clk: exynos: Add CLK_IGNORE_UNUSED to aclk200_disp1 and aclk300_disp1
> adc14dc POSTED: ARM: EXYNOS: Use MCPM call-backs to support S2R on Exynos5420
>
Am Dienstag, 30. September 2014, 15:30:00 schrieb Guenter Roeck:
> On Tue, Sep 30, 2014 at 02:20:02PM -0700, Andrew Morton wrote:
> > On Tue, 19 Aug 2014 17:45:27 -0700 Guenter Roeck
wrote:
> > > Introduce a system restart handler call chain to solve the described
> > > problems.>
> > So someone
Hi Inki,
On 17.09.2014 15:48, Inki Dae wrote:
> This patch removes DRM_EXYNOS_GEM_MMAP ictrl feature specific
> to Exynos drm and instead uses drm generic mmap.
It looks like libdrm_exynos is still using DRM_EXYNOS_GEM_MMAP, but this
patch just removes it. This basically means that any applicatio
Hi,
On Tuesday, September 30, 2014 10:22:34 AM Doug Anderson wrote:
> Bartlomiej
>
> On Mon, Sep 29, 2014 at 5:31 AM, Bartlomiej Zolnierkiewicz
> wrote:
> >
> > Hi,
> >
> > On Friday, August 29, 2014 01:34:44 PM Ulf Hansson wrote:
> >> On 22 August 2014 15:47, Yuvaraj Kumar C D wrote:
> >> > T
On 1 October 2014 13:23, Tomasz Figa wrote:
> On 30.09.2014 20:33, Kevin Hilman wrote:
>> Ulf Hansson writes:
>>
>>> At ->probe() it's common practice for drivers/subsystems to bring their
>>> devices to full power and without depending on CONFIG_PM_RUNTIME.
>>>
>>> We could also expect that driv
Hi Tomasz,
On Wednesday, October 01, 2014 4:07 PM, Tomasz Figa wrote,
> To: Pankaj Dubey; linux-arm-ker...@lists.infradead.org; linux-samsung-
> s...@vger.kernel.org
> Cc: kgene@samsung.com; li...@arm.linux.org.uk; thomas...@samsung.com;
> vikas.saj...@samsung.com; li...@roeck-us.net; naus...@
Let's register reboot_notifier from PMU driver for reboot
functionality. So that we can remove restart hooks from
machine specific file, and thus moving ahead when PMU moved
to driver folder, this functionality can be reused for ARM64
based Exynos SoC's.
Signed-off-by: Pankaj Dubey
---
arch/arm/
Let's register reboot_notifier for Exynos5440 from it's clock driver
for reboot functionality. So that we can cleanup restart hooks from
machine specific file.
Signed-off-by: Pankaj Dubey
---
arch/arm/mach-exynos/exynos.c| 19 +--
drivers/clk/samsung/clk-exynos5440.c |
This patch removes restart hook from machine_desc of Exynos, and moves
respective code into reboot_notifiers.
Exynos5440 handles reboot via clock register so let's register a
reboot_notifier in Exynos5440 clock driver.
For reset Exynos SoC, reboot is handled via PMU SWRESET register so
let's regist
On 30.09.2014 20:33, Kevin Hilman wrote:
> Ulf Hansson writes:
>
>> At ->probe() it's common practice for drivers/subsystems to bring their
>> devices to full power and without depending on CONFIG_PM_RUNTIME.
>>
>> We could also expect that drivers/subsystems requires their device's
>> correspond
Hi Daniel,
On 18.09.2014 01:42, Daniel Drake wrote:
> Hi,
>
> I'm using pwm-samsung on Exynos4412 for a variable-brightness LED.
>
> When the LED is set to maximum brightness via the pwm-leds driver, we
> arrive at pwm_samsung_config with duty_ns = period_ns, i.e. 100% duty
> cycle.
>
> This fu
Hi Pankaj,
Please see my comments inline.
On 01.10.2014 07:49, Pankaj Dubey wrote:
> Let's register reboot_notifier from PMU driver for reboot
> functionality. So that we can remove restart hooks from
> machine specific file, and thus moving ahead when PMU moved
> to driver folder, this functiona
Hi Pankaj,
Please see my comments inline.
On 01.10.2014 07:48, Pankaj Dubey wrote:
> Let's register reboot_notifier for Exynos5440 from it's clock driver
> for reboot functionality. So that we can cleanup restart hooks from
> machine specific file.
>
> CC: Sylwester Nawrocki
> CC: Mike Turquett
HI Javier,
On Tue, Sep 30, 2014 at 7:15 PM, Javier Martinez Canillas
wrote:
> Hello Vikas,
>
> Thanks a lot for the re-spin.
>
> On Tue, Sep 30, 2014 at 1:02 PM, Vikas Sajjan
> wrote:
>>
>> Tested on Kukjin Kim's tree, for-next branch +
>> 1] http://www.spinics.net/lists/linux-samsung-soc/msg33
The patch disables vblanks during dpms off only if pagefilp has
not been finished. It also replaces drm_vblank_off with drm_crtc_vblank_put.
It fixes issue with page_flip ioctl not being able to acquire vblank counter.
Signed-off-by: Andrzej Hajda
---
Hi Inki,
This is fix (or just workaround) of
46 matches
Mail list logo
