From: Kishon Vijay Abraham I <kishon@ti.com> To: Tony Lindgren <tony@atomide.com> Cc: Ulf Hansson <ulf.hansson@linaro.org>, Rob Herring <robh+dt@kernel.org>, Adrian Hunter <adrian.hunter@intel.com>, <nsekhar@ti.com>, <linux-omap@vger.kernel.org>, <linux-mmc@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org> Subject: Re: [RFC PATCH 5/7] dt-bindings: ti-omap-hsmmc: Document new compatible for sdhci omap Date: Thu, 17 Aug 2017 11:13:47 +0530 [thread overview] Message-ID: <2cdf9bbe-b98b-8811-7587-268b7ef4ac66@ti.com> (raw) In-Reply-To: <20170809221222.GK3934@atomide.com> Hi Tony, On Thursday 10 August 2017 03:42 AM, Tony Lindgren wrote: > * Kishon Vijay Abraham I <kishon@ti.com> [170807 09:03]: >> Document the new compatible string "ti,dra7-sdhci" to be used for >> MMC controllers in DRA7 and DRA72 SoCs. > > I wonder if this should really be documented for sdhci > instead of ti-omap-hsmmc.txt? hmm.. yeah, having a separate binding document for sdhci would make the binding really clean and we also don't have to carry legacy binding code. But we'll be never able to remove omap-hsmmc driver then and end up maintaining 2 drivers for the same controller. > > I agree it's better to use sdhci compatible and keep the > hsmmc compatible around as the sdhci is still missing features > for runtime PM and context save and restore etc. yeah, once we have all the features in omap_hsmmc added in sdhci-omap, we can add the omap-hsmmc compatible to sdhci-omap and remove omap-hsmmc driver. Thanks Kishon
WARNING: multiple messages have this Message-ID (diff)
From: Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org> To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> Cc: Ulf Hansson <ulf.hansson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>, Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, Adrian Hunter <adrian.hunter-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>, nsekhar-l0cyMroinI0@public.gmane.org, linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Subject: Re: [RFC PATCH 5/7] dt-bindings: ti-omap-hsmmc: Document new compatible for sdhci omap Date: Thu, 17 Aug 2017 11:13:47 +0530 [thread overview] Message-ID: <2cdf9bbe-b98b-8811-7587-268b7ef4ac66@ti.com> (raw) In-Reply-To: <20170809221222.GK3934-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> Hi Tony, On Thursday 10 August 2017 03:42 AM, Tony Lindgren wrote: > * Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org> [170807 09:03]: >> Document the new compatible string "ti,dra7-sdhci" to be used for >> MMC controllers in DRA7 and DRA72 SoCs. > > I wonder if this should really be documented for sdhci > instead of ti-omap-hsmmc.txt? hmm.. yeah, having a separate binding document for sdhci would make the binding really clean and we also don't have to carry legacy binding code. But we'll be never able to remove omap-hsmmc driver then and end up maintaining 2 drivers for the same controller. > > I agree it's better to use sdhci compatible and keep the > hsmmc compatible around as the sdhci is still missing features > for runtime PM and context save and restore etc. yeah, once we have all the features in omap_hsmmc added in sdhci-omap, we can add the omap-hsmmc compatible to sdhci-omap and remove omap-hsmmc driver. Thanks Kishon -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-17 5:43 UTC|newest] Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-08-07 16:01 [RFC PATCH 0/7] mmc: Add OMAP SDHCI driver Kishon Vijay Abraham I 2017-08-07 16:01 ` Kishon Vijay Abraham I 2017-08-07 16:01 ` [RFC PATCH 1/7] mmc: sdhci: Add quirk to indicate no CRC stripping in MMC_RSP_136 Kishon Vijay Abraham I 2017-08-07 16:01 ` Kishon Vijay Abraham I 2017-08-15 7:27 ` Adrian Hunter 2017-08-17 5:20 ` Kishon Vijay Abraham I 2017-08-17 5:20 ` Kishon Vijay Abraham I 2017-08-17 6:31 ` Adrian Hunter 2017-08-17 7:40 ` Kishon Vijay Abraham I 2017-08-17 7:40 ` Kishon Vijay Abraham I 2017-08-07 16:01 ` [RFC PATCH 2/7] mmc: sdhci: Add quirk to indicate controller supports ADMA2 Kishon Vijay Abraham I 2017-08-07 16:01 ` Kishon Vijay Abraham I 2017-08-15 7:33 ` Adrian Hunter 2017-08-17 5:30 ` Kishon Vijay Abraham I 2017-08-17 5:30 ` Kishon Vijay Abraham I 2017-08-07 16:01 ` [RFC PATCH 3/7] mmc: sdhci: Add callback to set bus mode Kishon Vijay Abraham I 2017-08-07 16:01 ` Kishon Vijay Abraham I 2017-08-15 7:38 ` Adrian Hunter 2017-08-17 5:31 ` Kishon Vijay Abraham I 2017-08-17 5:31 ` Kishon Vijay Abraham I 2017-08-07 16:01 ` [RFC PATCH 4/7] mmc: sdhci: Add quirk to indicate broken POWER_CONTROL Kishon Vijay Abraham I 2017-08-07 16:01 ` Kishon Vijay Abraham I 2017-08-15 7:41 ` Adrian Hunter 2017-08-15 7:41 ` Adrian Hunter 2017-08-17 5:32 ` Kishon Vijay Abraham I 2017-08-17 5:32 ` Kishon Vijay Abraham I 2017-08-07 16:01 ` [RFC PATCH 5/7] dt-bindings: ti-omap-hsmmc: Document new compatible for sdhci omap Kishon Vijay Abraham I 2017-08-07 16:01 ` Kishon Vijay Abraham I 2017-08-09 22:12 ` Tony Lindgren 2017-08-09 22:12 ` Tony Lindgren 2017-08-17 5:43 ` Kishon Vijay Abraham I [this message] 2017-08-17 5:43 ` Kishon Vijay Abraham I 2017-08-17 16:05 ` Tony Lindgren 2017-08-07 16:01 ` [RFC PATCH 6/7] mmc: sdhci-omap: Add OMAP SDHCI driver Kishon Vijay Abraham I 2017-08-07 16:01 ` Kishon Vijay Abraham I 2017-08-15 8:22 ` Adrian Hunter 2017-08-15 8:22 ` Adrian Hunter 2017-08-17 5:57 ` Kishon Vijay Abraham I 2017-08-17 5:57 ` Kishon Vijay Abraham I 2017-08-17 6:43 ` Adrian Hunter 2017-08-17 7:59 ` Kishon Vijay Abraham I 2017-08-17 7:59 ` Kishon Vijay Abraham I 2017-08-17 8:23 ` Adrian Hunter 2017-08-20 11:03 ` Kishon Vijay Abraham I 2017-08-20 11:03 ` Kishon Vijay Abraham I 2017-08-07 16:01 ` [RFC PATCH 7/7] MAINTAINERS: Add TI OMAP SDHCI Maintainer Kishon Vijay Abraham I 2017-08-07 16:01 ` Kishon Vijay Abraham I
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=2cdf9bbe-b98b-8811-7587-268b7ef4ac66@ti.com \ --to=kishon@ti.com \ --cc=adrian.hunter@intel.com \ --cc=devicetree@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mmc@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=nsekhar@ti.com \ --cc=robh+dt@kernel.org \ --cc=tony@atomide.com \ --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: linkBe 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.