From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Kukjin Kim <kgene@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Javier Martinez Canillas <javier@osg.samsung.com>,
Heiko Stuebner <heiko@sntech.de>, Chen-Yu Tsai <wens@csie.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: Consolidate SRAM bindings from all vendors
Date: Thu, 22 Oct 2015 15:34:47 +0200 [thread overview]
Message-ID: <20151022133447.GZ10947@lukather> (raw)
In-Reply-To: <5628AA23.5070608@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 3007 bytes --]
On Thu, Oct 22, 2015 at 06:19:31PM +0900, Krzysztof Kozlowski wrote:
> On 22.10.2015 18:05, Maxime Ripard wrote:
> > Hi,
> >
> > On Thu, Oct 22, 2015 at 10:25:28AM +0900, Krzysztof Kozlowski wrote:
> >> SRAM bindings for various SoCs, using the mmio-sram genalloc
> >> API, are spread over different places - per SoC vendor. Since all of
> >> these are quite similar (they depend on mmio-sram) move them to a common
> >> place.
> >>
> >> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> >> Cc: Heiko Stuebner <heiko@sntech.de>
> >> Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
> >> Cc: Chen-Yu Tsai <wens@csie.org>
> >> Cc: Kukjin Kim <kgene@kernel.org>
> >> Suggested-by: Rob Herring <robh+dt@kernel.org>
> >>
> >> ---
> >>
> >> Changes since v1:
> >> 1. New patch. Extended suggestion from Rob.
> >> ---
> >> .../bindings/{arm/rockchip/pmu-sram.txt => sram/rockchip-pmu-sram.txt} | 0
> >> .../bindings/{arm/rockchip/smp-sram.txt => sram/rockchip-smp-sram.txt} | 0
> >> .../bindings/{arm/exynos/smp-sysram.txt => sram/samsung-sram.txt} | 0
> >> Documentation/devicetree/bindings/{misc => sram}/sram.txt | 0
> >> .../devicetree/bindings/{soc/sunxi/sram.txt => sram/sunxi-sram.txt} | 0
> >> 5 files changed, 0 insertions(+), 0 deletions(-)
> >> rename Documentation/devicetree/bindings/{arm/rockchip/pmu-sram.txt => sram/rockchip-pmu-sram.txt} (100%)
> >> rename Documentation/devicetree/bindings/{arm/rockchip/smp-sram.txt => sram/rockchip-smp-sram.txt} (100%)
> >> rename Documentation/devicetree/bindings/{arm/exynos/smp-sysram.txt => sram/samsung-sram.txt} (100%)
> >> rename Documentation/devicetree/bindings/{misc => sram}/sram.txt (100%)
> >> rename Documentation/devicetree/bindings/{soc/sunxi/sram.txt => sram/sunxi-sram.txt} (100%)
> >
> > I'm not sure about that one. The SRAM bindins we have for sunxi is for
> > an SRAM controller, that maps the SRAM either to the CPU or to the
> > devices.
> >
> > It's not really related to the other users, and wouldn't it be
> > confusing to have a driver in drivers/soc, and a Documentation in
> > another sub-directory?
>
> I guess the only relation to other users is the "mmio-sram". In the same
> time this is still similar to e.g. Samsung's sram bindings (where the
> memory is mapped to CPU only).
>
> Being located in drivers/soc is not an issue here - code for other
> vendors may be moved there as well in the future.
>
> Of course I do not insist. Actually Rob's comment was only about moving
> sram.txt and Samsung's sram to common place.
>
> Anyway I will be sending v3 of these because while looking more
> carefully I found hard-coded paths to bindings/misc/sram.txt. I'll fix
> it in next version.
I didn't really have the context. If Rob feels like we should do that,
then go ahead.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] dt-bindings: Consolidate SRAM bindings from all vendors
Date: Thu, 22 Oct 2015 15:34:47 +0200 [thread overview]
Message-ID: <20151022133447.GZ10947@lukather> (raw)
In-Reply-To: <5628AA23.5070608@samsung.com>
On Thu, Oct 22, 2015 at 06:19:31PM +0900, Krzysztof Kozlowski wrote:
> On 22.10.2015 18:05, Maxime Ripard wrote:
> > Hi,
> >
> > On Thu, Oct 22, 2015 at 10:25:28AM +0900, Krzysztof Kozlowski wrote:
> >> SRAM bindings for various SoCs, using the mmio-sram genalloc
> >> API, are spread over different places - per SoC vendor. Since all of
> >> these are quite similar (they depend on mmio-sram) move them to a common
> >> place.
> >>
> >> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> >> Cc: Heiko Stuebner <heiko@sntech.de>
> >> Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
> >> Cc: Chen-Yu Tsai <wens@csie.org>
> >> Cc: Kukjin Kim <kgene@kernel.org>
> >> Suggested-by: Rob Herring <robh+dt@kernel.org>
> >>
> >> ---
> >>
> >> Changes since v1:
> >> 1. New patch. Extended suggestion from Rob.
> >> ---
> >> .../bindings/{arm/rockchip/pmu-sram.txt => sram/rockchip-pmu-sram.txt} | 0
> >> .../bindings/{arm/rockchip/smp-sram.txt => sram/rockchip-smp-sram.txt} | 0
> >> .../bindings/{arm/exynos/smp-sysram.txt => sram/samsung-sram.txt} | 0
> >> Documentation/devicetree/bindings/{misc => sram}/sram.txt | 0
> >> .../devicetree/bindings/{soc/sunxi/sram.txt => sram/sunxi-sram.txt} | 0
> >> 5 files changed, 0 insertions(+), 0 deletions(-)
> >> rename Documentation/devicetree/bindings/{arm/rockchip/pmu-sram.txt => sram/rockchip-pmu-sram.txt} (100%)
> >> rename Documentation/devicetree/bindings/{arm/rockchip/smp-sram.txt => sram/rockchip-smp-sram.txt} (100%)
> >> rename Documentation/devicetree/bindings/{arm/exynos/smp-sysram.txt => sram/samsung-sram.txt} (100%)
> >> rename Documentation/devicetree/bindings/{misc => sram}/sram.txt (100%)
> >> rename Documentation/devicetree/bindings/{soc/sunxi/sram.txt => sram/sunxi-sram.txt} (100%)
> >
> > I'm not sure about that one. The SRAM bindins we have for sunxi is for
> > an SRAM controller, that maps the SRAM either to the CPU or to the
> > devices.
> >
> > It's not really related to the other users, and wouldn't it be
> > confusing to have a driver in drivers/soc, and a Documentation in
> > another sub-directory?
>
> I guess the only relation to other users is the "mmio-sram". In the same
> time this is still similar to e.g. Samsung's sram bindings (where the
> memory is mapped to CPU only).
>
> Being located in drivers/soc is not an issue here - code for other
> vendors may be moved there as well in the future.
>
> Of course I do not insist. Actually Rob's comment was only about moving
> sram.txt and Samsung's sram to common place.
>
> Anyway I will be sending v3 of these because while looking more
> carefully I found hard-coded paths to bindings/misc/sram.txt. I'll fix
> it in next version.
I didn't really have the context. If Rob feels like we should do that,
then go ahead.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151022/791cc465/attachment-0001.sig>
next prev parent reply other threads:[~2015-10-22 13:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 1:25 [PATCH v2 1/3] dt-bindings: Consolidate SRAM bindings from all vendors Krzysztof Kozlowski
2015-10-22 1:25 ` Krzysztof Kozlowski
2015-10-22 1:25 ` Krzysztof Kozlowski
2015-10-22 1:25 ` [PATCH v2 2/3] dt-bindings: Consolidate Exynos SoC bindings Krzysztof Kozlowski
2015-10-22 1:25 ` Krzysztof Kozlowski
2015-10-22 1:25 ` [PATCH v2 3/3] dt-bindings: EXYNOS: Document compatibles from other vendors Krzysztof Kozlowski
2015-10-22 1:25 ` Krzysztof Kozlowski
2015-10-22 9:05 ` [PATCH v2 1/3] dt-bindings: Consolidate SRAM bindings from all vendors Maxime Ripard
2015-10-22 9:05 ` Maxime Ripard
2015-10-22 9:19 ` Krzysztof Kozlowski
2015-10-22 9:19 ` Krzysztof Kozlowski
2015-10-22 13:34 ` Maxime Ripard [this message]
2015-10-22 13:34 ` Maxime Ripard
2015-10-22 13:51 ` Rob Herring
2015-10-22 13:51 ` Rob Herring
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=20151022133447.GZ10947@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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.