All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Matthew McClintock <mmcclint@codeaurora.org>, twp@codeaurora.org
Cc: linux-watchdog@vger.kernel.org, Wim Van Sebroeck <wim@iguana.be>
Subject: Re: [PATCH v2 2/3] watchdog: qcom: add option for standalone watchdog not in timer block
Date: Tue, 28 Jun 2016 19:01:21 -0700	[thread overview]
Message-ID: <57732BF1.3060801@roeck-us.net> (raw)
In-Reply-To: <75720F79-5C72-4FFD-A391-427C5D336AE0@codeaurora.org>

On 06/28/2016 02:24 PM, Matthew McClintock wrote:
>
>> On Jun 28, 2016, at 3:45 PM, Thomas Pedersen <twp@codeaurora.org> wrote:
>>
>> I'll rectify the missing documentation, and am fine with changing the name to
>> kpss-core.
>
> I think the previous conclusion was to rename it to something with ipq4019 in the compat, but I’d suggest checking the comments in patchworks on the previous patches.
>

I looked up my notes. Here is what I had suggested earlier:

"The property name should probably be something like 'qcom,kpss-wdt'
(or 'qcom,kpss-watchdog' ?), possibly in addition to 'qcom,kpss-ipq4019-wdt'
and 'qcom,kpss-msm8916-wdt'."

Guenter


  reply	other threads:[~2016-06-29  2:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 18:35 [PATCH v2 1/3] watchdog: qcom: update device tree bindings Thomas Pedersen
2016-06-28 18:35 ` [PATCH v2 2/3] watchdog: qcom: add option for standalone watchdog not in timer block Thomas Pedersen
2016-06-28 19:47   ` Guenter Roeck
2016-06-28 20:45     ` Thomas Pedersen
2016-06-28 21:24       ` Matthew McClintock
2016-06-29  2:01         ` Guenter Roeck [this message]
2016-06-28 18:35 ` [PATCH v2 3/3] watchdog: qcom: configure BARK time in addition to BITE time Thomas Pedersen

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=57732BF1.3060801@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=mmcclint@codeaurora.org \
    --cc=twp@codeaurora.org \
    --cc=wim@iguana.be \
    /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.