Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1280111 > unrolled thread
| Started by | Ray Jui <rjui@broadcom.com> |
|---|---|
| First post | 2015-11-30 18:10 +0100 |
| Last post | 2015-12-11 00:00 +0100 |
| 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 2/3] pinctrl: nsp: add pinmux driver support for Broadcom NSP SoC Ray Jui <rjui@broadcom.com> - 2015-11-30 18:10 +0100
Re: [PATCH 2/3] pinctrl: nsp: add pinmux driver support for Broadcom NSP SoC Linus Walleij <linus.walleij@linaro.org> - 2015-12-10 18:00 +0100
Re: [PATCH 2/3] pinctrl: nsp: add pinmux driver support for Broadcom NSP SoC Ray Jui <rjui@broadcom.com> - 2015-12-11 00:00 +0100
| From | Ray Jui <rjui@broadcom.com> |
|---|---|
| Date | 2015-11-30 18:10 +0100 |
| Subject | Re: [PATCH 2/3] pinctrl: nsp: add pinmux driver support for Broadcom NSP SoC |
| Message-ID | <qAA7D-6si-15@gated-at.bofh.it> |
Hi Linus, On 11/30/2015 4:49 AM, Linus Walleij wrote: > On Fri, Nov 20, 2015 at 6:57 PM, Yendapally Reddy Dhananjaya Reddy > <yrdreddy@broadcom.com> wrote: > >> This adds the initial support of the Broadcom NSP pinmux driver. >> >> Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yrdreddy@broadcom.com> > > So what does Ray and Stephen say about this? > > Is the hardware unique enough to warrant its own driver? > > Or should it utilize/extend one of the existing Broadcom > drivers? Currently, the IOMUX configurations in Cygnus, NSP, and NS2 are completely different and require a separate driver to each of these SoCs. We now realize the shortcomings and have been communicating with our ASIC team. We'd like to fix this for the next-gen of our SoC. We are driving towards using a register layout that will allow us to use just "pinctrl-single" and "pinconf-single." > > Yours, > Linus Walleij > Thanks, Ray -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [next] | [standalone]
| From | Linus Walleij <linus.walleij@linaro.org> |
|---|---|
| Date | 2015-12-10 18:00 +0100 |
| Message-ID | <qEcJs-k8-7@gated-at.bofh.it> |
| In reply to | #1280111 |
On Mon, Nov 30, 2015 at 6:05 PM, Ray Jui <rjui@broadcom.com> wrote: > Hi Linus, > > On 11/30/2015 4:49 AM, Linus Walleij wrote: >> >> On Fri, Nov 20, 2015 at 6:57 PM, Yendapally Reddy Dhananjaya Reddy >> <yrdreddy@broadcom.com> wrote: >> >>> This adds the initial support of the Broadcom NSP pinmux driver. >>> >>> Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yrdreddy@broadcom.com> >> >> >> So what does Ray and Stephen say about this? >> >> Is the hardware unique enough to warrant its own driver? >> >> Or should it utilize/extend one of the existing Broadcom >> drivers? > > > Currently, the IOMUX configurations in Cygnus, NSP, and NS2 are completely > different and require a separate driver to each of these SoCs. We now > realize the shortcomings and have been communicating with our ASIC team. > We'd like to fix this for the next-gen of our SoC. We are driving towards > using a register layout that will allow us to use just "pinctrl-single" and > "pinconf-single." OK can you provide your reviews for the NSP driver? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Ray Jui <rjui@broadcom.com> |
|---|---|
| Date | 2015-12-11 00:00 +0100 |
| Message-ID | <qEilQ-432-9@gated-at.bofh.it> |
| In reply to | #1288671 |
Hi Linus, On 12/10/2015 8:50 AM, Linus Walleij wrote: > On Mon, Nov 30, 2015 at 6:05 PM, Ray Jui <rjui@broadcom.com> wrote: >> Hi Linus, >> >> On 11/30/2015 4:49 AM, Linus Walleij wrote: >>> >>> On Fri, Nov 20, 2015 at 6:57 PM, Yendapally Reddy Dhananjaya Reddy >>> <yrdreddy@broadcom.com> wrote: >>> >>>> This adds the initial support of the Broadcom NSP pinmux driver. >>>> >>>> Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yrdreddy@broadcom.com> >>> >>> >>> So what does Ray and Stephen say about this? >>> >>> Is the hardware unique enough to warrant its own driver? >>> >>> Or should it utilize/extend one of the existing Broadcom >>> drivers? >> >> >> Currently, the IOMUX configurations in Cygnus, NSP, and NS2 are completely >> different and require a separate driver to each of these SoCs. We now >> realize the shortcomings and have been communicating with our ASIC team. >> We'd like to fix this for the next-gen of our SoC. We are driving towards >> using a register layout that will allow us to use just "pinctrl-single" and >> "pinconf-single." > > OK can you provide your reviews for the NSP driver? > > Yours, > Linus Walleij > Yes, I just replied to the email thread with my "Reviewed-by". In fact, both Scott and I reviewed the patches internally in Broadcom before they went out to public. Thanks, Ray -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web