From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jonathan Bakker <xc-racer2@live.ca>
Cc: kgene@kernel.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/13] arm: dts: s5pv210: fascinate4g: Add sleep GPIO configuration
Date: Fri, 1 May 2020 15:10:18 +0200 [thread overview]
Message-ID: <20200501131018.GA5154@kozik-lap> (raw)
In-Reply-To: <BN6PR04MB06605BE9E1559751E083B4E4A3AC0@BN6PR04MB0660.namprd04.prod.outlook.com>
On Tue, Apr 28, 2020 at 04:49:36PM -0700, Jonathan Bakker wrote:
> Hi Krzysztof,
>
> On 2020-04-28 3:02 a.m., Krzysztof Kozlowski wrote:
> > On Sun, Apr 26, 2020 at 11:35:53AM -0700, Jonathan Bakker wrote:
> >> In order to minimize leakage current during sleep, set a config
> >> for sleep GPIOs.
> >>
> >> Signed-off-by: Jonathan Bakker <xc-racer2@live.ca>
> >> ---
> >> arch/arm/boot/dts/s5pv210-fascinate4g.dts | 242 ++++++++++++++++++++++
> >> 1 file changed, 242 insertions(+)
> >>
> >> diff --git a/arch/arm/boot/dts/s5pv210-fascinate4g.dts b/arch/arm/boot/dts/s5pv210-fascinate4g.dts
> >> index 07a8d9bbe5b8..94dcb9b64b9a 100644
> >> --- a/arch/arm/boot/dts/s5pv210-fascinate4g.dts
> >> +++ b/arch/arm/boot/dts/s5pv210-fascinate4g.dts
> >> @@ -36,3 +36,245 @@
> >> };
> >> };
> >> };
> >> +
> >> +&pinctrl0 {
> >> + pinctrl-names = "default";
> >> + pinctrl-0 = <&sleep_cfg>;
> >> +
> >> + sleep_cfg: sleep-cfg {
> >> + PIN_SLP(gpa0-0, PREV, NONE);
> >> + PIN_SLP(gpa0-1, PREV, NONE);
> >> + PIN_SLP(gpa0-2, PREV, NONE);
> >> + PIN_SLP(gpa0-3, OUT1, NONE);
> >
> > I would be happy to see some reasoning why certain pins have disabled
> > pull down (e.g. they are not connected or you use the same configuration
> > as running one) and why you set them as output.
> >
>
> Mostly it's copied from the vendor kernel configuration. Without schematics, I can
> only guess what's actually there. I can go through and note what each pin appears
> to be used for if you'd like.
Then please mention that it is based on vendor kernel vx.y for product
ABC. In such case it will be enough.
>
> >> + PIN_SLP(gpa0-4, PREV, NONE);
> >> + PIN_SLP(gpa0-5, PREV, NONE);
> >> + PIN_SLP(gpa0-6, PREV, NONE);
> >> + PIN_SLP(gpa0-7, PREV, NONE);
> >> +
> >> + PIN_SLP(gpa1-0, INPUT, DOWN);
> >> + PIN_SLP(gpa1-1, OUT0, NONE);
> >> + PIN_SLP(gpa1-2, INPUT, DOWN);
> >> + PIN_SLP(gpa1-3, OUT0, NONE);
> >> +
> >> + PIN_SLP(gpb-0, OUT0, NONE);
> >> + PIN_SLP(gpb-1, OUT1, NONE);
> >> + PIN_SLP(gpb-2, OUT0, NONE);
> >> + PIN_SLP(gpb-3, PREV, NONE);
> >> + PIN_SLP(gpb-4, INPUT, NONE);
> >> + PIN_SLP(gpb-5, PREV, NONE);
> >> + PIN_SLP(gpb-6, INPUT, DOWN);
> >> + PIN_SLP(gpb-7, OUT0, NONE);
> >> +
> >> + PIN_SLP(gpc0-0, OUT0, NONE);
> >> + PIN_SLP(gpc0-1, INPUT, DOWN);
> >> + PIN_SLP(gpc0-2, OUT0, NONE);
> >> + PIN_SLP(gpc0-3, INPUT, DOWN);
> >> + PIN_SLP(gpc0-4, OUT0, NONE);
> >> +
> >> + PIN_SLP(gpc1-0, INPUT, DOWN);
> >> + PIN_SLP(gpc1-1, INPUT, DOWN);
> >> + PIN_SLP(gpc1-2, INPUT, DOWN);
> >> + PIN_SLP(gpc1-3, INPUT, DOWN);
> >> + PIN_SLP(gpc1-4, INPUT, DOWN);
> >> +
> >> + PIN_SLP(gpd0-0, INPUT, DOWN);
> >> + PIN_SLP(gpd0-1, OUT0, NONE);
> >> + PIN_SLP(gpd0-2, INPUT, DOWN);
> >> + PIN_SLP(gpd0-3, INPUT, DOWN);
> >> +
> >> + PIN_SLP(gpd1-0, INPUT, NONE);
> >> + PIN_SLP(gpd1-1, INPUT, NONE);
> >> + PIN_SLP(gpd1-2, INPUT, DOWN);
> >> + PIN_SLP(gpd1-3, INPUT, DOWN);
> >> + PIN_SLP(gpd1-4, INPUT, DOWN);
> >> + PIN_SLP(gpd1-5, INPUT, DOWN);
> >> +
> >> + PIN_SLP(gpe0-0, INPUT, DOWN);
> >> + PIN_SLP(gpe0-1, INPUT, DOWN);
> >> + PIN_SLP(gpe0-2, INPUT, DOWN);
> >> + PIN_SLP(gpe0-3, INPUT, DOWN);
> >> + PIN_SLP(gpe0-4, INPUT, DOWN);
> >> + PIN_SLP(gpe0-5, INPUT, DOWN);
> >> + PIN_SLP(gpe0-6, INPUT, DOWN);
> >> + PIN_SLP(gpe0-7, INPUT, DOWN);
> >> +
> >> + PIN_SLP(gpe1-0, INPUT, DOWN);
> >> + PIN_SLP(gpe1-1, INPUT, DOWN);
> >> + PIN_SLP(gpe1-2, INPUT, DOWN);
> >> + PIN_SLP(gpe1-3, OUT0, NONE);
> >> + PIN_SLP(gpe1-4, INPUT, DOWN);
> >> +
> >> + PIN_SLP(gpf0-0, OUT0, NONE);
> >> + PIN_SLP(gpf0-1, OUT0, NONE);
> >> + PIN_SLP(gpf0-2, OUT0, NONE);
> >> + PIN_SLP(gpf0-3, OUT0, NONE);
> >> + PIN_SLP(gpf0-4, OUT0, NONE);
> >> + PIN_SLP(gpf0-5, OUT0, NONE);
> >> + PIN_SLP(gpf0-6, OUT0, NONE);
> >> + PIN_SLP(gpf0-7, OUT0, NONE);
> >> +
> >> + PIN_SLP(gpf1-0, OUT0, NONE);
> >> + PIN_SLP(gpf1-1, OUT0, NONE);
> >> + PIN_SLP(gpf1-2, OUT0, NONE);
> >> + PIN_SLP(gpf1-3, OUT0, NONE);
> >> + PIN_SLP(gpf1-4, OUT0, NONE);
> >> + PIN_SLP(gpf1-5, OUT0, NONE);
> >> + PIN_SLP(gpf1-6, OUT0, NONE);
> >> + PIN_SLP(gpf1-7, OUT0, NONE);
> >> +
> >> + PIN_SLP(gpf2-0, OUT0, NONE);
> >> + PIN_SLP(gpf2-1, OUT0, NONE);
> >> + PIN_SLP(gpf2-2, OUT0, NONE);
> >> + PIN_SLP(gpf2-3, OUT0, NONE);
> >> + PIN_SLP(gpf2-4, OUT0, NONE);
> >> + PIN_SLP(gpf2-5, OUT0, NONE);
> >> + PIN_SLP(gpf2-6, OUT0, NONE);
> >> + PIN_SLP(gpf2-7, OUT0, NONE);
> >> +
> >> + PIN_SLP(gpf3-0, OUT0, NONE);
> >> + PIN_SLP(gpf3-1, OUT0, NONE);
> >> + PIN_SLP(gpf3-2, OUT0, NONE);
> >> + PIN_SLP(gpf3-3, OUT0, NONE);
> >> + PIN_SLP(gpf3-4, PREV, NONE);
> >> + PIN_SLP(gpf3-5, INPUT, DOWN);
> >> +
> >> + PIN_SLP(gpg0-0, INPUT, DOWN);
> >> + PIN_SLP(gpg0-1, INPUT, DOWN);
> >> + PIN_SLP(gpg0-2, INPUT, NONE);
> >> + PIN_SLP(gpg0-3, INPUT, DOWN);
> >> + PIN_SLP(gpg0-4, INPUT, DOWN);
> >> + PIN_SLP(gpg0-5, INPUT, DOWN);
> >> + PIN_SLP(gpg0-6, INPUT, DOWN);
> >> +
> >> + PIN_SLP(gpg1-0, OUT0, NONE);
> >> + PIN_SLP(gpg1-1, OUT1, NONE);
> >> + PIN_SLP(gpg1-2, PREV, NONE);
> >> + PIN_SLP(gpg1-3, OUT1, NONE);
> >> + PIN_SLP(gpg1-4, OUT1, NONE);
> >> + PIN_SLP(gpg1-5, OUT1, NONE);
> >> + PIN_SLP(gpg1-6, OUT1, NONE);
> >> +
> >> + PIN_SLP(gpg2-0, OUT0, NONE);
> >> + PIN_SLP(gpg2-1, OUT0, NONE);
> >> + PIN_SLP(gpg2-2, INPUT, NONE);
> >> + PIN_SLP(gpg2-3, OUT0, NONE);
> >> + PIN_SLP(gpg2-4, OUT0, NONE);
> >> + PIN_SLP(gpg2-5, OUT0, NONE);
> >> + PIN_SLP(gpg2-6, OUT0, NONE);
> >> +
> >> + PIN_SLP(gpg3-0, PREV, UP);
> >> + PIN_SLP(gpg3-1, PREV, UP);
> >> + PIN_SLP(gpg3-2, INPUT, NONE);
> >> + PIN_SLP(gpg3-3, INPUT, DOWN);
> >> + PIN_SLP(gpg3-4, OUT0, NONE);
> >> + PIN_SLP(gpg3-5, OUT0, NONE);
> >> + PIN_SLP(gpg3-6, INPUT, DOWN);
> >> +
> >> + PIN_SLP(gpi-0, PREV, NONE);
> >
> > No such name. Did you mean gpgi?
> >
> >
>
> The node in s5pv210-pinctrl.dtsi is called "gpgi", but the i2s0_bus config
> in that file uses just "gpi". drivers/pinctrl/samsung/pinctrl-exynos-arm.c also
> notes it just as "gpi". I think the node should probably be renamed.
>
Good point. Will you send a fix for gpgi->gpi?
> >> + PIN_SLP(gpi-1, INPUT, DOWN);
> >> + PIN_SLP(gpi-2, PREV, NONE);
> >> + PIN_SLP(gpi-3, PREV, NONE);
> >> + PIN_SLP(gpi-4, PREV, NONE);
> >> + PIN_SLP(gpi-5, INPUT, DOWN);
> >> + PIN_SLP(gpi-6, INPUT, DOWN);
> >> +
> >> + PIN_SLP(gpj0-0, INPUT, NONE);
> >> + PIN_SLP(gpj0-1, INPUT, NONE);
> >> + PIN_SLP(gpj0-2, INPUT, NONE);
> >> + PIN_SLP(gpj0-3, INPUT, NONE);
> >> + PIN_SLP(gpj0-4, INPUT, NONE);
> >> + PIN_SLP(gpj0-5, INPUT, DOWN);
> >> + PIN_SLP(gpj0-6, OUT0, NONE);
> >> + PIN_SLP(gpj0-7, INPUT, NONE);
> >> +
> >> + PIN_SLP(gpj1-0, OUT1, NONE);
> >> + PIN_SLP(gpj1-1, OUT0, NONE);
> >> + PIN_SLP(gpj1-2, INPUT, DOWN);
> >> + PIN_SLP(gpj1-3, PREV, NONE);
> >> + PIN_SLP(gpj1-4, PREV, NONE);
> >> + PIN_SLP(gpj1-5, OUT0, NONE);
> >> +
> >> + PIN_SLP(gpj2-0, INPUT, DOWN);
> >> + PIN_SLP(gpj2-1, INPUT, DOWN);
> >> + PIN_SLP(gpj2-2, OUT0, NONE);
> >> + PIN_SLP(gpj2-3, INPUT, DOWN);
> >> + PIN_SLP(gpj2-4, INPUT, DOWN);
> >> + PIN_SLP(gpj2-5, PREV, NONE);
> >> + PIN_SLP(gpj2-6, PREV, NONE);
> >> + PIN_SLP(gpj2-7, INPUT, DOWN);
> >> +
> >> + PIN_SLP(gpj3-0, INPUT, NONE);
> >> + PIN_SLP(gpj3-1, INPUT, NONE);
> >> + PIN_SLP(gpj3-2, OUT0, NONE);
> >> + PIN_SLP(gpj3-3, INPUT, DOWN);
> >> + PIN_SLP(gpj3-4, INPUT, NONE);
> >> + PIN_SLP(gpj3-5, INPUT, NONE);
> >> + PIN_SLP(gpj3-6, INPUT, NONE);
> >> + PIN_SLP(gpj3-7, INPUT, NONE);
> >> +
> >> + PIN_SLP(gpj4-0, INPUT, NONE);
> >> + PIN_SLP(gpj4-1, INPUT, DOWN);
> >> + PIN_SLP(gpj4-2, PREV, NONE);
> >> + PIN_SLP(gpj4-3, INPUT, NONE);
> >> + PIN_SLP(gpj4-4, INPUT, DOWN);
> >> +
> >> + PIN_SLP(mp01-0, OUT1, NONE);
> >> + PIN_SLP(mp01-1, OUT0, NONE);
> >> + PIN_SLP(mp01-2, INPUT, DOWN);
> >> + PIN_SLP(mp01-3, INPUT, DOWN);
> >> + PIN_SLP(mp01-4, OUT1, NONE);
> >> + PIN_SLP(mp01-5, INPUT, DOWN);
> >> + PIN_SLP(mp01-6, INPUT, DOWN);
> >> + PIN_SLP(mp01-7, INPUT, DOWN);
> >> +
> >> + PIN_SLP(mp02-0, INPUT, DOWN);
> >> + PIN_SLP(mp02-1, INPUT, DOWN);
> >> + PIN_SLP(mp02-2, INPUT, NONE);
> >> + PIN_SLP(mp02-3, INPUT, DOWN);
> >> +
> >> + PIN_SLP(mp03-0, INPUT, DOWN);
> >> + PIN_SLP(mp03-1, INPUT, DOWN);
> >> + PIN_SLP(mp03-2, OUT1, NONE);
> >> + PIN_SLP(mp03-3, OUT0, NONE);
> >> + PIN_SLP(mp03-4, INPUT, NONE);
> >> + PIN_SLP(mp03-5, OUT0, NONE);
> >> + PIN_SLP(mp03-6, INPUT, DOWN);
> >> + PIN_SLP(mp03-7, INPUT, DOWN);
> >> +
> >> + PIN_SLP(mp04-0, INPUT, DOWN);
> >> + PIN_SLP(mp04-1, OUT0, NONE);
> >> + PIN_SLP(mp04-2, INPUT, DOWN);
> >> + PIN_SLP(mp04-3, OUT0, NONE);
> >> + PIN_SLP(mp04-4, INPUT, DOWN);
> >> + PIN_SLP(mp04-5, INPUT, DOWN);
> >> + PIN_SLP(mp04-6, OUT0, NONE);
> >> + PIN_SLP(mp04-7, INPUT, DOWN);
> >> +
> >> + PIN_SLP(mp05-0, INPUT, NONE);
> >> + PIN_SLP(mp05-1, INPUT, NONE);
> >> + PIN_SLP(mp05-2, INPUT, NONE);
> >> + PIN_SLP(mp05-3, INPUT, NONE);
> >> + PIN_SLP(mp05-4, INPUT, DOWN);
> >> + PIN_SLP(mp05-5, OUT0, NONE);
> >> + PIN_SLP(mp05-6, INPUT, DOWN);
> >> + PIN_SLP(mp05-7, PREV, NONE);
> >> +
> >> + PIN_SLP(mp06-0, INPUT, DOWN);
> >> + PIN_SLP(mp06-1, INPUT, DOWN);
> >> + PIN_SLP(mp06-2, INPUT, DOWN);
> >> + PIN_SLP(mp06-3, INPUT, DOWN);
> >> + PIN_SLP(mp06-4, INPUT, DOWN);
> >> + PIN_SLP(mp06-5, INPUT, DOWN);
> >> + PIN_SLP(mp06-6, INPUT, DOWN);
> >> + PIN_SLP(mp06-7, INPUT, DOWN);
> >> +
> >> + PIN_SLP(mp07-0, INPUT, DOWN);
> >> + PIN_SLP(mp07-1, INPUT, DOWN);
> >> + PIN_SLP(mp07-2, INPUT, DOWN);
> >> + PIN_SLP(mp07-3, INPUT, DOWN);
> >> + PIN_SLP(mp07-4, INPUT, DOWN);
> >> + PIN_SLP(mp07-5, INPUT, DOWN);
> >> + PIN_SLP(mp07-6, INPUT, DOWN);
> >> + PIN_SLP(mp07-7, INPUT, DOWN);
> >> + };
> >
> > What about gphX?
>
> The gphX pins are in the alive area and don't have power down configs, they retain their
> state over suspend. Therefore the samsung,pin-con-pdn and samsung,pin-pud-pdn properties
> have no effect (they're analogous to the gpxX pins in later Samsung SoCs).
Ah, good, thanks.
Best regards,
Krzysztof
next prev parent reply other threads:[~2020-05-01 13:10 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200426183604.28494-1-xc-racer2@live.ca>
2020-04-26 18:35 ` [PATCH 01/13] arm: dts: s5pv210: Add helper define for sleep gpio config Jonathan Bakker
2020-04-26 18:35 ` [PATCH 02/13] arm: dts: s5pv210: fascinate4g: Add sleep GPIO configuration Jonathan Bakker
2020-04-28 10:02 ` Krzysztof Kozlowski
2020-04-28 23:49 ` Jonathan Bakker
2020-05-01 13:10 ` Krzysztof Kozlowski [this message]
2020-04-26 18:35 ` [PATCH 03/13] arm: dts: s5pv210: galaxys: " Jonathan Bakker
2020-04-26 18:35 ` [PATCH 04/13] arm: dts: s5pv210: aries: Set keep-power-in-suspend for SDHCI1 Jonathan Bakker
2020-04-26 18:35 ` [PATCH 05/13] arm: dts: s5pv210: aries: Disable pulls on GPIO i2c adapters Jonathan Bakker
2020-04-26 18:35 ` [PATCH 06/13] arm: dts: s5pv210: aries: Add support for more devices Jonathan Bakker
2020-04-28 10:20 ` Krzysztof Kozlowski
2020-04-28 23:32 ` Jonathan Bakker
2020-05-01 13:31 ` Krzysztof Kozlowski
2020-05-01 19:43 ` Jonathan Bakker
2020-04-26 18:35 ` [PATCH 07/13] arm: dts: s5pv210: galaxys: Add si470x fmradio Jonathan Bakker
2020-04-26 18:35 ` [PATCH 08/13] arm: dts: s5pv210: aries: Disable pull for vibrator ena GPIO Jonathan Bakker
2020-04-26 18:36 ` [PATCH 09/13] arm: dts: s5pv210: Add an ADC node Jonathan Bakker
2020-04-28 10:26 ` Krzysztof Kozlowski
2020-04-28 22:27 ` Jonathan Bakker
2020-04-26 18:36 ` [PATCH 10/13] arm: dts: s5pv210: aries: Enable " Jonathan Bakker
2020-04-28 10:29 ` Krzysztof Kozlowski
2020-04-28 22:26 ` Jonathan Bakker
2020-04-26 18:36 ` [PATCH 11/13] arm: dts: s5pv210: Assign clocks to MMC devices Jonathan Bakker
2020-04-26 18:36 ` [PATCH 12/13] arm: dts: s5pv210: Correct FIMC definitions Jonathan Bakker
2020-04-28 10:32 ` Krzysztof Kozlowski
2020-04-28 22:31 ` Jonathan Bakker
2020-04-26 18:36 ` [PATCH 13/13] arm: dts: s5pv210: aries: Set MAX8998 GPIO pulls Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 00/18] S5PV210 and Aries DTS improvements Jonathan Bakker
2020-05-04 15:15 ` Krzysztof Kozlowski
[not found] ` <20200501235019.24022-1-xc-racer2@live.ca>
2020-05-01 23:50 ` [PATCH v2 01/18] ARM: dts: s5pv210: Add helper define for sleep gpio config Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 02/18] ARM: dts: s5pv210: Add sleep GPIO configuration for fascinate4g Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 03/18] ARM: dts: s5pv210: Add sleep GPIO configuration for galaxys Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 04/18] ARM: dts: s5pv210: Set keep-power-in-suspend for SDHCI1 on aries Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 05/18] ARM: dts: s5pv210: Disable pulls on GPIO i2c adapters for aries Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 06/18] ARM: dts: s5pv210: Add WM8994 support to aries boards Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 07/18] ARM: dts: s5pv210: Add FSA9480 support to Aries boards Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 08/18] ARM: dts: s5pv210: Add touchkey support to aries boards Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 09/18] ARM: dts: s5pv210: Add panel " Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 10/18] ARM: dts: s5pv210: Add remaining i2c-gpio adapters to aries Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 11/18] ARM: dts: s5pv210: Add si470x fmradio to galaxys Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 12/18] ARM: dts: s5pv210: Disable pull for vibrator ena GPIO on aries Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 13/18] ARM: dts: s5pv210: Add an ADC node Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 14/18] ARM: dts: s5pv210: Enable ADC on aries boards Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 15/18] ARM: dts: s5pv210: Assign clocks to MMC devices on aries Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 16/18] ARM: dts: s5pv210: Correct FIMC definitions Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 17/18] ARM: dts: s5pv210: Set MAX8998 GPIO pulls on aries Jonathan Bakker
2020-05-01 23:50 ` [PATCH v2 18/18] ARM: dts: s5pv210: Correct gpi gpio node name Jonathan Bakker
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=20200501131018.GA5154@kozik-lap \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=xc-racer2@live.ca \
/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;
as well as URLs for NNTP newsgroup(s).