From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: devicetree@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: ath10k: calibration data through Device Tree?
Date: Thu, 2 Oct 2014 17:55:57 +0300 [thread overview]
Message-ID: <87d2aamsg2.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <2397903.vznsjdQh6x@wuerfel> (Arnd Bergmann's message of "Thu, 2 Oct 2014 16:19:28 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Thursday 02 October 2014 16:47:48 Kalle Valo wrote:
>> >
>> > When you know the PCI bus/device/function ID of the device, you can put
>> > a device node in the dts file that corresponds to the PCI dev, and you
>> > can find the of_node pointer from pci_dev->dev.of_node.
>>
>> For me that's easier said than done as I'm a total newbie with Device
>> Tree Can you give any pointers or examples how to do that in
>> practise, please? Especially "node in the dts file that corresponds to
>> the PCI dev" part is puzzling me.
>
> See the recent patch "[PATCH v4] ARM: shmobile: r8a7791: link PCI USB
> devices to USB PHY" where someone does the same thing to supply additional
> data to a PCI device node in shmobile.
>
> Basically you just need to add a node under your PCI host controller node
> with "reg = <0x800 0 0 0 0>" (or whatever the address is and put the
> properties in there. See www.openfirmware.org/1275/bindings/pci/pci2_1.pdf
> for the description of how to construct the addresses.
Excellent, thanks. I'll study these and try to learn more.
> I notice that there are no Qualcomm or Atheros PCI host controller drivers
> in Linux though, so you first have to write a driver that allows probing
> the PCI bus, and get the binding reviewed for that before you can add
> it to the dts files. Is this for ipq8064 or something else?
But now I'm lost again :) I want ath10k and this feature to work with
all possible PCI controllers, not just with Qualcomm controllers. So why
do I need to wait for Qualcomm PCI host controller driver?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo-A+ZNKFmMK5xy9aJCnZT0Uw@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ath10k-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: ath10k: calibration data through Device Tree?
Date: Thu, 2 Oct 2014 17:55:57 +0300 [thread overview]
Message-ID: <87d2aamsg2.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <2397903.vznsjdQh6x@wuerfel> (Arnd Bergmann's message of "Thu, 2 Oct 2014 16:19:28 +0200")
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org> writes:
> On Thursday 02 October 2014 16:47:48 Kalle Valo wrote:
>> >
>> > When you know the PCI bus/device/function ID of the device, you can put
>> > a device node in the dts file that corresponds to the PCI dev, and you
>> > can find the of_node pointer from pci_dev->dev.of_node.
>>
>> For me that's easier said than done as I'm a total newbie with Device
>> Tree Can you give any pointers or examples how to do that in
>> practise, please? Especially "node in the dts file that corresponds to
>> the PCI dev" part is puzzling me.
>
> See the recent patch "[PATCH v4] ARM: shmobile: r8a7791: link PCI USB
> devices to USB PHY" where someone does the same thing to supply additional
> data to a PCI device node in shmobile.
>
> Basically you just need to add a node under your PCI host controller node
> with "reg = <0x800 0 0 0 0>" (or whatever the address is and put the
> properties in there. See www.openfirmware.org/1275/bindings/pci/pci2_1.pdf
> for the description of how to construct the addresses.
Excellent, thanks. I'll study these and try to learn more.
> I notice that there are no Qualcomm or Atheros PCI host controller drivers
> in Linux though, so you first have to write a driver that allows probing
> the PCI bus, and get the binding reviewed for that before you can add
> it to the dts files. Is this for ipq8064 or something else?
But now I'm lost again :) I want ath10k and this feature to work with
all possible PCI controllers, not just with Qualcomm controllers. So why
do I need to wait for Qualcomm PCI host controller driver?
--
Kalle Valo
--
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:[~2014-10-02 14:56 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 13:14 ath10k: calibration data through Device Tree? Kalle Valo
2014-10-02 13:14 ` Kalle Valo
2014-10-02 13:27 ` Arnd Bergmann
2014-10-02 13:27 ` Arnd Bergmann
2014-10-02 13:47 ` Kalle Valo
2014-10-02 13:47 ` Kalle Valo
2014-10-02 14:19 ` Arnd Bergmann
2014-10-02 14:19 ` Arnd Bergmann
2014-10-02 14:55 ` Kalle Valo [this message]
2014-10-02 14:55 ` Kalle Valo
2014-10-02 15:58 ` Arnd Bergmann
2014-10-02 15:58 ` Arnd Bergmann
2014-10-02 13:29 ` Mark Rutland
2014-10-02 13:29 ` Mark Rutland
2014-10-02 13:44 ` Kalle Valo
2014-10-02 13:44 ` Kalle Valo
2014-10-02 15:07 ` Mark Rutland
2014-10-02 15:07 ` Mark Rutland
2014-10-02 19:05 ` Andy Lutomirski
2014-10-02 19:05 ` Andy Lutomirski
2014-10-02 19:28 ` Adrian Chadd
2014-10-02 19:28 ` Adrian Chadd
2014-10-02 19:35 ` Andy Lutomirski
2014-10-02 19:35 ` Andy Lutomirski
2014-10-07 16:44 ` Kalle Valo
2014-10-07 16:44 ` Kalle Valo
2014-10-17 12:25 ` Kumar Gala
2014-10-17 12:25 ` Kumar Gala
2014-10-22 12:02 ` Kalle Valo
2014-10-22 12:02 ` Kalle Valo
2014-10-03 15:29 ` Arnd Bergmann
2014-10-03 15:29 ` Arnd Bergmann
2014-10-03 16:24 ` Andy Lutomirski
2014-10-03 16:24 ` Andy Lutomirski
2014-10-03 16:25 ` Mark Rutland
2014-10-03 16:25 ` Mark Rutland
2014-10-03 16:42 ` Arnd Bergmann
2014-10-03 16:42 ` Arnd Bergmann
2014-10-03 16:54 ` Andy Lutomirski
2014-10-03 16:54 ` Andy Lutomirski
2014-10-03 17:21 ` Adrian Chadd
2014-10-03 17:21 ` Adrian Chadd
-- strict thread matches above, loose matches on Subject: below --
2014-10-02 13:05 Kalle Valo
2014-10-02 13:09 ` Kalle Valo
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=87d2aamsg2.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=arnd@arndb.de \
--cc=ath10k@lists.infradead.org \
--cc=devicetree@vger.kernel.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 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.