From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: dts: max77686: Add DTS file for max77686 PMIC
Date: Sun, 27 Jan 2013 14:17:54 +0800 [thread overview]
Message-ID: <20130127061751.GF8952@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CADoNuNeF_fw1uuMt89=gZm-A2R6FHGpr-kCgFkOY0xXpA9+Jzw@mail.gmail.com>
On Sat, Jan 26, 2013 at 03:06:53PM +0900, Dongjin Kim wrote:
> Hello Mark,
>
> Yes, this is not ARM-specific chip at all. Just wanted to be reviewed
> by you and others if the format is ok before integrating to my board
> file. I had sent similar one before,
> https://patchwork.kernel.org/patch/1287711, and you advised that was
> too board specific. And plan to integrate like OMAP boards have with
> twl6030.dtsi and twl6040.dtsi.
> If would be nice if somewhere you specify a directory for such device files.
I think we need to create one, not quite sure where though. drivers/of
perhaps but that's a bit non-idiomatic, or possibly something top level.
firmware might do too.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130127/6cbc0e71/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dongjin Kim <tobetter@gmail.com>
Cc: yadi.brar01@gmail.com, Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] ARM: dts: max77686: Add DTS file for max77686 PMIC
Date: Sun, 27 Jan 2013 14:17:54 +0800 [thread overview]
Message-ID: <20130127061751.GF8952@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CADoNuNeF_fw1uuMt89=gZm-A2R6FHGpr-kCgFkOY0xXpA9+Jzw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
On Sat, Jan 26, 2013 at 03:06:53PM +0900, Dongjin Kim wrote:
> Hello Mark,
>
> Yes, this is not ARM-specific chip at all. Just wanted to be reviewed
> by you and others if the format is ok before integrating to my board
> file. I had sent similar one before,
> https://patchwork.kernel.org/patch/1287711, and you advised that was
> too board specific. And plan to integrate like OMAP boards have with
> twl6030.dtsi and twl6040.dtsi.
> If would be nice if somewhere you specify a directory for such device files.
I think we need to create one, not quite sure where though. drivers/of
perhaps but that's a bit non-idiomatic, or possibly something top level.
firmware might do too.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-27 6:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 18:46 [PATCH RESEND] ARM: dts: max77686: Add DTS file for max77686 PMIC Dongjin Kim
2013-01-24 18:46 ` Dongjin Kim
2013-01-26 5:06 ` Mark Brown
2013-01-26 5:06 ` Mark Brown
2013-01-26 6:06 ` Dongjin Kim
2013-01-26 6:06 ` Dongjin Kim
2013-01-27 6:17 ` Mark Brown [this message]
2013-01-27 6:17 ` Mark Brown
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=20130127061751.GF8952@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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.