Hi,
On Thu, Oct 22, 2015 at 9:07 AM, Javier Martinez Canillas
wrote:
>> Note that personally I would only choose the "highest" priority as an
>> absolute last resort. Leaving a little extra slack in there means
>> that when the next person comes up with a really good reason to run
>> before you
Krzysztof,
On Wed, Oct 21, 2015 at 6:43 PM, Krzysztof Kozlowski
wrote:
> I think at least one platform may be affected because it used
> mmc-pwrseq-emmc and gpio-restart.
>
> Look at rk3288-veyron.dtsi.
>
> Both of restart handlers had the priority of 129 which means that the
> order of execution
Hi,
On Mon, Oct 19, 2015 at 3:11 AM, Anand Moon wrote:
> 1 Drop the cd-gpios changes. pinctrl-0 changes.
Right.
> 2 Fix the regulator changes for vmmc/vqmmc with disable of
> regulator-always-on;
I'm not totally sure I understand. You should need to keep vmmc and
vqmmc always on because oth
Hi,
On Tue, Oct 13, 2015 at 6:06 PM, Alim Akhtar wrote:
> +Doug
> Hello,
> AFAIR, dw_mmc host controller does support UHS-I [1], specially SDR50
> and SDR104 modes.
>
> [1]: http://www.spinics.net/lists/linux-mmc/msg28186.html
>
> What I remember is, one need to set "broken-cd" property also in o
Hi,
On Wed, Sep 30, 2015 at 4:44 PM, Krzysztof Kozlowski
wrote:
>> Switching the default meaning of "google,snow" to Rev5 is probably not
>> something we'd ever want to do, since it could confuse "rev3" boards
>> (which should be serviced by the rev4 dts). From comments in the
>> Chrome OS tree:
Hi,
On Tue, Sep 29, 2015 at 5:30 PM, Krzysztof Kozlowski
wrote:
> Now the exynos5250-snow.dts means in fact Rev4... but there is no
> information in DTS about it. I think adding compatible
> "google,snow-rev4" makes sense:
> 1. For informational purposes (this could be also handled with a comment
Javier,
On Tue, Sep 29, 2015 at 4:57 AM, Javier Martinez Canillas
wrote:
> There are 2 revisions of the Exynos5250 Snow Chromebook that were shipped:
> Rev4 and Rev5. The only difference between these 2 revisions is the codec,
> Rev4 has a max98095 codec while Rev5 has a max98090.
>
> Mainline on
Heiko,
On Fri, Aug 14, 2015 at 3:13 PM, Heiko Stübner wrote:
> Hi Shawn,
>
> Am Freitag, 14. August 2015, 16:34:35 schrieb Shawn Lin:
>> DesignWare MMC Controller can supports two types of DMA
>> mode: external dma and internal dma. We get a RK312x platform
>> integrated dw_mmc and ARM pl330 dma
Hi,
On Tue, Jul 28, 2015 at 9:20 AM, Alexey Klimov wrote:
> Hi Doug,
>
> On Tue, Jul 28, 2015 at 6:24 PM, Doug Anderson wrote:
>> Alexey,
>>
>> On Mon, Jul 27, 2015 at 2:28 PM, Alexey Klimov
>> wrote:
>>> Hi all,
>>>
>>> year(s
Alexey,
On Mon, Jul 27, 2015 at 2:28 PM, Alexey Klimov wrote:
> Hi all,
>
> year(s) ago it was discovered that MCT timer and ARM architectured
> timer
> are the same hardware with different interface. Here [1].
>
> I followed mail-list discussions about removing MCT and using arch
> timer for Exy
Hi,
On Fri, Jun 12, 2015 at 12:36 PM, Javier Martinez Canillas
wrote:
>>> registers are lost assuming the combiner was powered down, even the
>>> status register will be lost and you will not know exactly the wakeup
>>> reason right ?
>>>
>>
>> Good question, I didn't find in the documentation I'
z Canillas
> ---
> arch/arm/boot/dts/exynos5420-peach-pit.dts | 1 +
> arch/arm/boot/dts/exynos5800-peach-pi.dts | 1 +
> 2 files changed, 2 insertions(+)
Reviewed-by: Doug Anderson
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a
Andreas,
On Thu, Feb 19, 2015 at 9:56 AM, Andreas Färber wrote:
> Am 19.02.2015 um 18:44 schrieb Doug Anderson:
>> On Thu, Feb 19, 2015 at 1:44 AM, Mark Brown wrote:
>>> On Wed, Feb 18, 2015 at 07:25:58PM +0100, Andreas Färber wrote:
>>>
>>>> static
Andreas,
On Thu, Feb 19, 2015 at 6:13 AM, Andreas Färber wrote:
>> I see that a master clock (mclk) is added in patch 6/6 but the
>> max98088 codec driver does handle this clock.
>>
>> If the SoC XCLKOUT provides the master clock to the max98089
>> codec in Spring like is the case for the max9809
Mark,
On Thu, Feb 19, 2015 at 1:44 AM, Mark Brown wrote:
> On Wed, Feb 18, 2015 at 07:25:58PM +0100, Andreas Färber wrote:
>
>> static const struct of_device_id snow_of_match[] = {
>> + { .compatible = "google,snow-audio-max98089", },
>> { .compatible = "google,snow-audio-max98090", },
t; 1 file changed, 1 insertion(+), 1 deletion(-)
Nice catch, thanks!
Reviewed-by: Doug Anderson
Tested-by: Doug Anderson
--
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 h
Alim,
On Sun, Jan 4, 2015 at 2:43 PM, Alim Akhtar wrote:
>> You are breaking backward compatibility here. If your change is
>> merged then all old boards will instantly break. Since the "dts" and
>> code changes will likely be merged through different trees you'll end
>> up with a bunch of brok
Alim,
On Tue, Dec 30, 2014 at 10:43 PM, Alim Akhtar wrote:
> From: Seungwon Jeon
>
> ciu_div may not be common value for all speed mode.
> So, it needs to be attached to CLKSEL timing.
The more time I've spent looking at all of this stuff the less I like
the exynos bindings. Personally I'd pre
Javier,
On Wed, Nov 19, 2014 at 2:07 AM, Javier Martinez Canillas
wrote:
> Hello Doug,
>
> Thanks for your feedback.
>
> On 11/18/2014 06:50 PM, Doug Anderson wrote:
>> This is common practice in the Chrome OS tree, but we've gotten
>> pushback from upstream quest
Javier,
On Mon, Nov 17, 2014 at 9:43 AM, Javier Martinez Canillas
wrote:
> +&spi_1 {
> + status = "okay";
> + samsung,spi-src-clk = <0>;
> + num-cs = <1>;
> + cs-gpios = <&gpa2 5 0>;
> +
> + spidev@0 {
> + compatible = "spidev";
This is common practice
variable in mct controller driver), so 1.5
years. The broken code has been running for a long time, but that
doesn't mean that there isn't a subtle issue...
In any case, it seems like we should take this fix, assuming someone
has tested it well.
Reviewed-by: Doug Anderson
--
To unsubscr
ithin a device driver.
>
> It is better to call the regulator suspend prepare/finish functions
> from platform code instead so this patch reverts the mentioned commit.
>
> Suggested-by: Doug Anderson
> Signed-off-by: Javier Martinez Canillas
Reviewed-by: Doug Anderson
--
To
handlers
> defined by regulator drivers are not called when the system is suspended.
>
> Suggested-by: Doug Anderson
> Signed-off-by: Javier Martinez Canillas
> Reviewed-by: Doug Anderson
I think you forgot to carry Chanwoo's review:
Reviewed-by: Chanwoo Choi
I don't
Javier,
On Mon, Oct 20, 2014 at 9:58 AM, Javier Martinez Canillas
wrote:
>> It turns out that regulator_suspend_finish() actually returns an error
>> code. Could you print a warning if you see it?
>>
>
> Yes, I noticed this when looking at Chris patch for Rockchip but didn't
> re-spin
> because
handlers
> defined by regulator drivers are not called when the system is suspended.
>
> Suggested-by: Doug Anderson
> Signed-off-by: Javier Martinez Canillas
> ---
> arch/arm/mach-exynos/suspend.c | 18 ++
> 1 file changed, 18 insertions(+)
>
> diff --
handlers
> defined in regulator drivers are never called when the system is suspended.
>
> Suggested-by: Doug Anderson
> Signed-off-by: Javier Martinez Canillas
Could you also add a patch to your series ripping out the call in
"drivers/mfd/sec-core.c" since it doesn't
Hi,
On Wed, Oct 8, 2014 at 8:20 AM, Arnd Bergmann wrote:
> Why does it cause a regression though? Does this mean you are breaking
> any boot with an old DT file and a new kernel? That would be very
> bad, the driver is supposed to keep working with an existing dtb.
The old dts file specified com
Bartlomiej,
On Thu, Oct 2, 2014 at 10:24 AM, Bartlomiej Zolnierkiewicz
wrote:
>
> Hi,
>
> On Thursday, October 02, 2014 09:45:41 AM Doug Anderson wrote:
>> Bartiomiej
>>
>> On Thu, Oct 2, 2014 at 9:39 AM, Bartlomiej Zolnierkiewicz
>> wrote:
>> > O
Bartiomiej
On Thu, Oct 2, 2014 at 9:39 AM, Bartlomiej Zolnierkiewicz
wrote:
> On Thursday, October 02, 2014 09:19:08 AM Doug Anderson wrote:
>> Bartiomiej,
>>
>> On Thu, Oct 2, 2014 at 9:10 AM, Bartlomiej Zolnierkiewicz
>> wrote:
>> > Regulators for MMC2
is
> not specified. Fix it.
>
> Without this patch:
> - "mmc: dw_mmc: use mmc_regulator_get_supply to handle regulators"
> patch causes a SD card detection to fail
> - "mmc: dw_mmc: Support voltage changes" patch causes a boot hang
>
> This patch fixes both
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
>
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:
>> >
>>
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:
>> > This patch makes use of mmc_regulator_get_supply() to handle
>> > the vmmc and vqmmc regula
king over
>author for this patchset from Tomasz Figa.
>
> [1]: https://lkml.org/lkml/2014/9/29/99
> [2]: https://lkml.org/lkml/2014/9/18/130
> [3]: https://lkml.org/lkml/2014/9/27/2
> drivers/mfd/syscon.c | 96
> ++
> 1
ted most of these. They
may not show up in linuxnext yet, but that doesn't mean Andrew hasn't
taken them (I think).
> Doug Anderson (1):
> rtc: max77686: Allow the max77686 rtc to wakeup the system
http://ozlabs.org/~akpm/mmots/broken-out/rtc-max77686-allow-the-max77686-rt
Daniel,
On Wed, Sep 17, 2014 at 9:49 AM, Daniel Drake wrote:
> On Tue, Sep 16, 2014 at 4:15 PM, Doug Anderson wrote:
>> NOTE: I don't think that the builtin RTC is terribly important for any
>> exynos-based Chromebooks that I'm aware of. We rely on the RTC that&#x
9 {
> compatible = "maxim,max77686";
> interrupt-parent = <&gpx3>;
> interrupts = <2 0>;
In any case, there's nothing wrong with Javier's patch other than the
fact that it will eventually need to get merged with Andreas's, so:
Reviewed-by: Doug Anderson
--
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
/boot/dts/exynos5800-peach-pi.dts | 5 -
> 2 files changed, 8 insertions(+), 2 deletions(-)
Reviewed-by: Doug Anderson
--
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
Hi,
On Tue, Sep 16, 2014 at 8:20 AM, Javier Martinez Canillas
wrote:
> Hello Daniel,
>
> On Tue, Sep 16, 2014 at 5:03 PM, Daniel Drake wrote:
>> On Tue, Sep 16, 2014 at 7:48 AM, Javier Martinez Canillas
>> wrote:
Clock list for s3c-rtc device:
- rtc : CLK_RTC of CLK_GATE_IP_PERIR is g
to use recommended reset procedure
> are now merged in upstream.
> So you can go ahead and pick this change.
>
> arch/arm/boot/dts/exynos5420-peach-pit.dts |2 +-
> arch/arm/boot/dts/exynos5800-peach-pi.dts | 2 +-
> 2 files changed, 2 insertions(+), 2 deletion
Hi,
On Fri, Sep 12, 2014 at 8:54 AM, Javier Martinez Canillas
wrote:
> You are right, I completely forgot to check if that actually landed and to
> remove the note in that case...
>
> Maybe when the set is applied the note can be removed from this patch or do
> you think that I should re-spin the
Hi,
On Fri, Sep 12, 2014 at 1:17 AM, Javier Martinez Canillas
wrote:
> From: Doug Anderson
>
> The max77686 includes an RTC that keeps power during suspend. It's
> convenient to be able to use it as a wakeup source.
>
> NOTE: due to wakeup ordering problems this patc
Hi,
On Thu, Sep 11, 2014 at 11:03 AM, Mark Brown wrote:
> On Thu, Sep 11, 2014 at 10:22:32AM +0100, Grant Likely wrote:
>> On Wed, 10 Sep 2014 17:57:23 +0100, Mark Brown wrote:
>
>> > It's not quite as simple as just disabling PM - for example in the
>> > clocks case we've also got to worry abou
es.
>
> Signed-off-by: Vivek Gautam
> Signed-off-by: Javier Martinez Canillas
> ---
> arch/arm/configs/exynos_defconfig | 3 +++
> 1 file changed, 3 insertions(+)
I've no complaints about any of that.
Reviewed-by: Doug Anderson
--
To unsubscribe from this list: send th
Javier,
On Wed, Sep 10, 2014 at 3:19 AM, Javier Martinez Canillas
wrote:
> The downstream ChromeOS 3.8 kernel sets the clock frequency
> for the I2C bus 7 at 400kHz. Do the same change in mainline.
>
> Suggested-by: Doug Anderson
> Signed-off-by: Javier Martinez Canillas
> --
Mark,
On Wed, Sep 10, 2014 at 12:45 PM, Mark Brown wrote:
> On Wed, Sep 10, 2014 at 09:45:21AM -0700, Doug Anderson wrote:
>
>> Right now I know that clock disabling is supposed to be inhibited
>> during the early boot process. I think regulators too?
>
> No, for regula
Grant,
On Wed, Sep 10, 2014 at 9:29 AM, Grant Likely wrote:
> On Wed, Sep 10, 2014 at 4:39 PM, Mark Brown wrote:
>> On Wed, Sep 10, 2014 at 03:56:16PM +0100, Grant Likely wrote:
>>> On Wed, Sep 10, 2014 at 3:31 PM, Mark Brown wrote:
>>
>>> > As far as I can tell the problem here is coming from
Will,
On Wed, Sep 10, 2014 at 4:17 AM, Will Deacon wrote:
> On Mon, Sep 08, 2014 at 03:05:40PM +0100, Javier Martinez Canillas wrote:
>> Hello Will,
>
> Hi Javier,
>
>> Since many folks don't agree that hacking different subsystems is the way
>> forward I'll hold the patches and don't post them.
Hi,
On Mon, Sep 8, 2014 at 8:47 PM, wrote:
> Javier Martinez Canillas wrote:
>>
>> Hello Kukjin,
>>
> Hi,
>
>> On Wed, Aug 20, 2014 at 1:19 PM, Javier Martinez Canillas
>> wrote:
>> >
>> > This is a second version of the series that adds max77802 support for
>> > the Peach Pit and Pi boards. Th
insertions(+)
I would note that the downstream dts file has this i2c bus at 400kHz.
...but that's not a problem with your patch. Perhaps you could submit
that as a separate patch?
Reviewed-by: Doug Anderson
--
To unsubscribe from this list: send the line "unsubscribe linux-s
> arch/arm/boot/dts/exynos5800-peach-pi.dts | 6
> 3 files changed, 56 insertions(+)
Reviewed-by: Doug Anderson
--
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
gt; ---
> arch/arm/boot/dts/exynos5420-peach-pit.dts | 5 +
> 1 file changed, 5 insertions(+)
Reviewed-by: Doug Anderson
--
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 i
Hi,
On Tue, Sep 9, 2014 at 9:44 PM, Doug Anderson wrote:
> Javier / Rahul,
>
> On Tue, Aug 19, 2014 at 8:08 AM, Javier Martinez Canillas
> wrote:
>> From: Rahul Sharma
>>
>> Adding regulators for HDMI for Peach-pi board.
>>
>> Signed-off-by: Rah
gt; ---
> arch/arm/boot/dts/exynos5800-peach-pi.dts | 5 +
> 1 file changed, 5 insertions(+)
Reviewed-by: Doug Anderson
--
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
> ---
>
> v2: 1) Add blank line before hdmi regulators.
>
> arch/arm/boot/dts/exynos5800-peach-pi.dts | 5 +
> 1 file changed, 5 insertions(+)
Reviewed-by: Doug Anderson
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a me
Javier,
On Wed, Aug 20, 2014 at 4:19 AM, Javier Martinez Canillas
wrote:
> Exynos5420 based Peach Pit and Exynos5800 based Peach Pi boards
> uses a Maxim 77802 power management IC to drive regulators and
> its Real Time Clock. This patch adds support for this chip.
>
> These are the device nodes
Will,
On Mon, Sep 8, 2014 at 9:07 AM, Will Deacon wrote:
> On Mon, Sep 08, 2014 at 04:55:31PM +0100, Doug Anderson wrote:
>> So "simple-framebuffer" is added to the device tree here:
>>
>> https://chromium-review.googlesource.com/#/c/49358/2/board/samsung/smdk5250
Grant,
On Mon, Sep 8, 2014 at 5:20 AM, Grant Likely wrote:
> On Mon, Sep 8, 2014 at 12:21 PM, Will Deacon wrote:
>> On Sun, Sep 07, 2014 at 05:19:03PM +0100, Tomasz Figa wrote:
>>> At least for next 3.17-rc I'd suggest fixing this up in respective clock
>>> driver and dropping the hack only afte
Javier,
On Sun, Sep 7, 2014 at 11:09 PM, Javier Martinez Canillas
wrote:
> Hello Doug,
>
> On 09/08/2014 06:36 AM, Doug Anderson wrote:
>>
>> One (ugly?) solution would be to add a feature to your bootloader to
>> modify the device tree to mark regulators as "alw
Hi,
On Sun, Sep 7, 2014 at 8:52 AM, Tomasz Figa wrote:
> Now with regulators this is pretty straightforward, but with clocks I
> believe it's an open issue. AFAIR we've discussed this on MLs some time
> ago (at least I remember Doug commenting on that topic) and kind of
> concluded that SoC clock
Hi,
On Sun, Sep 7, 2014 at 8:52 AM, Tomasz Figa wrote:
> So I believe we've got a process issue here. If you don't have normal
> support for display hardware, but you want to keep the display
> operational thanks to bootloader already initializing it, you should not
> add anything to the kernel w
Will,
On Fri, Sep 5, 2014 at 5:22 AM, Will Deacon wrote:
> [Looks like it's not just Rutland that can't spell the address of the
> mailing list today. Fixed here, so please use this post in any replies].
>
> On Fri, Sep 05, 2014 at 12:57:04PM +0100, Will Deacon wrote:
>> Hi all,
>>
>> I'm one of
Hi,
On Thu, Aug 28, 2014 at 10:50 AM, Sonny Rao wrote:
> On Thu, Aug 28, 2014 at 8:50 AM, Doug Anderson wrote:
>> Ulf,
>>
>> On Thu, Aug 28, 2014 at 12:25 AM, Ulf Hansson wrote:
>>> On 27 August 2014 17:52, Doug Anderson wrote:
>>>> Ulf,
>>>
Jaehoon,
On Thu, Aug 28, 2014 at 1:43 AM, Jaehoon Chung wrote:
> On 08/28/2014 12:49 AM, Doug Anderson wrote:
>> Jaehoon,
>>
>> On Tue, Aug 26, 2014 at 9:47 PM, Jaehoon Chung
>> wrote:
>>> Doug,
>>>
>>> On 08/27/2014 01:14 PM, Doug Anders
Ulf,
On Thu, Aug 28, 2014 at 12:25 AM, Ulf Hansson wrote:
> On 27 August 2014 17:52, Doug Anderson wrote:
>> Ulf,
>>
>> On Wed, Aug 27, 2014 at 4:17 AM, Ulf Hansson wrote:
>>>> Now, we've got MMC_CAP_NEEDS_POLL, so dw_mmc will periodically be
>>>&
Ulf,
On Wed, Aug 27, 2014 at 4:17 AM, Ulf Hansson wrote:
>> Now, we've got MMC_CAP_NEEDS_POLL, so dw_mmc will periodically be
>> called to check the card detect line, but with vmmc and vqmmc off. It
>> will be unable to return a sensible value without actually turning on
>> vmmc and vqmmc.
>
> C
Jaehoon,
On Tue, Aug 26, 2014 at 9:47 PM, Jaehoon Chung wrote:
> Doug,
>
> On 08/27/2014 01:14 PM, Doug Anderson wrote:
>> Jaehoon,
>>
>> On Tue, Aug 26, 2014 at 8:48 PM, Jaehoon Chung
>> wrote:
>>> Hi, Doug,
>>>
>>> On 08/26/2014 1
Jaehoon,
On Tue, Aug 26, 2014 at 8:48 PM, Jaehoon Chung wrote:
> Hi, Doug,
>
> On 08/26/2014 12:25 AM, Doug Anderson wrote:
>> Jaehoon,
>>
>> On Mon, Aug 25, 2014 at 1:50 AM, Jaehoon Chung
>> wrote:
>>> On 08/25/2014 05:13 PM, Ulf Hansson wrote:
>
Ulf,
On Tue, Aug 26, 2014 at 12:37 AM, Ulf Hansson wrote:
> On 25 August 2014 17:20, Doug Anderson wrote:
>> Ulf,
>>
>> On Mon, Aug 25, 2014 at 1:13 AM, Ulf Hansson wrote:
>>> On 22 August 2014 20:27, Sonny Rao wrote:
>>>> On Fri, Aug 22, 2014 at 8:31
* the hardware reports OFF as the regulator operating mode.
> +* Default to operating mode NORMAL in that case.
> +*/
> + if (val == MAX77802_OPMODE_OFF)
> + max77802->opmode[id] = MAX77802_OPMODE_NORMAL;
> +
Ulf,
On Mon, Aug 25, 2014 at 1:31 AM, Ulf Hansson wrote:
> On 22 August 2014 22:38, Doug Anderson wrote:
>> Ulf,
>>
>> On Fri, Aug 22, 2014 at 8:35 AM, Ulf Hansson wrote:
>>> On 22 August 2014 15:47, Yuvaraj Kumar C D wrote:
>>>> From: Doug And
Javier,
On Mon, Aug 25, 2014 at 2:07 AM, Javier Martinez Canillas
wrote:
> Hello Yuvaraj,
>
> On 08/25/2014 10:22 AM, Yuvaraj Cd wrote:
Good question. I'm not that familiar with the dw_mmc host controller nor
its driver implementation so I'll let Yuvaraj or Doug to answer that.
>> Well,
Jaehoon,
On Mon, Aug 25, 2014 at 1:50 AM, Jaehoon Chung wrote:
> On 08/25/2014 05:13 PM, Ulf Hansson wrote:
>> On 22 August 2014 20:27, Sonny Rao wrote:
>>> On Fri, Aug 22, 2014 at 8:31 AM, Ulf Hansson wrote:
On 22 August 2014 15:47, Yuvaraj Kumar C D wrote:
> Exynos 5250 and 5420 bas
Ulf,
On Mon, Aug 25, 2014 at 1:13 AM, Ulf Hansson wrote:
> On 22 August 2014 20:27, Sonny Rao wrote:
>> On Fri, Aug 22, 2014 at 8:31 AM, Ulf Hansson wrote:
>>> On 22 August 2014 15:47, Yuvaraj Kumar C D wrote:
Exynos 5250 and 5420 based boards uses built-in CD# line for card
detectio
Jaehoon,
On Mon, Aug 25, 2014 at 5:32 AM, Jaehoon Chung wrote:
> On 08/22/2014 10:47 PM, Yuvaraj Kumar C D wrote:
>> This patch makes use of mmc_regulator_get_supply() to handle
>> the vmmc and vqmmc regulators.Also it moves the code handling
>> the these regulators to dw_mci_set_ios().It turned
Hi,
On Fri, Aug 22, 2014 at 3:02 PM, Javier Martinez Canillas
wrote:
> Hello Mark,
>
> On 08/22/2014 08:30 PM, Mark Brown wrote:
>>
>>> The problem is that one of these regulators is used as the vqmmc-supply
>>> (VCCQ/VDD_IO) so the mmc host controller driver disables it on
>>> MMC_POWER_OFF. Now
Ulf,
On Fri, Aug 22, 2014 at 8:35 AM, Ulf Hansson wrote:
> On 22 August 2014 15:47, Yuvaraj Kumar C D wrote:
>> From: Doug Anderson
>>
>> For UHS cards we need the ability to switch voltages from 3.3V to
>> 1.8V. Add support to the dw_mmc driver to handle this.
Kukjin,
On Fri, Aug 22, 2014 at 3:49 AM, Kukjin Kim wrote:
> Andreas Färber wrote:
>>
>> Allows them to be extended by reference.
>>
>> Reviewed-by: Doug Anderson
>> Signed-off-by: Andreas Färber
>> ---
>> v6 -> v7:
>> * Dropped uart* la
Guenter,
On Wed, Aug 20, 2014 at 9:42 PM, Guenter Roeck wrote:
> On Wed, Aug 20, 2014 at 09:10:31PM -0700, Doug Anderson wrote:
>> Guenter,
>>
>> On Tue, Aug 19, 2014 at 5:45 PM, Guenter Roeck wrote:
>> > machine_restart is supported on non-ARM platf
| 1 +
> 4 files changed, 30 insertions(+)
This patch doesn't apply cleanly with the in-flight (clk: rockchip:
protect critical clocks from getting disabled) patch from Heiko. It's
trivial to resolve and unclear which will land first, so I think it's
fine...
Reviewed-by: Doug Ande
t;
> arch/arm64/kernel/process.c | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Doug Anderson
--
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
rm64/kernel/process.c | 1 -
> 2 files changed, 2 deletions(-)
Reviewed-by: Doug Anderson
Tested-by: Doug Anderson
(FYI: all patches tested by me were tested on rk3288-evb)
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to
Stuebner
> ---
> v7: No change.
> v6: No change.
> v5: No change.
> v4: No change.
> v3: No change.
> v2: Added patch.
>
> drivers/power/reset/restart-poweroff.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Reviewed-by: Doug Anderson
Tested-by: Doug And
ile changed, 5 insertions(+), 6 deletions(-)
Reviewed-by: Doug Anderson
Tested-by: Doug Anderson
--
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
gt; v2: No change.
>
> include/linux/reboot.h | 3 ++
> kernel/reboot.c| 81
> ++
> 2 files changed, 84 insertions(+)
Reviewed-by: Doug Anderson
Tested-by: Doug Anderson
--
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
s(+), 12 deletions(-)
After comment nitfix:
Reviewed-by: Doug Anderson
--
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
nel.c | 2 +-
> drivers/input/keyboard/cros_ec_keyb.c | 2 +-
> drivers/mfd/cros_ec.c | 7 +++
> include/linux/mfd/cros_ec.h | 24 ++--
> 4 files changed, 27 insertions(+), 8 deletions(-)
Reviewed-by: Doug Anderson
--
To unsubscri
Javier,
On Tue, Aug 19, 2014 at 8:08 AM, Javier Martinez Canillas
wrote:
> The VCC/VDD and VCCQ/VDD_IO power supplies for the MMC are
> provided by the tps65090 fet4 and max77802 ldo4 regulators
> respectively. Add the phandle to the regulators tree nodes
> for the the dw_mmc device device.
>
> T
e're not going to do anything else we end the
request and unblock anyone waiting.
Signed-off-by: Doug Anderson
Signed-off-by: Yuvaraj Kumar C D
Acked-by: Seungwon Jeon
---
Changes in v2:
- Removed TODO
- Set cmd to NULL before calling dw_mci_request_end()
drive
Hi,
On Wed, May 21, 2014 at 2:08 AM, Seungwon Jeon wrote:
> On Wed, May 21, 2014, Doug Anderson wrote:
>> If we happened to get a data error at just the wrong time the dw_mmc
>> driver could get into a state where it would never complete its
>> request. That would leave th
Javier,
On Tue, Aug 12, 2014 at 9:44 AM, Javier Martinez Canillas
wrote:
> The tps65090 PMU is a component used in many ChromeOS devices
> so instead of having the same device tree definitions in many
> files, create a .dtsi fragment that can be included in DTS.
>
> This fragment is based on the
Hi,
On Mon, Aug 11, 2014 at 10:28 AM, Bartlomiej Zolnierkiewicz
wrote:
>
> Hi,
>
> On Monday, August 11, 2014 06:23:01 PM Javier Martinez Canillas wrote:
>> Hello,
>>
>> On 08/11/2014 05:59 PM, Doug Anderson wrote:
>> > Bartlomiej,
>> >
Bartlomiej,
On Mon, Aug 11, 2014 at 8:42 AM, Bartlomiej Zolnierkiewicz
wrote:
>
> Hi,
>
> On Monday, August 11, 2014 02:52:27 PM Javier Martinez Canillas wrote:
>> Hello Bartlomiej,
>>
>> On 08/11/2014 02:40 PM, Bartlomiej Zolnierkiewicz wrote:
>> >> index fc7d168..c390bb9 100644
>> >> --- a/arch
Javier,
On Mon, Aug 11, 2014 at 4:38 AM, Javier Martinez Canillas
wrote:
> Both Exynos5420 Peach Pit and Exynos5800 Peach Pi boards
> have a tps65090 PMU that has a number of switches (FETs)
> that are just on/off devices but they do have a current
> limit and the output voltage of the switch is
s/exynos5420-peach-pit.dts | 12 ++--
> arch/arm/boot/dts/exynos5800-peach-pi.dts | 12 ++--
> 2 files changed, 12 insertions(+), 12 deletions(-)
Matches my schematics. Kukjin: I think this could be applied to
for-next whenever it's convenient.
Acked-by: Doug Anderson
Javier,
On Mon, Aug 11, 2014 at 4:06 AM, Javier Martinez Canillas
wrote:
> Many Exynos5 boards (e.g: Snow, Peach Pit and Pi) have
> a SBS-compliant gas gauge battery. Enable it as module
> so the needed support is available for these boards.
>
> Suggested-by: Doug Anderson
Javier,
On Fri, Aug 8, 2014 at 3:26 PM, Javier Martinez Canillas
wrote:
>> I have some vague recollection that I set interrupts to pin-function
>> "0" by default for some reason (assuming they would go to 0xf when
>> interrupts were enabled). ...but I can't for the life of me remember
>> if it w
Hi,
On Fri, Aug 8, 2014 at 11:29 AM, Javier Martinez Canillas
wrote:
> Hello,
>
> On 08/08/2014 06:38 PM, Javier Martinez Canillas wrote:
>>
>>
>> It seems as if the first call to exynos_irq_set_type() that is made by OF is
>> a
>> no-op while the second call is the one that actually setups the
Fabio,
On Wed, Aug 6, 2014 at 6:35 PM, Fabio Estevam wrote:
> On Wed, Aug 6, 2014 at 10:08 PM, Javier Martinez Canillas
> wrote:
>
>> +&hsi2c_8 {
>> + status = "okay";
>> + clock-frequency = <333000>;
>
> Doesn't it work at the more standard 400kHz i2c frequency?
I'm pretty sure tha
Andreas,
On Sat, Aug 2, 2014 at 3:25 AM, Andreas Färber wrote:
> Hi,
>
> Am 02.08.2014 06:57, schrieb Doug Anderson:
>> On Fri, Aug 1, 2014 at 7:34 PM, Javier Martinez Canillas
>> wrote:
>>> On 08/02/2014 02:52 AM, Andreas Färber wrote:
>>>>
>>
1 - 100 of 757 matches
Mail list logo
