From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Hauke Mehrtens" <hauke@hauke-m.de>,
devicetree@vger.kernel.org, "Wim Van Sebroeck" <wim@iguana.be>,
"Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Grant Likely" <grant.likely@linaro.org>,
linux-watchdog@vger.kernel.org,
"Florian Fainelli" <florian@openwrt.org>,
m.adam--linux@adamis.de
Subject: Re: Extending wdt-gpio to be used on non-of (no DT) platforms
Date: Sat, 29 Mar 2014 17:56:28 +0400 [thread overview]
Message-ID: <1396101388.868708358@f391.i.mail.ru> (raw)
In-Reply-To: <CACna6rw5eryfe_yFzUs4oTv697LudngogmdOJNK-P8Qq12fJLQ@mail.gmail.com>
Sat, 29 Mar 2014 14:51:34 +0100 от Rafał Miłecki <zajec5@gmail.com>:
> 2014-03-29 14:33 GMT+01:00 Alexander Shiyan <shc_work@mail.ru>:
> > Sat, 29 Mar 2014 14:16:40 +0100 от Hauke Mehrtens <hauke@hauke-m.de>:
> >> The Huawei E970, the only device with a bcm47xx SoC which uses this gpio
> >> watchdog I know of, needs the gpio driver very early. It is not possible
> >> to deactivate the watchdogs, so it has to get trigged very early in the
> >
> > Why it cannot be deactivated?
> > The driver has been designed for ADM70x ICs, where watchdog is
> > deactivated by set GPIO to tristate.
>
> I'm not sure how to achieve tri-state with Broadcom SoC. Our code is in:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/bcma/driver_gpio.c
>
> We have bcma_chipco_gpio_control that sets if GPIO is controlled by
> ChipCommon (part of the SoC, one of many cores).
> Maybe setting GPIO to be *not* controlled by ChipCommon will make it tri-state?
>
> Any other ideas?
Usually this should be done by setup GPIO direction to input.
---
next prev parent reply other threads:[~2014-03-29 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 11:54 Extending wdt-gpio to be used on non-of (no DT) platforms Rafał Miłecki
2014-03-29 12:29 ` Alexander Shiyan
2014-03-29 13:16 ` Hauke Mehrtens
2014-03-29 13:33 ` Alexander Shiyan
2014-03-29 13:51 ` Rafał Miłecki
2014-03-29 13:56 ` Alexander Shiyan [this message]
2014-04-01 0:13 ` Guenter Roeck
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=1396101388.868708358@f391.i.mail.ru \
--to=shc_work@mail.ru \
--cc=devicetree@vger.kernel.org \
--cc=florian@openwrt.org \
--cc=grant.likely@linaro.org \
--cc=hauke@hauke-m.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-watchdog@vger.kernel.org \
--cc=m.adam--linux@adamis.de \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=wim@iguana.be \
--cc=zajec5@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