From: pullip.cho@samsung•com (Cho KyongHo)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v8 07/12] iommu/exynos: support for device tree
Date: Thu, 01 Aug 2013 22:14:03 +0900 [thread overview]
Message-ID: <003a01ce8eb8$fe946db0$fbbd4910$@samsung.com> (raw)
In-Reply-To: <1743111.Ek7FldnHal@flatron>
> -----Original Message-----
> From: Tomasz Figa [mailto:tomasz.figa at gmail.com]
> Sent: Saturday, July 27, 2013 11:07 PM
>
> Hi,
>
> On Friday 26 of July 2013 20:28:36 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.
> >
> > Signed-off-by: Cho KyongHo <pullip.cho@samsung•com>
> > ---
> > drivers/iommu/Kconfig | 5 +-
> > drivers/iommu/exynos-iommu.c | 182
> > ++++++++++++++++-------------------------- 2 files changed, 70
> > insertions(+), 117 deletions(-)
>
> Whenever you introduce or modify (extend) a device tree binding please
> don't forget about reflecting that in documentation
> (Documentation/devicetree/bindings) and CCing devicetree mailing list
> (devicetree at vger.kernel.org). Both of these steps are necessary to get any
> device tree stuff merged.
>
Oh I see.
Thank you for advice.
> Best regards,
> Tomasz
next prev parent reply other threads:[~2013-08-01 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 11:28 [PATCH v8 07/12] iommu/exynos: support for device tree Cho KyongHo
2013-07-27 14:06 ` Tomasz Figa
2013-08-01 13:14 ` Cho KyongHo [this message]
2013-08-02 17:17 ` Bartlomiej Zolnierkiewicz
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='003a01ce8eb8$fe946db0$fbbd4910$@samsung.com' \
--to=pullip.cho@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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