From: Tomasz Figa <t.figa@samsung.com>
To: Rob Herring <robherring2@gmail.com>
Cc: Cho KyongHo <pullip.cho@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>,
Linux IOMMU <iommu@lists.linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Samsung SOC <linux-samsung-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Joerg Roedel <joro@8bytes.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Prathyush <prathyush.k@samsung.com>,
Rahul Sharma <rahul.sharma@samsung.com>,
Subash Patel <supash.ramaswamy@linaro.org>,
Grant Grundler <grundler@chromium.org>,
Antonios Motakis <a.motakis@virtualopensystems.com>,
kvmarm@lists.cs.columbia.edu,
Sachin Kamat <sachin.kamat@linaro.org>
Subject: Re: [PATCH v9 07/16] iommu/exynos: support for device tree
Date: Fri, 09 Aug 2013 17:02:02 +0200 [thread overview]
Message-ID: <33568604.vCtP4hvQ1q@amdc1227> (raw)
In-Reply-To: <CAL_JsqKM_YP0Cj3Uo7TeCVcKcbzzsuK3yxTSn6pG8qGFOnZAiA@mail.gmail.com>
On Friday 09 of August 2013 08:28:09 Rob Herring wrote:
> On Fri, Aug 9, 2013 at 1:37 AM, Cho KyongHo <pullip.cho@samsung.com>
wrote:
> > On Fri, 09 Aug 2013 00:41:25 +0200, Tomasz Figa wrote:
> >> Hi KyongHo,
> >>
> >> On Thursday 08 of August 2013 18:38:49 Cho KyongHo wrote:
> >> > This commit adds device tree support for System MMU.
> >> > This also include the following changes and enhancements:
> >> >
> >> > * use managed device helper functions.
> >> > Simplyfies System MMU device driver.
> >> >
> >> > * use only a single clock descriptor.
> >> > System MMU device descriptor is seperate if it is imposible to make
> >> > a single clock descriptor to make a device descriptor for a group of
> >> > System MMUs.
> >> >
> >> > * removed dbgname member from sysmmu_drvdata structure.
> >> > debugging kernel message for a System MMU is distinguisheable with
> >> > the
> >> > name of device descroptors.
> >>
> >> Please put all these three changes in separate patches. This patch is
> >> hard to review with all the changes mixed together...
>
> Agreed.
>
> > Ok.
> >
> >> In addition, I believe this is the patch that should be adding device
> >> tree binding documentation, not the 6/16 one, as this is where
> >> actually support for this binding gets added to the kernel.
> >
> > Oh, I didn't know that devicetree binding description and
> > implementation need to be in the same patch.
> > I will do as you advised.
>
> Actually, I prefer the binding docs be separate patches. The reason
> being so we can get closer to having them in a separate repository.
> Also, then the binding can be acked separately from the kernel
> implementation using the binding.
OK. This is a good point. So maybe let's fully define this order to be as
following (and have first best practice for the DT binding best practices
that need to be defined):
Bindings documentation should be added with a separate patch, before any
user of these bindings is introduced.
What do you think?
Best regards,
Tomasz
prev parent reply other threads:[~2013-08-09 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 9:38 [PATCH v9 07/16] iommu/exynos: support for device tree Cho KyongHo
2013-08-08 22:41 ` Tomasz Figa
2013-08-09 6:37 ` Cho KyongHo
2013-08-09 8:30 ` Tomasz Figa
2013-08-12 2:13 ` Cho KyongHo
2013-08-09 13:28 ` Rob Herring
2013-08-09 15:02 ` Tomasz Figa [this message]
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=33568604.vCtP4hvQ1q@amdc1227 \
--to=t.figa@samsung.com \
--cc=a.motakis@virtualopensystems.com \
--cc=devicetree@vger.kernel.org \
--cc=grundler@chromium.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kgene.kim@samsung.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=prathyush.k@samsung.com \
--cc=pullip.cho@samsung.com \
--cc=rahul.sharma@samsung.com \
--cc=robherring2@gmail.com \
--cc=sachin.kamat@linaro.org \
--cc=supash.ramaswamy@linaro.org \
--cc=tomasz.figa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox