Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1482433 > unrolled thread
| Started by | Joel Stanley <joel@jms.id.au> |
|---|---|
| First post | 2016-09-13 14:50 +0200 |
| Last post | 2016-09-14 03:00 +0200 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v3 4/7] palmetto: Request relevant mux functions in devicetree Joel Stanley <joel@jms.id.au> - 2016-09-13 14:50 +0200
Re: [PATCH v3 4/7] palmetto: Request relevant mux functions in devicetree Benjamin Herrenschmidt <benh@kernel.crashing.org> - 2016-09-13 23:00 +0200
Re: [PATCH v3 4/7] palmetto: Request relevant mux functions in devicetree Joel Stanley <joel@jms.id.au> - 2016-09-14 03:00 +0200
| From | Joel Stanley <joel@jms.id.au> |
|---|---|
| Date | 2016-09-13 14:50 +0200 |
| Subject | Re: [PATCH v3 4/7] palmetto: Request relevant mux functions in devicetree |
| Message-ID | <sgVjY-1TH-45@gated-at.bofh.it> |
On Tue, Aug 30, 2016 at 5:25 PM, Andrew Jeffery <andrew@aj.id.au> wrote:
> +&pinctrl {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_flbusy_default &pinctrl_flwp_default
> + &pinctrl_vgahs_default &pinctrl_vgavs_default
> + &pinctrl_ddcclk_default &pinctrl_ddcdat_default
> +
> + &pinctrl_pwm1_default &pinctrl_pwm2_default
> + &pinctrl_pwm3_default &pinctrl_pwm4_default
> + &pinctrl_pwm5_default &pinctrl_pwm6_default
> + &pinctrl_pwm7_default
> +
> + &pinctrl_bmcint_default &pinctrl_flack_default>;
> +};
It's not clear that all systems use these pins in that way. I will not
include this one for now.
Cheers,
Joel
[toc] | [next] | [standalone]
| From | Benjamin Herrenschmidt <benh@kernel.crashing.org> |
|---|---|
| Date | 2016-09-13 23:00 +0200 |
| Subject | Re: [PATCH v3 4/7] palmetto: Request relevant mux functions in devicetree |
| Message-ID | <sh2Ya-6XB-27@gated-at.bofh.it> |
| In reply to | #1482433 |
On Tue, 2016-09-13 at 22:11 +0930, Joel Stanley wrote: > It's not clear that all systems use these pins in that way. I will > not > include this one for now. Well, it has VGA so the VGA hsync, vsync and DDC should be there at least... Ben.
[toc] | [prev] | [next] | [standalone]
| From | Joel Stanley <joel@jms.id.au> |
|---|---|
| Date | 2016-09-14 03:00 +0200 |
| Message-ID | <sh6Ip-17K-17@gated-at.bofh.it> |
| In reply to | #1482778 |
On Wed, Sep 14, 2016 at 6:28 AM, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote: > On Tue, 2016-09-13 at 22:11 +0930, Joel Stanley wrote: >> It's not clear that all systems use these pins in that way. I will >> not >> include this one for now. > > Well, it has VGA so the VGA hsync, vsync and DDC should be there at > least... True. When we enable VGA in our tree these pins will be requested as part of the VGA driver's device node, so they don't need to be hogged by the pinctrl node like this. The ones I'm not clear on are bmc_flack and bmc_int. Andrew, do you have a recommendation here? Cheers, Joel
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web