From: Tony Lindgren <tony@atomide.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Rob Herring <robh+dt@kernel.org>, Sekhar Nori <nsekhar@ti.com>,
Russell King <linux@armlinux.org.uk>,
linux-omap <linux-omap@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH v2 0/8] omap*: Fixes/Cleanups for MMC devicetree node
Date: Thu, 8 Jun 2017 01:46:20 -0700 [thread overview]
Message-ID: <20170608084619.GH3730@atomide.com> (raw)
In-Reply-To: <CAPDyKFrJh9qAz6q2-TH8rMshuMjDTkT5pHP==FUUH9KZEOehOQ@mail.gmail.com>
* Ulf Hansson <ulf.hansson@linaro.org> [170608 00:24]:
> If it helps, I can host a branch with the updates on the omap_hsmmc
> driver, such it can be pulled in from arm soc?
Great that works for me. Let's just make sure git bisect
keeps working.
> I guess you need that as, the DT changes relies on the new vqmmc
> binding. Or you thing it doesn't matter, because for the current
> changes that regulator is always an always on regulator?
Or maybe we can just add the new regulator, then do a
follow-up series to remove the old ones?
Regards,
Tony
next prev parent reply other threads:[~2017-06-08 8:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 9:37 [PATCH v2 0/8] omap*: Fixes/Cleanups for MMC devicetree node Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 1/8] ARM: dts: dra72-evm-common: Correct vmmc-supply for mmc2 Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 2/8] ARM: dts: dra72-evm: Add vqmmc supply to mmc1 Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 3/8] ARM: dts: dra72-evm-revc: " Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 4/8] ARM: dts: am57xx-beagle-x15-revb1: Fix supply name used for MMC1 IO lines Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 5/8] ARM: dts: dra7-evm: Correct the vmmc-supply for mmc2 Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 6/8] ARM: dts: dra7: Add "max-frequency" property to MMC dt nodes Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 7/8] ARM: OMAP2+: Add pdata-quirks for MMC/SD on DRA74x EVM Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 8/8] ARM: dts: omap*: Replace deprecated "vmmc_aux" with "vqmmc" Kishon Vijay Abraham I
2017-06-09 12:08 ` [PATCH v3] " Kishon Vijay Abraham I
2017-06-08 7:20 ` [PATCH v2 0/8] omap*: Fixes/Cleanups for MMC devicetree node Ulf Hansson
2017-06-08 8:46 ` Tony Lindgren [this message]
2017-06-09 12:21 ` Kishon Vijay Abraham I
2017-06-09 8:05 ` Kishon Vijay Abraham I
[not found] ` <4a4c4eb2-d865-25e6-cd53-a74d4f7b1f62-l0cyMroinI0@public.gmane.org>
2017-06-09 10:41 ` Ulf Hansson
2017-08-03 11:18 ` Kishon Vijay Abraham I
2017-08-07 6:48 ` Tony Lindgren
[not found] ` <20170807064813.GA5487-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-08-10 16:13 ` Tony Lindgren
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=20170608084619.GH3730@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.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 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).