From: Pavel Fedin <p.fedin@samsung.com>
To: 'Rob Herring' <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.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>,
'Kukjin Kim' <kgene@kernel.org>,
'Krzysztof Kozlowski' <k.kozlowski@samsung.com>
Subject: RE: [PATCH v7 1/4] Documentation: dt-bindings: Describe SROMc configuration
Date: Wed, 11 Nov 2015 09:44:35 +0300 [thread overview]
Message-ID: <009301d11c4c$6eaa1eb0$4bfe5c10$@samsung.com> (raw)
In-Reply-To: <CAL_JsqLsD9gA2-AWYGaHvOuZhhDmE2BHmPMU2nJjPYEvQJdNHQ@mail.gmail.com>
Hello!
> > +- samsung,srom-timing : array of 6 integers, specifying bank timings in the
> > + following order: Tacp, Tcah, Tcoh, Tacc, Tcos, Tacs.
> > + Each value is specified in cycles and has the following
> > + meaning and valid range:
> > + Tacp : Page mode access cycle at Page mode (0 - 15)
> > + Tcah : Address holding time after CSn (0 - 15)
> > + Tcoh : Chip selection hold on OEn (0 - 15)
> > + Tacc : Access cycle (0 - 31, the actual time is N + 1)
> > + Tcos : Chip selection set-up before OEn (0 - 15)
> > + Tacs : Address set-up before CSn (0 - 15)
>
> This is not easily extended. Perhaps a property per value instead.
We had a discussion with Krzysztof about it, he agreed with this form of the property.
My concern was that it's just too much typing, and makes little sense because these
settings always go together. If register layout changes, or parameter set changes in
incompatible way, then it's another device, not exynos-srom anymore.
So would you agree with that, or is your position strong?
> > compatible = "samsung,exynos-srom";
> > - reg = <0x12570000 0x10>;
> > + reg = <0x12570000 0x14>;
> > +
> > + ethernet@3 {
> > + compatible = "smsc,lan9115";
> > + reg = <3 0 0x10000>; // Bank 3, offset = 0
> > + phy-mode = "mii";
> > + interrupt-parent = <&gpx0>;
> > + interrupts = <5 8>;
> > + reg-io-width = <2>;
> > + smsc,irq-push-pull;
> > + smsc,force-internal-phy;
> > +
> > + samsung,srom-config = <1 9 12 1 9 1 1>;
>
> This doesn't match the doc.
Damn, overlooked. :(
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-11-11 6:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 10:03 [PATCH v7 0/4] Exynos SROMc configuration and Ethernet support for SMDK5410 Pavel Fedin
2015-11-06 10:03 ` [PATCH v7 1/4] Documentation: dt-bindings: Describe SROMc configuration Pavel Fedin
2015-11-10 14:24 ` Rob Herring
2015-11-11 6:44 ` Pavel Fedin [this message]
2015-11-11 20:43 ` Rob Herring
2015-11-12 0:32 ` Krzysztof Kozlowski
2015-11-12 7:02 ` Pavel Fedin
2015-11-06 10:03 ` [PATCH v7 2/4] ARM: dts: Add SROMc to Exynos 5410 Pavel Fedin
2015-11-06 10:03 ` [PATCH v7 3/4] drivers: exynos-srom: Add support for bank configuration Pavel Fedin
2015-11-06 10:03 ` [PATCH v7 4/4] ARM: dts: Add Ethernet chip to SMDK5410 Pavel Fedin
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='009301d11c4c$6eaa1eb0$4bfe5c10$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).