<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>79daeb24 - mmc: core: Prepare to support SD UHS-II cards</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#79daeb24</link>
        <description>mmc: core: Prepare to support SD UHS-II cardsThe SD UHS-II interface was introduced to the SD spec v4.00 several yearsago. The interface is fundamentally different from an electrical and aprotocol point of view, comparing to the legacy SD interface.However, the legacy SD protocol is supported through a specific transportlayer (SD-TRAN) defined in the UHS-II addendum of the spec. This allows theSD card to be managed in a very similar way as a legacy SD card, hence alot of code can be re-used to support these new types of cards through themmc subsystem.Moreover, an SD card that supports the UHS-II interface shall also bebackwards compatible with the legacy SD interface, which allows a UHS-IIcard to be inserted into a legacy slot. As a matter of fact, this isalready supported by mmc subsystem as of today.To prepare to add support for UHS-II, this change puts the basic foundationin the mmc core in place, allowing it to be more easily reviewed beforesubsequent changes implements the actual support.Basically, the approach here adds a new UHS-II bus_ops type and adds aseparate initialization path for the UHS-II card. The intent is to avoid usfrom sprinkling the legacy initialization path, but also to simplifyimplementation of the UHS-II specific bits.At this point, there is only one new host ops added to manage the variousios settings needed for UHS-II. Additional host ops that are needed, arebeing added from subsequent changes.Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;Link: https://lore.kernel.org/r/20240913102836.6144-3-victorshihgli@gmail.com

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Fri, 13 Sep 2024 10:28:16 +0000</pubDate>
        <dc:creator>Ulf Hansson &lt;ulf.hansson@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>93f1c150 - mmc: core: Add basic support for inline encryption</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#93f1c150</link>
        <description>mmc: core: Add basic support for inline encryptionIn preparation for adding CQHCI crypto engine (inline encryption)support, add the code required to make mmc_core and mmc_block aware ofinline encryption.  Specifically:- Add a capability flag MMC_CAP2_CRYPTO to struct mmc_host.  Drivers  will set this if the host and driver support inline encryption.- Embed a blk_keyslot_manager in struct mmc_host.  Drivers will  initialize this (as a device-managed resource) if the host and driver  support inline encryption.  mmc_block registers this keyslot manager  with the request_queue of any MMC card attached to the host.- Make mmc_block copy the crypto keyslot and crypto data unit number  from struct request to struct mmc_request, so that drivers will have  access to them.- If the MMC host is reset, reprogram all the keyslots to ensure that  the software state stays in sync with the hardware state.Co-developed-by: Satya Tangirala &lt;satyat@google.com&gt;Signed-off-by: Satya Tangirala &lt;satyat@google.com&gt;Acked-by: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Reviewed-by: Satya Tangirala &lt;satyat@google.com&gt;Reviewed-and-tested-by: Peng Zhou &lt;peng.zhou@mediatek.com&gt;Signed-off-by: Eric Biggers &lt;ebiggers@google.com&gt;Link: https://lore.kernel.org/r/20210126001456.382989-2-ebiggers@kernel.orgSigned-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Tue, 26 Jan 2021 00:14:48 +0000</pubDate>
        <dc:creator>Eric Biggers &lt;ebiggers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>de13d5a4 - mmc: core: Move regulator helpers to separate file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#de13d5a4</link>
        <description>mmc: core: Move regulator helpers to separate fileThe mmc regulator helper functions, are placed in the extensive core.cfile.  In a step towards trying to create a better structure of files,avoiding too many lines of code per file, let&apos;s move these helpers to a newfile, regulator.c.Moreover, this within this context it makes sense to also drop the exportof mmc_vddrange_to_ocrmask(), but instead let&apos;s make it internal to the mmccore.Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Wed, 13 Feb 2019 17:10:37 +0000</pubDate>
        <dc:creator>Ulf Hansson &lt;ulf.hansson@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#b2441318</link>
        <description>License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the &apos;GPL-2.0&apos;SPDX license identifier.  The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode &amp; Windriver) producing SPDXtag:value files created by Philippe Ombredanne.  Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed.  Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;t find any license traces, file was   considered to have no license information in it, and the top level   COPYING file license applied.   For non */uapi/* files that summary was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0                                              11139   and resulted in the first patch in this series.   If that file was a */uapi/* path one, it was &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  Results of that was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0 WITH Linux-syscall-note                        930   and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one   of the */uapi/* ones, it was denoted with the Linux-syscall-note if   any GPL family license was found in the file or had no licensing in   it (per prior point).  Results summary:   SPDX license identifier                            # files   ---------------------------------------------------|------   GPL-2.0 WITH Linux-syscall-note                       270   GPL-2.0+ WITH Linux-syscall-note                      169   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17   LGPL-2.1+ WITH Linux-syscall-note                      15   GPL-1.0+ WITH Linux-syscall-note                       14   ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5   LGPL-2.0+ WITH Linux-syscall-note                       4   LGPL-2.1 WITH Linux-syscall-note                        3   ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3   ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1   and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became   the concluded license(s). - when there was disagreement between the two scanners (one detected a   license but the other didn&apos;t, or they both detected different   licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file   resulted in a clear resolution of the license that should apply (and   which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was   confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier,   the file was flagged for further research and to be revisited later   in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights.  TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected   license ids and scores - reviewing anything where there was a license detected (about 500+   files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license   was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied   SPDX license was correctThis produced a worksheet with 20 files needing minor correction.  Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg.  Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected.  This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.)  Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>28fc64af - mmc: core: change quirks.c to be a header file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#28fc64af</link>
        <description>mmc: core: change quirks.c to be a header fileRename quirks.c to quirks.h, and include it forindividual C files which need it.Signed-off-by: Shawn Lin &lt;shawn.lin@rock-chips.com&gt;Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Wed, 15 Feb 2017 08:35:28 +0000</pubDate>
        <dc:creator>Shawn Lin &lt;shawn.lin@rock-chips.com&gt;</dc:creator>
    </item>
<item>
        <title>de19b4c9 - mmc: pwrseq: add support for Marvell SD8787 chip</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#de19b4c9</link>
        <description>mmc: pwrseq: add support for Marvell SD8787 chipAllow power sequencing for the Marvell SD8787 Wifi/BT chip.This can be abstracted to other chipsets if needed in the future.Cc: Tony Lindgren &lt;tony@atomide.com&gt;Cc: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;Signed-off-by: Matt Ranostay &lt;matt@ranostay.consulting&gt;Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Tue, 24 Jan 2017 03:08:30 +0000</pubDate>
        <dc:creator>Matt Ranostay &lt;matt@ranostay.consulting&gt;</dc:creator>
    </item>
<item>
        <title>f397c8d8 - mmc: block: Move files to core</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#f397c8d8</link>
        <description>mmc: block: Move files to coreOnce upon a time it made sense to keep the mmc block device driver and itsrelated code, in its own directory called card. Over time, more an morefunctions/structures have become shared through generic mmc header files,between the core and the card directory. In other words, the relationshipbetween them has become closer.By sharing functions/structures via generic header files, it becomes easyfor outside users to abuse them. In a way to avoid that from happen, let&apos;smove the files from card directory into the core directory, as it enablesus to move definitions of functions/structures into mmc core specificheader files.Note, this is only the first step in providing a cleaner mmc interface foroutside users. Following changes will do the actual cleanup, as that is notpart of this change.Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;Reviewed-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Thu, 08 Dec 2016 10:23:49 +0000</pubDate>
        <dc:creator>Ulf Hansson &lt;ulf.hansson@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>d97a1e5d - mmc: pwrseq: convert to proper platform device</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#d97a1e5d</link>
        <description>mmc: pwrseq: convert to proper platform devicesimple-pwrseq and emmc-pwrseq drivers rely on platform_devicestructure from of_find_device_by_node(), this works mostly. But, as thereis no driver associated with this devices, cases like default/init pinctrlsetup would never be performed by pwrseq. This becomes problem when thegpios used in pwrseq require pinctrl setup.Currently most of the common pinctrl setup is done indrivers/base/pinctrl.c by pinctrl_bind_pins().There are two ways to solve this issue on either convert pwrseq driversto a proper platform drivers or copy the exact code frompcintrl_bind_pins(). I prefer converting pwrseq to proper drivers so thatother cases like setting up clks/parents from dt would also be possible.Signed-off-by: Srinivas Kandagatla &lt;srinivas.kandagatla@linaro.org&gt;Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Thu, 14 Apr 2016 13:02:16 +0000</pubDate>
        <dc:creator>Srinivas Kandagatla &lt;srinivas.kandagatla@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>726b6324 - mmc: pwrseq: add driver for emmc hardware reset</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#726b6324</link>
        <description>mmc: pwrseq: add driver for emmc hardware resetThis patch provides a simple mmc-pwrseq-emmc driver, which controlssingle gpio line. It perform standard eMMC hw reset procedure, asdescibed by Jedec 4.4 specification. This procedure is performed justafter MMC core enabled power to the given mmc host (to fix possibleissues if bootloader has left eMMC card in initialized or unknownstate), and before performing complete system reboot (also in case ofemergency reboot call). The latter is needed on boards, which doesn&apos;thave hardware reset logic connected to emmc card and (limited or broken)ROM bootloaders are unable to read second stage from the emmc card ifthe card is left in unknown or already initialized state.Signed-off-by: Marek Szyprowski &lt;m.szyprowski@samsung.com&gt;Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Tue, 03 Feb 2015 13:07:53 +0000</pubDate>
        <dc:creator>Marek Szyprowski &lt;m.szyprowski@samsung.com&gt;</dc:creator>
    </item>
<item>
        <title>8c96f89c - mmc: pwrseq: Initial support for the simple MMC power sequence provider</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#8c96f89c</link>
        <description>mmc: pwrseq: Initial support for the simple MMC power sequence providerTo add the core part for the MMC power sequence, let&apos;s start by addinginitial support for the simple MMC power sequence provider.In this initial step, the MMC power sequence node are fetched and thecompatible string for the simple MMC power sequence provider areverified.At this point we don&apos;t parse the node for any properties, but insteadthat will be handled from following patches. Since there are noproperties supported yet, let&apos;s just implement the -&gt;alloc() and the-&gt;free() callbacks.Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;Tested-by: Javier Martinez Canillas &lt;javier.martinez@collabora.co.uk&gt;Reviewed-by: Javier Martinez Canillas &lt;javier.martinez@collabora.co.uk&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Fri, 05 Dec 2014 13:36:58 +0000</pubDate>
        <dc:creator>Ulf Hansson &lt;ulf.hansson@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>3aa8793f - mmc: core: Initial support for MMC power sequences</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#3aa8793f</link>
        <description>mmc: core: Initial support for MMC power sequencesSystem on chip designs may specify a specific MMC power sequence. Tosuccessfully detect an (e)MMC/SD/SDIO card, that power sequence mustbe followed while initializing the card.To be able to handle these SOC specific power sequences, let&apos;s add aMMC power sequence interface. It provides the following functions tohelp the mmc core to deal with these power sequences.mmc_pwrseq_alloc() - Invoked from mmc_of_parse(), to initialize data.mmc_pwrseq_pre_power_on()- Invoked in the beginning of mmc_power_up().mmc_pwrseq_post_power_on()- Invoked at the end in mmc_power_up().mmc_pwrseq_power_off()- Invoked from mmc_power_off().mmc_pwrseq_free() - Invoked from mmc_free_host(), to free data.Each MMC power sequence provider will be responsible to implement a setof callbacks. These callbacks mirrors the functions above.This patch adds the skeleton, following patches will extend the core ofthe MMC power sequence and add support for a specific simple MMC powersequence.Do note, since the mmc_pwrseq_alloc() is invoked from mmc_of_parse(),host drivers needs to make use of this API to enable the support forMMC power sequences. Moreover the MMC power sequence support depends onCONFIG_OF.Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;Tested-by: Javier Martinez Canillas &lt;javier.martinez@collabora.co.uk&gt;Reviewed-by: Javier Martinez Canillas &lt;javier.martinez@collabora.co.uk&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Fri, 28 Nov 2014 13:38:36 +0000</pubDate>
        <dc:creator>Ulf Hansson &lt;ulf.hansson@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>fd0ea65d - mmc: extend and rename cd-gpio helpers to handle more slot GPIO functions</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#fd0ea65d</link>
        <description>mmc: extend and rename cd-gpio helpers to handle more slot GPIO functionsGPIOs can be used in MMC/SD-card slots not only for hotplug detection, butalso to implement the write-protection pin. Rename cd-gpio helpers toslot-gpio to make addition of further slot GPIO functions possible.Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Mon, 30 Apr 2012 21:31:57 +0000</pubDate>
        <dc:creator>Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;</dc:creator>
    </item>
<item>
        <title>349ab524 - mmc: add a generic GPIO card-detect helper</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#349ab524</link>
        <description>mmc: add a generic GPIO card-detect helperThis patch adds a primitive helper to support card hotplug detection onplatforms, where a GPIO, capable of producing interrupts, is used fordetection of card-insertion and -removal events.Signed-off-by: Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Sun, 25 Dec 2011 20:36:02 +0000</pubDate>
        <dc:creator>Guennadi Liakhovetski &lt;g.liakhovetski@gmx.de&gt;</dc:creator>
    </item>
<item>
        <title>57f0adc7 - mmc: add per device quirk placeholder</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#57f0adc7</link>
        <description>mmc: add per device quirk placeholderSome cards have quirks valid for every platforms using currentplatform quirk hooks leads to a lot of code and debug duplication.So we inspire a bit from what exists in PCI subsystem and do our ownper vendorid/deviceid quirk.  We still drop the complexity of the pciquirk system (with special section tables, and so on).That can be added later if needed.Signed-off-by: Pierre Tardy &lt;pierre.tardy@intel.com&gt;Acked-by: Linus Walleij &lt;linus.walleij@stericsson.com&gt;Acked-by: Ohad Ben-Cohen &lt;ohad@wizery.com&gt;Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Sun, 06 Feb 2011 18:03:46 +0000</pubDate>
        <dc:creator>Pierre Tardy &lt;pierre.tardy@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>d3c502b8 - mmc: Makefile: Fix EXTRA_CFLAGS assignment</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#d3c502b8</link>
        <description>mmc: Makefile: Fix EXTRA_CFLAGS assignmentThe EXTRA_CFLAGS assignment in mmc/Makefile was not accomplishinganything because this flag only has effect on sources at the same levelas the makefile (i.e., per directory). Since card/, core/, and host/rely on MMC_DEBUG, the subdir-ccflags-y variant seems to be theappropriate choice.Signed-off-by: matt mooney &lt;mfm@muteddisk.com&gt;Signed-off-by: Chris Ball &lt;cjb@laptop.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Fri, 24 Sep 2010 19:17:24 +0000</pubDate>
        <dc:creator>matt mooney &lt;mfm@muteddisk.com&gt;</dc:creator>
    </item>
<item>
        <title>6edd8ee6 - mmc: Export internal host state through debugfs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#6edd8ee6</link>
        <description>mmc: Export internal host state through debugfsWhen CONFIG_DEBUG_FS is set, create a few files under /sys/kernel/debugcontaining information about an mmc host&apos;s internal state. Currently,just a single file is created, &quot;ios&quot;, which contains information aboutthe current operating parameters for the bus (clock speed, bus width,etc.)Host drivers can add additional files and directories under the host&apos;sroot directory by passing the debugfs_root field in struct mmc_host asthe &apos;parent&apos; parameter to debugfs_create_*.Signed-off-by: Haavard Skinnemoen &lt;haavard.skinnemoen@atmel.com&gt;Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Thu, 24 Jul 2008 12:18:57 +0000</pubDate>
        <dc:creator>Haavard Skinnemoen &lt;haavard.skinnemoen@atmel.com&gt;</dc:creator>
    </item>
<item>
        <title>51ec92e2 - mmc: use sysfs groups to handle conditional attributes</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#51ec92e2</link>
        <description>mmc: use sysfs groups to handle conditional attributesSuppressing uevents turned out to be a bad idea as it screws up theorder of events, making user space very confused. Change the system touse sysfs groups instead.This is a regression that, for some odd reason, has gone unnoticed forsome time. It confuses hal so that the block devices (which have themmc device as a parent) are not registered. End result being thatdesktop magic when cards are inserted won&apos;t work.Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Fri, 21 Mar 2008 22:54:50 +0000</pubDate>
        <dc:creator>Pierre Ossman &lt;drzeus-list@drzeus.cx&gt;</dc:creator>
    </item>
<item>
        <title>d1496c39 - sdio: core support for SDIO function interrupt</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#d1496c39</link>
        <description>sdio: core support for SDIO function interruptSigned-off-by: Nicolas Pitre &lt;npitre@mvista.com&gt;Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Sat, 30 Jun 2007 14:29:41 +0000</pubDate>
        <dc:creator>Nicolas Pitre &lt;nico@cam.org&gt;</dc:creator>
    </item>
<item>
        <title>b7261261 - sdio: initial CIS parsing code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#b7261261</link>
        <description>sdio: initial CIS parsing codeSigned-off-by: Nicolas Pitre &lt;npitre@mvista.com&gt;Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Sat, 16 Jun 2007 06:04:16 +0000</pubDate>
        <dc:creator>Nicolas Pitre &lt;nico@cam.org&gt;</dc:creator>
    </item>
<item>
        <title>46f555f2 - mmc: add basic SDIO I/O operations</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/mmc/core/Makefile#46f555f2</link>
        <description>mmc: add basic SDIO I/O operationsAdd command wrappers that simplify register access from SDIOfunction drivers.Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;

            List of files:
            /linux-6.15/drivers/mmc/core/Makefile</description>
        <pubDate>Sun, 27 May 2007 10:57:15 +0000</pubDate>
        <dc:creator>Pierre Ossman &lt;drzeus@drzeus.cx&gt;</dc:creator>
    </item>
</channel>
</rss>
