From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Thomas Abraham <thomas.abraham@linaro.org>
Cc: kgene.kim@samsung.com, Grant Likely <grant.likely@secretlab.ca>,
linux-mmc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, cjb@laptop.org,
rob.herring@calxeda.com, linux-samsung-soc@vger.kernel.org,
ben-linux@fluff.org
Subject: Re: [PATCH 6/6] mmc: sdhci-s3c: Add device tree support
Date: Thu, 05 Jan 2012 17:22:56 +0100 [thread overview]
Message-ID: <4F05CE60.5090402@samsung.com> (raw)
In-Reply-To: <CAJuYYwTMpde-528t=vQnbkJv_gG7xuOr05b1K-+H-RxYRX0iEQ@mail.gmail.com>
Hi Thomas,
On 01/05/2012 04:45 PM, Thomas Abraham wrote:
>>>> On Thu, Nov 03, 2011 at 02:06:03AM +0530, Thomas Abraham wrote:
>>>>> Add device tree based discovery support for Samsung's sdhci controller
>>>>>
>>>>> Cc: Ben Dooks <ben-linux@fluff.org>
>>>>> Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
>>>>> ---
>>>>> +Example:
>>>>> + sdhci@12530000 {
>>>>> + compatible = "samsung,exynos4210-sdhci";
>>>>> + reg = <0x12530000 0x100>;
>>>>> + interrupts = <139>;
>>>>> + samsung,sdhci-bus-width = <4>;
>>>>> + linux,mmc_cap_4_bit_data;
>>>>
>>>> Following on from my reply on patch 5, this is an example of exactly
>>>> what I'm talking about. This node both sets bus-width to '4', and
>>>> sets the 4_bit_data flag. Don't you think that the driver would be
>>>> smart enough to set the 4_bit_data flag when the bus width was set to
>>>> 4?
>>>
>>> Yes, that is true. I will modify the driver based on your comments and
>>> resubmit this patch.
>>
>> Are we going to have those patches in 3.3-rc1 or only in 3.4 ?
>
> Sorry for the delaying in completing this patchset. I will redo this
> patchset and submit it soon. But 3.3-rc1 looks unlikely.
Ok, thanks. It's fine, there is no rush. I was just curious because we have
reused this sdhci driver update series and it seemed essential for initial
DT support on Exynos4 machines. Just FYI I have prepared initial DT support
patches for the S5P MIPI-CSI2 (s5p-mipi-csis) receiver driver.
But the whole camera subsystem needs more work, i.e. resource dependencies
(clock) between all involved devices (like image sensors and video capture
platform devices) need to be resolved and method of registering sub-devices
in the V4L2 core will likely need to be changed.
--
Thanks,
Sylwester
WARNING: multiple messages have this Message-ID (diff)
From: s.nawrocki@samsung.com (Sylwester Nawrocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/6] mmc: sdhci-s3c: Add device tree support
Date: Thu, 05 Jan 2012 17:22:56 +0100 [thread overview]
Message-ID: <4F05CE60.5090402@samsung.com> (raw)
In-Reply-To: <CAJuYYwTMpde-528t=vQnbkJv_gG7xuOr05b1K-+H-RxYRX0iEQ@mail.gmail.com>
Hi Thomas,
On 01/05/2012 04:45 PM, Thomas Abraham wrote:
>>>> On Thu, Nov 03, 2011 at 02:06:03AM +0530, Thomas Abraham wrote:
>>>>> Add device tree based discovery support for Samsung's sdhci controller
>>>>>
>>>>> Cc: Ben Dooks <ben-linux@fluff.org>
>>>>> Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
>>>>> ---
>>>>> +Example:
>>>>> + sdhci at 12530000 {
>>>>> + compatible = "samsung,exynos4210-sdhci";
>>>>> + reg = <0x12530000 0x100>;
>>>>> + interrupts = <139>;
>>>>> + samsung,sdhci-bus-width = <4>;
>>>>> + linux,mmc_cap_4_bit_data;
>>>>
>>>> Following on from my reply on patch 5, this is an example of exactly
>>>> what I'm talking about. This node both sets bus-width to '4', and
>>>> sets the 4_bit_data flag. Don't you think that the driver would be
>>>> smart enough to set the 4_bit_data flag when the bus width was set to
>>>> 4?
>>>
>>> Yes, that is true. I will modify the driver based on your comments and
>>> resubmit this patch.
>>
>> Are we going to have those patches in 3.3-rc1 or only in 3.4 ?
>
> Sorry for the delaying in completing this patchset. I will redo this
> patchset and submit it soon. But 3.3-rc1 looks unlikely.
Ok, thanks. It's fine, there is no rush. I was just curious because we have
reused this sdhci driver update series and it seemed essential for initial
DT support on Exynos4 machines. Just FYI I have prepared initial DT support
patches for the S5P MIPI-CSI2 (s5p-mipi-csis) receiver driver.
But the whole camera subsystem needs more work, i.e. resource dependencies
(clock) between all involved devices (like image sensors and video capture
platform devices) need to be resolved and method of registering sub-devices
in the V4L2 core will likely need to be changed.
--
Thanks,
Sylwester
next prev parent reply other threads:[~2012-01-05 16:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 20:35 [PATCH 0/6] mmc: sdhci-s3c: Rework platform data and add device tree support Thomas Abraham
2011-11-02 20:35 ` Thomas Abraham
2011-11-02 20:35 ` [PATCH 1/6] mmc: sdhci-s3c: Remove usage of clk_type member in platform data Thomas Abraham
2011-11-02 20:35 ` Thomas Abraham
[not found] ` <1320266163-15292-1-git-send-email-thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-11-02 20:35 ` [PATCH 2/6] arm: exynos4: use 'exynos4-sdhci' as device name for sdhci controllers Thomas Abraham
2011-11-02 20:35 ` Thomas Abraham
2011-11-02 20:36 ` [PATCH 3/6] arm: samsung: remove all uses of clk_type member in sdhci platform data Thomas Abraham
2011-11-02 20:36 ` Thomas Abraham
2011-11-02 20:36 ` [PATCH 4/6] mmc: sdhci-s3c: Keep a copy of platform data and use it Thomas Abraham
2011-11-02 20:36 ` Thomas Abraham
2011-11-02 20:36 ` [PATCH 5/6] mmc: Add OF bindings support for mmc host controller capabilities Thomas Abraham
2011-11-02 20:36 ` Thomas Abraham
2011-11-04 19:57 ` Olof Johansson
2011-11-04 19:57 ` Olof Johansson
[not found] ` <20111104195717.GA3045-O5ziIzlqnXUVNXGz7ipsyg@public.gmane.org>
2011-11-07 14:21 ` Thomas Abraham
2011-11-07 14:21 ` Thomas Abraham
2011-11-07 21:15 ` Grant Likely
2011-11-07 21:15 ` Grant Likely
2011-11-08 15:19 ` Thomas Abraham
2011-11-08 15:19 ` Thomas Abraham
2011-11-02 20:36 ` [PATCH 6/6] mmc: sdhci-s3c: Add device tree support Thomas Abraham
2011-11-02 20:36 ` Thomas Abraham
2011-11-07 21:17 ` Grant Likely
2011-11-07 21:17 ` Grant Likely
2011-11-08 15:23 ` Thomas Abraham
2011-11-08 15:23 ` Thomas Abraham
2012-01-04 15:37 ` Sylwester Nawrocki
2012-01-04 15:37 ` Sylwester Nawrocki
2012-01-05 15:45 ` Thomas Abraham
2012-01-05 15:45 ` Thomas Abraham
2012-01-05 16:22 ` Sylwester Nawrocki [this message]
2012-01-05 16:22 ` Sylwester Nawrocki
2012-01-05 16:43 ` Thomas Abraham
2012-01-05 16:43 ` Thomas Abraham
2012-01-30 9:51 ` Heiko Stübner
2012-01-30 9:51 ` Heiko Stübner
2012-01-30 19:01 ` Grant Likely
2012-01-30 19:01 ` Grant Likely
2012-01-31 6:13 ` Heiko Stübner
2012-01-31 6:13 ` Heiko Stübner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F05CE60.5090402@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=ben-linux@fluff.org \
--cc=cjb@laptop.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=thomas.abraham@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.