LE_DEVICE_TABLE.
> Remove #ifdef CONFIG_OF.
> Make the Kconfig symbol to depend on OF.
> Replace irqd_get_trigger_type() with irq_get_trigger_type().
>
> .../bindings/net/wireless/ti,wlcore,spi.txt | 34
In any case:
Acked-by
On Sun, Dec 27, 2015 at 05:34:27PM -0800, Bjorn Andersson wrote:
> Add binding representing the Qualcomm wcn3620/60/80 WiFi block.
> Signed-off-by: Bjorn Andersson
> ---
> .../bindings/net/wireless/qcom,wcn36xx-wifi.txt| 76
> ++
> 1 file changed, 76 insertions(+)
> crea
On Tue, Dec 29, 2015 at 11:03:57AM -0800, Bjorn Andersson wrote:
> On Tue 29 Dec 10:34 PST 2015, Rob Herring wrote:
>
> > On Sun, Dec 27, 2015 at 05:34:27PM -0800, Bjorn Andersson wrote:
> > > Add binding representing the Qualcomm wcn3620/60/80 WiFi block.
> > >
core,spi.txt| 35 +++
For the binding:
Acked-by: Rob Herring
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Dec 23, 2015 at 11:05:15AM +0530, Raja Mani wrote:
> Add device tree binding documentation details for wifi block present
> in Qualcomm IPQ4019 SoC into qcom,ath10k.txt.
>
> Signed-off-by: Raja Mani
> ---
> .../bindings/net/wireless/qcom,ath10k.txt | 87
> --
On Mon, Feb 08, 2016 at 01:11:03PM +0100, Arnd Bergmann wrote:
> On Monday 08 February 2016 02:15:27 Amitkumar Karwar wrote:
> > if (adapter->dt_node) {
> > + if (of_property_read_u32(adapter->dt_node,
> > +"mwifi
On Mon, Feb 08, 2016 at 02:15:26AM -0800, Amitkumar Karwar wrote:
> From: Xinming Hu
>
> Platform device and driver provides easy way to
> interact with device-tree-enabled system.
>
> This patch registers platform driver and reorganise
> existing device tree specific code.
> Corresponding devic
corporate qca4019 cal data download sequence
>
> .../bindings/net/wireless/qcom,ath10k.txt | 23
> +++---
> 1 file changed, 16 insertions(+), 7 deletions(-)
Acked-by: Rob Herring
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
changelist for both 1/2 and 2/2 patches
> v3: Don't update adapter->dt_node if mwifiex_plt_dev is NULL
>
> v4: a)Corrected the 'name' and 'compatible' property names.(Arnd Bergmann and
> Rob
> Herring)
> b)Patch description wraped in 72 co
| 11 +--
> 2 files changed, 1 insertion(+), 12 deletions(-)
Acked-by: Rob Herring
: dts: omap4-droid4: Use wl1285 for wifi compatible
> Bluetooth: hci_ll: Add compatible values for more WL chips
> ARM: dts: omap4-droid4: Add bluetooth
For the series,
Reviewed-by: Rob Herring
On Mon, May 15, 2017 at 10:13:56PM +0200, Martin Blumenstingl wrote:
> The example in the BCM43xx documentation uses "brcmf" as node name.
> However, wireless devices should be named "wifi" instead. Fix this to
> make sure that .dts authors can simply use the documentation as
> reference (or simply
Reichel writes:
>> >>
>> >>> Motorola Droid 4 uses a WL1285C. With differences between the
>> >>> chips not being public let's add explicit binding for wl1285
>> >>> instead of relying on wl1283 being very similar.
>> >>>
&g
On Mon, May 22, 2017 at 11:21 AM, Sebastian Reichel
wrote:
> Hi,
>
> On Mon, May 22, 2017 at 11:11:49AM -0500, Rob Herring wrote:
>> On Mon, May 22, 2017 at 10:21 AM, Sebastian Reichel
>> wrote:
>> > Hi,
>> >
>> > On Mon, May 22, 2017 at 05:44:
ded benefit of
> simplifying the kernel driver and putting the extra complexity into
> userspace.
>
> CC: Rob Herring
> CC: devicet...@vger.kernel.org
> Signed-off-by: Mark Greer
> ---
> .../devicetree/bindings/net/nfc/trf7970a.txt | 4
> drivers/nfc/trf7970a
ek,mt76.txt | 19 +++
> 1 file changed, 19 insertions(+)
>
Reviewed-by: Rob Herring
On Fri, Feb 16, 2018 at 10:13:48AM +0530, Govind Singh wrote:
> Add device tree binding documentation details for wcn3990
> wifi block present in Qualcomm SDM845/APQ8098 SoC into
> "qcom,ath10k.txt".
>
> Signed-off-by: Govind Singh
> ---
> .../bindings/net/wireless/qcom,ath10k.txt | 35
++---
> drivers/of/device.c | 6 --
> drivers/of/of_reserved_mem.c | 2 +-
> drivers/pci/pci-driver.c | 3 +--
> include/linux/device.h| 4
> include/linux/of_device.h | 8 ++++++--
> 10 files changed, 17 insertions(+), 19 deletions(-)
Reviewed-by: Rob Herring
s/qcom,ath10k.txt | 31
> ++
> 1 file changed, 31 insertions(+)
One nit, otherwise:
Reviewed-by: Rob Herring
>
> diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
> b/Documentation/devicetree/bindings/net/wireless/qcom,ath1
ude/linux/of_device.h | 8 ++--
> 10 files changed, 17 insertions(+), 19 deletions(-)
Reviewed-by: Rob Herring
tions(+), 7 deletions(-)
>
Reviewed-by: Rob Herring
vicetree/bindings/net/wireless/qcom,ath10k.txt | 5 +
> 1 file changed, 5 insertions(+)
>
Reviewed-by: Rob Herring
On Tue, Oct 09, 2018 at 11:31:42AM -0700, Brian Norris wrote:
> On Tue, Oct 09, 2018 at 09:22:07AM +0200, Geert Uytterhoeven wrote:
> > Please note these aliases become cumbersome once you start considering
> > (dynamic) DT overlays. That's why I made them optional in the sh-sci
> > serial driver,
On Thu, Oct 04, 2018 at 05:12:43PM +0530, Bhagavathi Perumal S wrote:
> This adds new dt entry ext-fem-name, it is used by ath10k driver
> to select correct timing parameters and configure it in target wifi hardware.
> The Front End Module(FEM) normally includes tx power amplifier(PA) and
> rx low
On Tue, Oct 30, 2018 at 3:41 AM wrote:
>
> On 2018-10-16 00:54, Rob Herring wrote:
> > On Thu, Oct 04, 2018 at 05:12:43PM +0530, Bhagavathi Perumal S wrote:
> >> This adds new dt entry ext-fem-name, it is used by ath10k driver
> >> to select correct timing paramet
On Tue, Dec 11, 2018 at 12:01:29AM +0530, Bhagavathi Perumal S wrote:
> In qcom,ath10k documentation, ath10k is used as node name in the example of
> pci based device. Normally, node name shoud be class of device and not the
> model
s/shoud/should/
> name, so fix it to node name "wifi". And remo
oose correct
> timing values in driver if different external FEM hardware used.
>
> Signed-off-by: Bhagavathi Perumal S
> ---
> Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt | 9 -
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring
On Tue, Dec 11, 2018 at 09:43:23PM +0530, Bhagavathi Perumal S wrote:
> This adds new dt entry ext-fem-name, it is used by ath10k driver
> to select correct timing parameters and configure it in target wifi hardware.
> The Front End Module(FEM) normally includes tx power amplifier(PA) and
> rx low
remove the property device_type
> pci since only pci bridges should have this property.
>
> Signed-off-by: Bhagavathi Perumal S
> ---
> Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
Reviewed-by: Rob Herring
On Thu, Feb 02, 2017 at 12:52:06PM +0100, Felix Fietkau wrote:
> Signed-off-by: Felix Fietkau
> ---
> .../bindings/net/wireless/mediatek,mt76.txt| 25
> ++
> 1 file changed, 25 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/net/wireless/media
On Tue, Feb 07, 2017 at 06:22:04AM +0100, Heiko Schocher wrote:
> From: Guan Ben
>
> Make the EN2 pin optional. This is useful for boards,
> which have this pin fix wired, for example to ground.
>
> Signed-off-by: Guan Ben
> Signed-off-by: Mark Jonas
> Signed-off-by: Heiko Schocher
>
> ---
>
On Mon, Feb 13, 2017 at 12:38 AM, Heiko Schocher wrote:
> Hello Rob,
>
>
> Am 10.02.2017 um 16:51 schrieb Rob Herring:
>>
>> On Tue, Feb 07, 2017 at 06:22:04AM +0100, Heiko Schocher wrote:
>>>
>>> From: Guan Ben
>>>
>>> Make the EN2
On Tue, Feb 07, 2017 at 09:20:33PM +0100, Felix Fietkau wrote:
> Signed-off-by: Felix Fietkau
Commit msg? Also, use "dt-bindings: net: " for the subject prefix.
> ---
> .../bindings/net/wireless/mediatek,mt76.txt| 24
> ++
> 1 file changed, 24 insertions(+)
> creat
On Sun, Feb 19, 2017 at 11:19 PM, Heiko Schocher wrote:
> Hello all,
>
> Am 13.02.2017 um 22:31 schrieb Rob Herring:
>>
>> On Mon, Feb 13, 2017 at 12:38 AM, Heiko Schocher wrote:
>>>
>>> Hello Rob,
>>>
>>>
>>> Am 10.02.2017 um 16
On Wed, Jan 25, 2017 at 11:54 PM, Marcel Holtmann wrote:
> Hi Rob,
>
>> It appears that TI WiLink devices including NFC (WL185x/WL189x) never
>> shipped. The only information I found were announcements in Feb
>> 2012 about the parts. There's been no activity on this driver besided
>> common change
On Fri, Feb 24, 2017 at 3:43 PM, Marcel Holtmann wrote:
> Hi Rob,
>
It appears that TI WiLink devices including NFC (WL185x/WL189x) never
shipped. The only information I found were announcements in Feb
2012 about the parts. There's been no activity on this driver besided
common
On Fri, Mar 10, 2017 at 09:06:14AM +0100, Sven Eckelmann wrote:
> The bus + bmi-chip-id + bmi-board-id is not enough to identify the correct
> board data file on QCA4019 based devices. Multiple different boards share
> the same values. Only the original reference designs can currently be
> identifi
gt; --
> 1 file changed, 38 insertions(+), 3 deletions(-)
For the subject, "dt-bindings: net: ..." and one nit below, otherwise:
Acked-by: Rob Herring
>
> diff --git a/Documentation/devicetree/bindings/net/wireless/qca,ath9k.txt
> b/Documentation/devi
On Mon, Mar 20, 2017 at 11:28 AM, Sven Eckelmann
wrote:
> On Montag, 20. März 2017 10:07:33 CET Rob Herring wrote:
>> On Fri, Mar 10, 2017 at 09:06:14AM +0100, Sven Eckelmann wrote:
>> > The bus + bmi-chip-id + bmi-board-id is not enough to identify the correct
>> >
On Tue, Mar 21, 2017 at 9:33 AM, Sven Eckelmann
wrote:
> On Dienstag, 21. März 2017 08:00:34 CET Rob Herring wrote:
> [...]
>> > It would then up with something like this as compatibility string:
>> >
>> > * qcom,ipq4019-wifi-asus-rt-ac58u
>> > * qc
On Sun, Jul 10, 2016 at 08:32:40AM +, Reizer, Eyal wrote:
> Add support for using with both wl12xx and wl18xx.
>
> - all wilink family needs special init command for entering wspi mode.
> extra clock cycles should be sent after the spi init command while the
> cs pin is high.
> - Use inver
On Thu, Jul 07, 2016 at 10:46:28AM +0200, Arnd Bergmann wrote:
> On Wednesday, July 6, 2016 9:19:41 PM CEST Arend Van Spriel wrote:
> > On 6-7-2016 15:42, Arnd Bergmann wrote:
> > > On Wednesday, July 6, 2016 10:08:55 AM CEST Arend Van Spriel wrote:
> > >> On Tue, Jul 5, 2016 at 3:43 PM, Arnd Bergm
On Tue, Sep 06, 2016 at 11:46:21PM +0200, Martin Blumenstingl wrote:
> Add documentation how devicetree can be used to configure ath9k based
> devices.
>
> Signed-off-by: Martin Blumenstingl
> ---
> .../devicetree/bindings/net/wireless/qca,ath9k.txt | 39
> ++
> 1 file chang
On Fri, Sep 09, 2016 at 10:57:06PM +0200, Martin Blumenstingl wrote:
> On Fri, Sep 9, 2016 at 9:48 AM, Oleksij Rempel wrote:
> >> +Optional properties:
> >> +- reg: Address and length of the register set for the device.
> >> +- qca,clk-25mhz: Defines that a 25MHz clock is used
> >
> > Some SoCs ev
On Fri, Sep 09, 2016 at 08:47:34PM +0530, Amitkumar Karwar wrote:
> From: Xinming Hu
>
> This patch derives device tree node from pcie bus layer framework.
> Device tree bindings file has been renamed(marvell-sd8xxx.txt ->
> marvell-8xxx.txt) to accomodate PCIe changes.
>
> Signed-off-by: Xinmin
On Sun, Oct 2, 2016 at 5:50 PM, Martin Blumenstingl
wrote:
> There are at least two drivers (ath9k and mt76) out there, where
> devicetree authors need to override the enabled bands.
>
> For ath9k there is only one use-case: disabling a band which has been
> incorrectly enabled by the vendor in th
>
> Signed-off-by: Xinming Hu
> Signed-off-by: Amitkumar Karwar
> ---
> v2: Included vendor and product IDs in compatible strings for PCIe
> chipsets(Rob Herring)
> v3: Patch is created using -M option so that it will only include diff of
> original and renamed files(Rob Herring
On Wed, Oct 5, 2016 at 1:36 PM, Felix Fietkau wrote:
> On 2016-10-05 20:25, Martin Blumenstingl wrote:
>> On Mon, Oct 3, 2016 at 5:22 PM, Rob Herring wrote:
>>> On Sun, Oct 2, 2016 at 5:50 PM, Martin Blumenstingl
>>> wrote:
>>>> There are at least two dr
On Sun, Oct 02, 2016 at 11:47:41PM +0200, Martin Blumenstingl wrote:
> Add documentation how devicetree can be used to configure ath9k based
> devices.
>
> Signed-off-by: Martin Blumenstingl
> ---
> .../devicetree/bindings/net/wireless/qca,ath9k.txt | 30
> ++
> 1 file chang
+++
> 1 file changed, 48 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/net/wireless/qca,ath9k.txt
Acked-by: Rob Herring
vell-sd8xxx.txt ->
> marvell-8xxx.txt) to accommodate PCIe changes.
>
> Signed-off-by: Xinming Hu
> Signed-off-by: Amitkumar Karwar
> Signed-off-by: Rajat Jain
> Reviewed-by: Brian Norris
> ---
> v2: Included vendor and product IDs in compatible strings for PCIe
> chipsets
ist for both 1/2 and 2/2 patches
> v3: Don't update adapter->dt_node if mwifiex_plt_dev is NULL
>
> v4: a)Corrected the 'name' and 'compatible' property names.(Arnd Bergmann and
> Rob
> Herring)
> b)Patch description wraped in 72 columns(Ro
changelist for both 1/2 and 2/2 patches
> v3: Don't update adapter->dt_node if mwifiex_plt_dev is NULL
>
> v4: a)Corrected the 'name' and 'compatible' property names.(Arnd Bergmann and
> Rob
> Herring)
> b)Patch description wraped in 72 co
On Tue, Jun 21, 2016 at 12:02:06PM +, Reizer, Eyal wrote:
> Add support for using with both wl12xx and wl18xx.
>
> - all wilink family needs special init command for entering wspi mode.
> extra clock cycles should be sent after the spi init command while the
> cs pin is high.
> - Use inver
d
> for sending the extra init cycle which, achieves the same hardware purpose.
> update device tree bindings docucmentation accordingly
> v3->v4: Remove redundant data form binding documentation and fix chip select
> number mismatch in wl1271 example
>
> .../bindings/net
On Wed, Jun 29, 2016 at 04:04:31PM +0200, Hans de Goede wrote:
> Add a brcm,nvram_file_name dt property to allow overruling the default
> nvram filename for sdio devices. The idea is that we can specify a
> board specific nvram file, e.g. brcmfmac43362-ap6210.txt for boards
> with an ap6210 wifi sd
On Fri, Jul 01, 2016 at 10:17:37AM +0200, Arend Van Spriel wrote:
>
>
> On 1-7-2016 4:08, Rob Herring wrote:
> > On Wed, Jun 29, 2016 at 04:04:31PM +0200, Hans de Goede wrote:
> >> Add a brcm,nvram_file_name dt property to allow overruling the default
> >> nvr
76.txt| 32
> ++
> 1 file changed, 32 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/net/wireless/mediatek,mt76.txt
Acked-by: Rob Herring
ect board data for a design which was modified by an ODM.
>
> Signed-off-by: Sven Eckelmann
> ---
> Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt | 3 +++
> 1 file changed, 3 insertions(+)
Reviewed-by: Rob Herring
On Mon, Dec 11, 2017 at 10:55:18AM +0100, Arend van Spriel wrote:
> On 12/11/2017 9:11 AM, Chi-Hsien Lin wrote:
> > broken_sg_support, sd_head_align, and sd_sgentry_align are used in
> > brcmfmac code but not configurable in dts file. Add the parsing logic.
> > Now they can be configured like below
On Tue, Nov 01, 2016 at 11:58:39AM +0100, Paul Cercueil wrote:
> This document gives information about how to write a devicetree
> node that corresponds to the rfkill-regulator driver.
>
> Signed-off-by: Paul Cercueil
> ---
> .../devicetree/bindings/net/rfkill-regulator.txt | 18
> +++
On Thu, Nov 17, 2016 at 05:14:23PM +0530, c_tr...@qti.qualcomm.com wrote:
> From: Tamizh chelvam
>
> There two things done in this patch.
>
> 1) 'btcoex_support' flag for BTCOEX feature support by the hardware.
> 2) 'wlan_btcoex_gpio' is used to fill wlan priority pin number for
>BTCOEX prio
>
> Signed-off-by: Xinming Hu
> Signed-off-by: Rajat Jain
> Reviewed-by: Brian Norris
> Signed-off-by: Amitkumar Karwar
> ---
> v2: Included vendor and product IDs in compatible strings for PCIe
> chipsets(Rob Herring)
> v3: Patch is created using -M option so that it wil
On Fri, Nov 18, 2016 at 06:21:41PM +0200, Kalle Valo wrote:
> Amitkumar Karwar writes:
>
> > From: Xinming Hu
> >
> > This patch derives device tree node from pcie bus layer framework.
> > Device tree bindings file has been renamed(marvell-sd8xxx.txt ->
> > marvell-8xxx.txt) to accommodate PCIe
On Thu, Nov 17, 2016 at 05:55:09PM -0800, Matt Ranostay wrote:
> Allow power sequencing for the Marvell SD8787 Wifi/BT chip.
> This can be abstracted to other chipsets if needed in the future.
I don't like the MMC pwrseq bindings, so I won't be acking any. Look at
the USB pwrseq for why.
> Cc: T
On Mon, Nov 28, 2016 at 9:54 AM, Ulf Hansson wrote:
> [...]
>
>>> +
>>> +Example:
>>> +
>>> + wifi_pwrseq: wifi_pwrseq {
>>> + compatible = "mmc-pwrseq-sd8787";
>>> + pwrdn-gpio = <&twl_gpio 0 GPIO_ACTIVE_LOW>;
>>> + reset-gpio = <&twl_gpio 1 GPIO_ACTIVE_LOW
On Thu, Dec 15, 2016 at 05:30:42PM -0500, Geoff Lansberry wrote:
> From: Geoff Lansberry
>
> ---
> .../devicetree/bindings/net/nfc/trf7970a.txt | 3 ++
> drivers/nfc/trf7970a.c | 42
> --
> 2 files changed, 34 insertions(+), 11 deletions(-)
On Thu, Dec 15, 2016 at 05:30:43PM -0500, Geoff Lansberry wrote:
> From: Geoff Lansberry
>
> ---
> Documentation/devicetree/bindings/net/nfc/trf7970a.txt | 2 ++
> drivers/nfc/trf7970a.c | 13 -
> 2 files changed, 14 insertions(+), 1 deletion(-)
>
>
On Mon, Dec 19, 2016 at 5:23 PM, Geoff Lansberry wrote:
> I can make that change, however, I worry that it may be a bit
> misleading, since there are only two supported clock frequencies, but
> a number like that to me implies that it could be set to any number
> you want. I'm new at this, and s
13.56MHz clock or the optional 27.12MHz clock.
>
> Signed-off-by: Geoff Lansberry
> ---
> .../devicetree/bindings/net/nfc/trf7970a.txt | 2 +
Acked-by: Rob Herring
> drivers/nfc/trf7970a.c | 50
> +-
> 2 files changed, 41 insertions(+), 11 deletions(-)
the hardware configuration. If no option is supplied it defaults to
> 3.3 volt configuration.
>
> Signed-off-by: Geoff Lansberry
> ---
> .../devicetree/bindings/net/nfc/trf7970a.txt | 2 ++
Acked-by: Rob Herring
> drivers/nfc/trf7970a.c | 26
On Wed, Dec 28, 2016 at 04:59:54PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This new file should be used for properties handled at higher level and
> so usable with all drivers.
Why is this needed? Where would this data normally come from?
> Signed-off-by: Rafał Miłecki
> ---
> .
On Tue, Jan 03, 2017 at 12:03:38PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This new file should be used for properties that apply to all wireless
> devices.
The commit msg should answer the questions I asked on v1.
> Signed-off-by: Rafał Miłecki
> ---
> V2: Switch to a single iee
On Tue, Jan 03, 2017 at 11:57:15PM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> There are some devices (e.g. Netgear R8000 home router) with one chipset
> model used for different radios, some of them limited to subbands. NVRAM
> entries don't contain any extra info on such limitations a
> Documentation/devicetree/bindings/net/wireless/ieee80211.txt
Acked-by: Rob Herring
On Thu, Jan 5, 2017 at 5:51 AM, Johannes Berg wrote:
>
>> Acked-by: Rob Herring
>
> Do I take that to mean that we'll merge it through the subsystem tree,
> and not go through some common DT tree?
Yes, that's generally the case when bindings are in a series with
driver changes.
Rob
On Thu, Jan 12, 2017 at 09:22:17PM -0800, Matt Ranostay wrote:
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Matt Ranostay
> ---
> Documentation/devicetree/bindings/net/wireless/marvell-8xxx.txt | 7 ++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
Acked-by: Rob Herring
On Thu, Jan 12, 2017 at 09:29:36PM -0800, Matt Ranostay wrote:
Changelog?
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Matt Ranostay
> ---
> .../devicetree/bindings/mmc/mmc-pwrseq-sd8787.txt | 14
> ++
> .../devicetree/bindings/net/wireless/marvell-8xxx.txt | 7
x-wireless@vger.kernel.org
Signed-off-by: Rob Herring
---
drivers/nfc/Kconfig | 11 -
drivers/nfc/Makefile| 1 -
drivers/nfc/nfcwilink.c | 578
3 files changed, 590 deletions(-)
delete mode 100644 drivers/nfc/nfcwilink.c
diff --git a/d
On Tue, Jul 18, 2017 at 03:29:40PM +0800, Icenowy Zheng wrote:
> Allwinner XR819 is a SDIO Wi-Fi chip, which has the functionality to use
> an out-of-band interrupt pin instead of SDIO in-band interrupt.
>
> Add the device tree binding of this chip, in order to make it possible
> to add this inter
On Wed, Aug 30, 2017 at 02:02:18PM +0200, Antony Antony wrote:
> hi,
>
> On Wed, Aug 30, 2017 at 10:28:20AM +0800, Chen-Yu Tsai wrote:
> > On Wed, Aug 30, 2017 at 5:43 AM, Antony Antony wrote:
>
> > > a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt
> > > +++ b/Documentatio
On Fri, Sep 1, 2017 at 2:10 PM, Arend van Spriel
wrote:
> On 01-09-17 18:49, Rob Herring wrote:
>>
>> On Wed, Aug 30, 2017 at 02:02:18PM +0200, Antony Antony wrote:
>>>
>>> hi,
>>>
>>> On Wed, Aug 30, 2017 at 10:28:20AM +0800, Chen-Yu Tsai wrote
On Fri, Oct 06, 2017 at 01:02:47PM +0200, Felix Fietkau wrote:
> Add documentation describing how device tree can be used to configure
> wireless chips supported by the mt76 driver.
>
> Signed-off-by: Felix Fietkau
> ---
> .../bindings/net/wireless/mediatek,mt76.txt| 24
> ++
On Sat, Oct 14, 2017 at 10:43 AM, Christian Lamparter
wrote:
> On Saturday, October 14, 2017 9:20:46 AM CEST Felix Fietkau wrote:
>> On 2017-10-13 21:07, Rob Herring wrote:
>> > On Fri, Oct 06, 2017 at 01:02:47PM +0200, Felix Fietkau wrote:
>> >> Add documentation
On Tue, Aug 20, 2019 at 06:47:27PM +0300, Kalle Valo wrote:
Missing commit message and Sob (and on the other patches).
> ---
> .../bindings/net/wireless/qcom,ath11k.txt | 127
> +
> 1 file changed, 127 insertions(+)
Please use the DT schema format (YAML). See writi
85 matches
Mail list logo
