http://permalink.gmane.org/gmane.linux.documentation hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.linux.documentation/11249 <pre>Hi, Rohit Thanks for the patch! On 05/21/2013 09:32 PM, Rohit Vaswani wrote: &lt;cut&gt; IMO here you should use irq_find_mapping() and create irq mapping once in .probe. See below comment. &lt;cut&gt; Are you sure that we want to WARN if no memory? I'd return an error and fail the probe if the driver can't works without interrupts. Adding irqdomain might fail, could you check the return value. And if irqdomain init fail do we need to set up chained handler for summary_irq at all? I'd call irq_create_mapping() instead. This way the mapping will be created once in .probe and use irq_find_mapping() in gpio_to_irq. These three function calls are not needed anymore because irq_create_mapping() will call internally irqdomain .map operation. The .map already calls these three functions. - Stan -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo&lt; at &gt;vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Stanimir Varbanov 2013-05-22T09:36:00 http://permalink.gmane.org/gmane.linux.documentation/11248 <pre>...... Oh, yes. We don't need this. Will remove the following in the next version. Thanks. :) -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo&lt; at &gt;vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Tang Chen 2013-05-22T09:24:37 http://permalink.gmane.org/gmane.linux.documentation/11246 <pre>Updated broken "The Perfect Patch" link in HOWTO to a copy at kerneltrap.org. Signed-off-by: Ben Minerds &lt;puzzleduck&lt; at &gt;gmail.com&gt; --- Documentation/HOWTO | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/HOWTO b/Documentation/HOWTO index a9f288f..27faae3 100644 --- a/Documentation/HOWTO +++ b/Documentation/HOWTO &lt; at &gt;&lt; at &gt; -112,7 +112,7 &lt; at &gt;&lt; at &gt; required reading: Other excellent descriptions of how to create patches properly are: "The Perfect Patch" -http://userweb.kernel.org/~akpm/stuff/tpp.txt +http://kerneltrap.org/node/3737 "Linux kernel patch submission format" http://linux.yyz.us/patch-format.html </pre> Ben Minerds 2013-05-22T08:42:07 http://permalink.gmane.org/gmane.linux.documentation/11245 <pre>From: KV Sujith &lt;sujithkv&lt; at &gt;ti.com&gt; - Add of_device_id for Davinci GPIO driver. - Add function to populate data from DT. - Modify the probe to read from DT if DT match is found. - Add DT binding documentation for Davinci GPIO properties in a new file gpio-davinci.txt located at Documentation/devicetree/bindings/gpio/. Cc: Grant Likely &lt;grant.likely&lt; at &gt;secretlab.ca&gt; Cc: Rob Herring &lt;rob.herring&lt; at &gt;calxeda.com&gt; Cc: Rob Landley &lt;rob&lt; at &gt;landley.net&gt; Cc: devicetree-discuss&lt; at &gt;lists.ozlabs.org Cc: linux-doc&lt; at &gt;vger.kernel.org Signed-off-by: KV Sujith &lt;sujithkv&lt; at &gt;ti.com&gt; Signed-off-by: Philip Avinash &lt;avinashphilip&lt; at &gt;ti.com&gt; --- .../devicetree/bindings/gpio/gpio-davinci.txt | 26 +++++++++ drivers/gpio/gpio-davinci.c | 57 ++++++++++++++++++-- 2 files changed, 80 insertions(+), 3 deletions(-) create mode 100644 Documentation/devicetree/bindings/gpio/gpio-davinci.txt diff --git a/Documentation/devicetree/bindings/gpio/gpio-davinci.txt b/Documentation/devicetree/bindings/gpio/gpio-davinci.txt new fi</pre> Philip Avinash 2013-05-22T07:10:32 http://permalink.gmane.org/gmane.linux.documentation/11244 <pre>Hi, On Tuesday 07 May 2013 10:51 AM, Kishon Vijay Abraham I wrote: I think this is to do with disabling interrupts while reporting the VBUS state. (linkstat is updated in irq handler). So this should be fine I guess? Thanks Kishon -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo&lt; at &gt;vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Kishon Vijay Abraham I 2013-05-22T06:23:21 http://permalink.gmane.org/gmane.linux.documentation/11242 <pre>Hi Vasilis, Maybe the following two problems are the cause of the reboot panic problem in qemu you mentioned. On 04/30/2013 05:21 PM, Tang Chen wrote: ...... Need to call find_usable_zone_for_movable() here before goto out. Here, it should be PFN_DOWN(reserved-&gt;regions[i].base). Thanks. :) -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo&lt; at &gt;vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Tang Chen 2013-05-22T04:43:14 http://permalink.gmane.org/gmane.linux.documentation/11241 <pre> This doesn't actually rely on ARCH_MSM anymore so I think we can drop that dependency. Looks like intstat is used uninitialized now? Fail probe if the property isn't there? devm_ioremap_resource() returns an ERR_PTR on failure, not NULL. Also, it already prints messages on errors so you can drop all the prints around this. Just do res = platform_get_resource(&amp;pdev-&gt;dev, IORESOURCE_MEM, 0); msm_tlmm_base = devm_ioremap_resource(pdev-&gt;dev, res); if (IS_ERR(msm_tlmm_base)) return ERR_PTR(msm_tlmm_base); You could use module_platform_driver here now too. </pre> Stephen Boyd 2013-05-21T21:06:27 http://permalink.gmane.org/gmane.linux.documentation/11238 <pre> The allocation, it can be part of the sdhci_pltfm_host data. Sorry for being unclear. I mean you can just use &amp;sdhci_pltfm_data_kona in the probe function, since the data is constant anyway, no need to have a local variable for pulling this out of the device id. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo&lt; at &gt;vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Arnd Bergmann 2013-05-21T18:23:03 http://permalink.gmane.org/gmane.linux.documentation/11237 <pre>function-mask property is a mask for a pin at each pin configure offset in a pincontrol register. Signed-off-by: Manjunathappa, Prakash &lt;prakash.pm&lt; at &gt;ti.com&gt; --- arch/arm/boot/dts/da850.dtsi | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi index 4d43046..9bec36c 100644 --- a/arch/arm/boot/dts/da850.dtsi +++ b/arch/arm/boot/dts/da850.dtsi &lt; at &gt;&lt; at &gt; -37,7 +37,7 &lt; at &gt;&lt; at &gt; #size-cells = &lt;0&gt;; pinctrl-single,bit-per-mux; pinctrl-single,register-width = &lt;32&gt;; -pinctrl-single,function-mask = &lt;0xffffffff&gt;; +pinctrl-single,function-mask = &lt;0xf&gt;; status = "disabled"; nand_cs3_pins: pinmux_nand_pins { </pre> Manjunathappa, Prakash 2013-05-21T14:08:02 http://permalink.gmane.org/gmane.linux.documentation/11232 <pre>Add device tree based support for TI's tps6507x touchscreen. Tested on da850-evm. Signed-off-by: Vishwanathrao Badarkhe, Manish &lt;manishv.b&lt; at &gt;ti.com&gt; --- Changes since V2: - Removed unnecessary code. - Updated Documentation to provide proper names of devicetree properties. Changes since V1: - Updated documentation to specify tps6507x as multifunctional device. - return proper error value in absence of platform and DT data for touchscreen. - Updated commit message. :100755 100755 8fffa3c... 65ee2cd... MDocumentation/devicetree/bindings/mfd/tps6507x.txt :100644 100644 65e0f9a... 89232ee... Mdrivers/input/touchscreen/tps6507x-ts.c Documentation/devicetree/bindings/mfd/tps6507x.txt | 28 ++++++- drivers/input/touchscreen/tps6507x-ts.c | 98 ++++++++++++++------ 2 files changed, 95 insertions(+), 31 deletions(-) diff --git a/Documentation/devicetree/bindings/mfd/tps6507x.txt b/Documentation/devicetree/bindings/mfd/tps6507x.txt index 8fffa3c..65ee2cd 100755 --- a/Documentation/dev</pre> Vishwanathrao Badarkhe, Manish 2013-05-21T08:54:17 http://permalink.gmane.org/gmane.linux.documentation/11231 <pre>Add tps6507x touchscreen DT node to da850-evm. Touchscreen DT data is added as per da850 board file. Tested on da850-evm. Signed-off-by: Vishwanathrao Badarkhe, Manish &lt;manishv.b&lt; at &gt;ti.com&gt; --- Changes since V2: - Updated names of devicetree properties. Changes since V1: - Updated commit message. :100644 100644 c914357... 1ca1691... March/arm/boot/dts/da850-evm.dts arch/arm/boot/dts/da850-evm.dts | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/arch/arm/boot/dts/da850-evm.dts b/arch/arm/boot/dts/da850-evm.dts index c914357..1ca1691 100644 --- a/arch/arm/boot/dts/da850-evm.dts +++ b/arch/arm/boot/dts/da850-evm.dts &lt; at &gt;&lt; at &gt; -155,4 +155,13 &lt; at &gt;&lt; at &gt; regulator-boot-on; }; }; + +tsc { +ti,poll-period = &lt;30&gt;; +ti,min-pressure = &lt;0x30&gt;; +ti,vref = &lt;0&gt;; +ti,vendor = &lt;0&gt;; +ti,product = &lt;65070&gt;; +ti,version = &lt;0x100&gt;; +}; }; </pre> Vishwanathrao Badarkhe, Manish 2013-05-21T08:54:18 http://permalink.gmane.org/gmane.linux.documentation/11230 <pre>Patch set adds DT support for tps6507x based touchscreen. Also, add DT data for tps6507x touchscreen in da850-evm by providing touchscreen node inside tps6507x mfd device. This patch series applies on top of linux-next tree and depends on [1]. [1]tps6507x-ts: update to devm_* API https://patchwork.kernel.org/patch/2324441/ Tested on da850-evm board. Changes since V2: - Updated tps6507x documentation. - Removed unnecessary code. Changes since V1: - Updated tps6507x documentation. - Updated commit message. - return proper error value in absence platform and DT data for touchscreen. Vishwanathrao Badarkhe, Manish (2): tps6507x-ts: Add DT support ARM: davinci: da850: add tps6507x touchscreen DT data Documentation/devicetree/bindings/mfd/tps6507x.txt | 28 ++++++- arch/arm/boot/dts/da850-evm.dts | 9 ++ drivers/input/touchscreen/tps6507x-ts.c | 98 ++++++++++++++------ 3 files changed, 104 insertions(+), 31 deletions(-) </pre> Vishwanathrao Badarkhe, Manish 2013-05-21T08:54:16 http://permalink.gmane.org/gmane.linux.documentation/11227 <pre> Yes, mdio is using GbE0Err interrupt and that is 14 on IRQ HIGH CAUSE. I was misled by 11 on IRQ LOW CAUSE. Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo&lt; at &gt;vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Sebastian Hesselbarth 2013-05-20T21:38:00 http://permalink.gmane.org/gmane.linux.documentation/11225 <pre>Hi Sebastian, On Mon, May 06, 2013 at 05:33:39PM +0200, Sebastian Hesselbarth wrote: ... Shouldn't this be 46? - Simon -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo&lt; at &gt;vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Simon Baatz 2013-05-20T21:27:08 http://permalink.gmane.org/gmane.linux.documentation/11223 <pre> (...) Note: I have come to realize that there is apparently almost zero review on the devicetree-discuss list, is there anyone in the world reviewing new device tree bindings for generality, or is it all up to Linux subsystem maintainers like myself to take care of this? This vendor prefix does not exist in Documentation/devicetree/bindings/vendor-prefixes.txt so atleast add it. I don't see the point in abbreviating "altera" to "altr" to save two letters, use the full name of the company! So why do you add it? Because all other GPIO controllers use it? Or because you will use it for something later? Is this how other GPIO controllers do it? I don't get it, but I guess reading the code will. I suspect this needs editing since DT bindings shall be *reusable* without having to read the code to understand them. Explain exactly what you mean when you say it is "used to detect internally how the trigger is handled". Used how? Handled how? Internally to what? Delete this. We do not put Linux-specific </pre> Linus Walleij 2013-05-20T18:02:30 http://permalink.gmane.org/gmane.linux.documentation/11222 <pre>Hi Arnd, Thankyou for the comments. On 17/05/13 15:36, Arnd Bergmann wrote: yes I agree. Some of the drivers like Ethernet already provide higher level interfaces via callbacks. We did implement such a callbacks per each SOC in non-DT case, and ended up having code duplicated for each SOC. On the other hand using device trees to describe the HW configuration(sysconfs) made more sense and got rid of SOC specific callbacks. In pinctrl bindings case, I think we could do better job by replacing the existing bindings of sysconfs for a group of banks with just two integer offsets. This would mean that, we can still use the a common driver across the SOCs. And w.r.t to reset, we are planning on using sysconf based reset-controller API sitting underneath the reset-controller subsystem. Passing the information from device trees would be much clear and flexible than adding new driver per/SOC. I forget to mention a important point here, the protection is at bit level for the sysconfs. Some of sysconfs have bits</pre> Srinivas KANDAGATLA 2013-05-20T12:48:59 http://permalink.gmane.org/gmane.linux.documentation/11221 <pre> Now I'm ever more confused ... we already have this :-) It's not even pinctrl-simple-centric it is completely generic. The code is in drivers/gpio/gpiolib-of.c. It was written by Shiraz Hashin and Haojian Zhuang. At the time I augmented the core code quite a bit to make a good fit. This is from: Documentation/devicetree/bindings/gpio/gpio.txt 2.1) gpio-controller and pinctrl subsystem ------------------------------------------ gpio-controller on a SOC might be tightly coupled with the pinctrl subsystem, in the sense that the pins can be used by other functions together with optional gpio feature. While the pin allocation is totally managed by the pin ctrl subsystem, gpio (under gpiolib) is still maintained by gpio drivers. It may happen that different pin ranges in a SoC is managed by different gpio drivers. This makes it logical to let gpio drivers announce their pin ranges to the pin ctrl subsystem and call 'pinctrl_request_gpio' in order to request the corresponding pin before any gpio usage. Fo</pre> Linus Walleij 2013-05-20T08:10:33 http://permalink.gmane.org/gmane.linux.documentation/11220 <pre>On Wed, May 15, 2013 at 11:41 AM, Christian Ruppert &lt;christian.ruppert&lt; at &gt;abilis.com&gt; wrote: No, sorry that the code is strange... The variable is named "gpio" because that is the numbering used in the data sheet. Think of "gpio" as "the number in the data sheet". Then offset is calculated to start from 0. No that is already done by the GPIO ranges. I thought this discussion was about shuffleing around/translating the numberings of the pins themselves. Yep. It has abx500_pinrange to associate some information with certain ranges of pins. It has nothing to do with GPIO ranges if you look closer at it. The offset by one is achieved not by this range type, but by hard-coding a subtraction with one at every entry point, as illustrated. This is orthogonal to all range concepts. This is getting very confused so I can't follow it. For the GPIO and pin control subsystems there exist three things: - Local offsets on the GPIO controller, such as if there is a GPIO controller for 32 lines represented by </pre> Linus Walleij 2013-05-20T08:03:24 http://permalink.gmane.org/gmane.linux.documentation/11219 <pre> Thanks, applied. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo&lt; at &gt;vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Kent Overstreet 2013-05-19T17:15:16 http://permalink.gmane.org/gmane.linux.documentation/11218 <pre>Correct spelling typo in documentation/bcache.txt Signed-off-by: Masanari Iida &lt;standby24x7&lt; at &gt;gmail.com&gt; # Please enter the commit message for your changes. Lines starting # with '#' will be kept; you may remove them yourself if you want to. # An empty message aborts the commit. # On branch bcache-fix # Changes to be committed: # (use "git reset HEAD &lt;file&gt;..." to unstage) # #modified: Documentation/bcache.txt # --- Documentation/bcache.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/bcache.txt b/Documentation/bcache.txt index b3a7e7d..c3365f2 100644 --- a/Documentation/bcache.txt +++ b/Documentation/bcache.txt &lt; at &gt;&lt; at &gt; -181,7 +181,7 &lt; at &gt;&lt; at &gt; want for getting the best possible numbers when benchmarking. In practice this isn't an issue because as soon as a write comes along it'll cause the btree node to be split, and you need almost no write traffic for - this to not show up enough to be noticable (especially since bcache's btree + this to not show up e</pre> Masanari Iida 2013-05-19T15:04:35 http://permalink.gmane.org/gmane.linux.documentation/11216 <pre> i2c list is monitored by patchwork which is rigorously not forgetting ;) -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo&lt; at &gt;vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Wolfram Sang 2013-05-17T08:56:57 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.documentation