From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Tony K Nadackal <tony.kn@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, tomasz.figa@gmail.com,
mturquette@linaro.org, kgene@kernel.org, a.kesavan@samsung.com,
bhushan.r@samsung.com
Subject: Re: [PATCH] clk: samsung: exynos7: Add clocks for MSCL block
Date: Mon, 22 Dec 2014 15:57:47 +0100 [thread overview]
Message-ID: <5498316B.9050906@samsung.com> (raw)
In-Reply-To: <000901d01ddc$eac0d120$c0427360$@samsung.com>
On 22/12/14 12:46, Tony K Nadackal wrote:
>>> diff --git a/Documentation/devicetree/bindings/clock/exynos7-clock.txt
>>> > > b/Documentation/devicetree/bindings/clock/exynos7-clock.txt
>>> > > index 6d3d5f8..d0e048c 100644
>>> > > --- a/Documentation/devicetree/bindings/clock/exynos7-clock.txt
>>> > > +++ b/Documentation/devicetree/bindings/clock/exynos7-clock.txt
>>> > > @@ -34,6 +34,7 @@ Required Properties for Clock Controller:
>>> > > - "samsung,exynos7-clock-peris"
>>> > > - "samsung,exynos7-clock-fsys0"
>>> > > - "samsung,exynos7-clock-fsys1"
>>> > > + - "samsung,exynos7-clock-mscl"
>> >
>> > I can't see anything controversial in the patch, but I've got some doubts
>> > regarding the compatible string. Is there a SoC named just "Exynos7"?
>
> Yes, We have an SoC named Exynos7.
> Please refer http://www.spinics.net/lists/linux-samsung-soc/msg36765.html
I've queued this patch for 3.20. Would be nice to have a Reviewed-by tag
from someone else who has access to the SoC documentation though.
Is Exynos7420 User Manual applicable to this?
Exynos 7 (Octa?) seems like a marketing name to me. In technical documents
there are usually more specific names used, like exynos7410 or exynos7420.
--
Regards,
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] clk: samsung: exynos7: Add clocks for MSCL block
Date: Mon, 22 Dec 2014 15:57:47 +0100 [thread overview]
Message-ID: <5498316B.9050906@samsung.com> (raw)
In-Reply-To: <000901d01ddc$eac0d120$c0427360$@samsung.com>
On 22/12/14 12:46, Tony K Nadackal wrote:
>>> diff --git a/Documentation/devicetree/bindings/clock/exynos7-clock.txt
>>> > > b/Documentation/devicetree/bindings/clock/exynos7-clock.txt
>>> > > index 6d3d5f8..d0e048c 100644
>>> > > --- a/Documentation/devicetree/bindings/clock/exynos7-clock.txt
>>> > > +++ b/Documentation/devicetree/bindings/clock/exynos7-clock.txt
>>> > > @@ -34,6 +34,7 @@ Required Properties for Clock Controller:
>>> > > - "samsung,exynos7-clock-peris"
>>> > > - "samsung,exynos7-clock-fsys0"
>>> > > - "samsung,exynos7-clock-fsys1"
>>> > > + - "samsung,exynos7-clock-mscl"
>> >
>> > I can't see anything controversial in the patch, but I've got some doubts
>> > regarding the compatible string. Is there a SoC named just "Exynos7"?
>
> Yes, We have an SoC named Exynos7.
> Please refer http://www.spinics.net/lists/linux-samsung-soc/msg36765.html
I've queued this patch for 3.20. Would be nice to have a Reviewed-by tag
from someone else who has access to the SoC documentation though.
Is Exynos7420 User Manual applicable to this?
Exynos 7 (Octa?) seems like a marketing name to me. In technical documents
there are usually more specific names used, like exynos7410 or exynos7420.
--
Regards,
Sylwester
next prev parent reply other threads:[~2014-12-22 14:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 7:33 [PATCH] clk: samsung: exynos7: Add clocks for MSCL block Tony K Nadackal
2014-12-17 7:33 ` Tony K Nadackal
2014-12-19 16:21 ` Sylwester Nawrocki
2014-12-19 16:21 ` Sylwester Nawrocki
2014-12-22 11:46 ` Tony K Nadackal
2014-12-22 11:46 ` Tony K Nadackal
2014-12-22 14:57 ` Sylwester Nawrocki [this message]
2014-12-22 14:57 ` Sylwester Nawrocki
2014-12-23 8:13 ` Tony K Nadackal
2014-12-23 8:13 ` Tony K Nadackal
2014-12-23 4:59 ` Pankaj Dubey
2014-12-23 4:59 ` Pankaj Dubey
2014-12-23 11:55 ` Sylwester Nawrocki
2014-12-23 11:55 ` Sylwester Nawrocki
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=5498316B.9050906@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=a.kesavan@samsung.com \
--cc=bhushan.r@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=tomasz.figa@gmail.com \
--cc=tony.kn@samsung.com \
/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.